Short answer: Drop the "Square → Create Square Customer" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
First Name given_name | string | Optional | — |
Last Name family_name | string | Optional | — |
Email email_address | string | Optional | The email address. Used as the recipient or identifier depending on context. |
Phone phone_number | string | Optional | Phone number in E.164 format (with country code, no spaces). |
Company company_name | string | Optional | — |
Note note | string | Optional | — |
{"given_name": "{{trigger.given_name}}","family_name": "{{trigger.family_name}}","email_address": "e.g. user@example.com","phone_number": "e.g. +14155551234","company_name": "{{trigger.company_name}}"}
{"customer": {"id": "ABC123","given_name": "Jane","family_name": "Doe","email_address": "jane@acme.com"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.