Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Square

Payment solutions for every business

CategoryCommerce
AuthenticationOAuth 2.0
Version0.4.6
Published scopes11 published scopes
Last updatedSeptember 26, 2026

Overview

Connect Square with Flows360

Payment solutions for every business

Use the Square connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes no declared actions and 7 triggers.

Available actions

  • No actions are declared in this pinned package.

Available triggers

  • New Order
  • Order Updated
  • New Customer
  • Customer Updated
  • New Appointment
  • New Payment
  • Plus 1 additional declared trigger.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Square
  • Package: @activepieces/piece-square@0.4.6
  • Exact artifact digest: sha256:2a00af15c8cb0f4092c42192cc6495f1fcebc80efe58c62e282e410f1d0bb6fb
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

OAUTH2. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

No actions are declared by this package version.

Trigger contracts

  • New Order, app webhook.
  • Order Updated, app webhook.
  • New Customer, app webhook.
  • Customer Updated, app webhook.
  • New Appointment, app webhook.
  • New Payment, app webhook.
  • New Invoice, app webhook.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 0 exercised action entrypoints and 7 exercised trigger entrypoints.

Capability summary

AuthenticationOAuth 2.0
Supported objects7
Supported actionsNot published
Triggers7

Authentication

Authentication method: OAuth 2.0

Required scopes

MERCHANT_PROFILE_READCUSTOMERS_READCUSTOMERS_WRITEITEMS_READITEMS_WRITEORDERS_READORDERS_WRITEPAYMENTS_READINVOICES_READAPPOINTMENTS_READAPPOINTMENTS_WRITE

Authentication profiles

connection · oauth2

OAuth scopes: MERCHANT_PROFILE_READ, CUSTOMERS_READ, CUSTOMERS_WRITE, ITEMS_READ, ITEMS_WRITE, ORDERS_READ, ORDERS_WRITE, PAYMENTS_READ, INVOICES_READ, APPOINTMENTS_READ, APPOINTMENTS_WRITE

Supported objects

ObjectReadWriteNotes
New Order Yes No app webhook trigger declared by the pinned package.
Order Updated Yes No app webhook trigger declared by the pinned package.
New Customer Yes No app webhook trigger declared by the pinned package.
Customer Updated Yes No app webhook trigger declared by the pinned package.
New Appointment Yes No app webhook trigger declared by the pinned package.
New Payment Yes No app webhook trigger declared by the pinned package.
New Invoice Yes No app webhook trigger declared by the pinned package.

Triggers

New Order · Webhook

Triggered when a new order is created

Order Updated · Webhook

Triggered when an order is updated

New Customer · Webhook

Triggered when a customer is created

Customer Updated · Webhook

Triggered when a customer is updated

New Appointment · Webhook

Triggered when a new appointment is created

New Payment · Webhook

Triggered when a new payment is created

New Invoice · Webhook

Triggered when a new invoice is created

Setup

Setup

  1. Add the Square connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • No provider credential fields are declared by the pinned package.

OAuth scopes

  • MERCHANT_PROFILE_READ
  • CUSTOMERS_READ
  • CUSTOMERS_WRITE
  • ITEMS_READ
  • ITEMS_WRITE
  • ORDERS_READ
  • ORDERS_WRITE
  • PAYMENTS_READ
  • INVOICES_READ
  • APPOINTMENTS_READ
  • APPOINTMENTS_WRITE
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-square@0.4.6; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 0 actions and 7 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 0 exercised action entrypoints and 7 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Square connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-square@0.4.6 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com