Once your Company is connected to Zapier, Final can automatically send data to Zapier whenever certain events occur. These are known as trigger events. Each event type sends a specific payload structure that you can use in your Zap to drive automations in other platforms.
The following triggers are supported:
Customer Created
Triggered when a new customer is created in Final. Includes name, contact information, billing/shipping addresses, and metadata.
Customer Updated
Triggered when an existing customer is edited in Final.
Product Created
Triggered when a new product is created. Payload includes product name, price, image URL, category, options, SKU, and tax class.
Product Updated
Triggered when an existing product is updated.
Product Deleted
Triggered when a product is removed from the Company.
Stock Changed
Triggered any time inventory changes for a product, including via:
sales in the Station App
bulk stock adjustments
manual counts in Manage
adjustments via a flow
The payload includes before/after counts, adjustment reason, and source Outlet.
Order Created
Triggered when a new order is placed from the Station App or API. Includes customer, line items, prices, taxes, and payment methods.
Order Updated
Triggered when an existing order is modified (e.g. after being Parked and resumed, or after refund).
Order Refunded
Triggered when a full or partial refund is processed.
Session Closed
Triggered when a register session is closed. Payload includes total sales, taxes, tips, payment method breakdowns, and refunds for the session.
Custom Event: “Run automation in Zapier” action
This trigger is used when a checkout flow includes the Run automation in Zapier action. It allows you to trigger a Zap mid-flow and send a snapshot of the current flow context. This includes all open orders, customer information, user metadata, and any additional inputs collected earlier in the flow.
See: “Final POS → Zapier: Payload Structure (Custom Event) for the full structure.
