Appearance
Square
Process payments, manage catalog items, and handle orders with the Square API.
| Detail | Value |
|---|---|
| Category | Payments |
| Base URL | https://connect.squareup.com |
| Authentication | Bearer Token |
| Endpoints | 6 |
| Connector key | square |
Using Square in a workflow
- Go to Connections and click New Connection.
- Pick Square from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
POST /payments | Create a payment |
GET /payments/{payment_id} | Retrieve a payment |
GET /payments | List payments |
POST /refunds | Refund a payment |
GET /customers | List customers |
POST /customers | Create a customer |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
POST /payments
Create a payment
| Detail | Value |
|---|---|
| Operation ID | payments.createPayment |
| Method | POST |
| Path | /payments |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
source_id | string |
amount_money | object |
idempotency_key | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Square connection from the Connection dropdown.
- In the Operation dropdown, select
payments.createPayment. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Square API reference.
GET /payments/{payment_id}
Retrieve a payment
| Detail | Value |
|---|---|
| Operation ID | payments.getPayment |
| Method | GET |
| Path | /payments/{payment_id} |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
payment_id | path | string | Yes |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Square connection from the Connection dropdown.
- In the Operation dropdown, select
payments.getPayment. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Square API reference.
GET /payments
List payments
| Detail | Value |
|---|---|
| Operation ID | payments.listPayments |
| Method | GET |
| Path | /payments |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
begin_time | query | string | No |
end_time | query | string | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Square connection from the Connection dropdown.
- In the Operation dropdown, select
payments.listPayments. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Square API reference.
POST /refunds
Refund a payment
| Detail | Value |
|---|---|
| Operation ID | payments.refundPayment |
| Method | POST |
| Path | /refunds |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
payment_id | string |
amount_money | object |
idempotency_key | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Square connection from the Connection dropdown.
- In the Operation dropdown, select
payments.refundPayment. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Square API reference.
GET /customers
List customers
| Detail | Value |
|---|---|
| Operation ID | payments.listCustomers |
| Method | GET |
| Path | /customers |
Parameters
| Name | Location | Type | Required |
|---|---|---|---|
cursor | query | string | No |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Square connection from the Connection dropdown.
- In the Operation dropdown, select
payments.listCustomers. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Square API reference.
POST /customers
Create a customer
| Detail | Value |
|---|---|
| Operation ID | payments.createCustomer |
| Method | POST |
| Path | /customers |
Parameters
No parameters.
Request Body
| Field | Type |
|---|---|
given_name | string |
email_address | string |
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Square connection from the Connection dropdown.
- In the Operation dropdown, select
payments.createCustomer. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
Required fields are marked — fill them or the call will fail at runtime.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Square API reference.