Skip to Content

Webhooks

Send real-time notifications to your ERP, CRM or automation when orders, quotes, customers, part specifications and carts change in Phasio.

Available to manufacturers on Startup, Pro and Factory Floor plans

A webhook is an automated HTTP notification Phasio sends to a URL you choose when a specific event happens in your account, such as a new order or an updated customer organisation. Phasio sends an encrypted POST request to your endpoint as the event happens, so external systems like ERPs, CRMs or your own automation stay in sync without polling.

Webhooks are for Phasio calling your systems. To have your systems call Phasio, use an API key with the Manufacturer API.

How it works

  • One event per webhook. Each webhook has a single trigger (event type) and a single URL. To receive several events, add a webhook for each.
  • Encrypted and signed. Each webhook gets its own secret. Phasio encrypts every payload with AES-256-GCM using that secret and signs the request with HMAC-SHA256, so your endpoint can check the request came from Phasio before decrypting it.
  • Fire and forget. Webhooks are delivered asynchronously: Phasio doesn't wait for your endpoint before carrying on. Requests time out after 5 seconds, and failed deliveries are not retried, so make sure your endpoint is reliable and responds quickly.
  • Full state, not a diff. Payloads carry the current state of the order, customer organisation or cart, not what changed.

Add a webhook

  1. Navigate to Developers from the main sidebar.
  2. Click Add Webhook.
  3. Select a Trigger: the event type that should fire the webhook.
  4. Enter the URL of the endpoint that should receive the notification. The URL must use https:// and point to a valid, publicly reachable domain. Private, loopback, and link-local addresses are rejected.
  5. Click Add to save the webhook.

Phasio then generates a unique secret for the webhook, a Base64 URL-safe encoded AES-256 encryption key. To copy it, open the actions menu (⋯) for the webhook in the webhooks table and click Copy Secret. Give it to whoever builds your endpoint.

Treat the secret like a password. Store it securely and never expose it in client-side code or public repositories.

To verify and decrypt requests, your developer follows Verifying and decrypting the payload, which has a Node.js example.

Delete a webhook

  1. In the webhooks table, open the actions menu (⋯) for the webhook.
  2. Click Delete. Phasio stops sending requests to that endpoint immediately.

Events

EventTriggerFires when
Order CreatedORDERA new order is created or committed.
Order UpdatedORDER_UPDATEDAn order's details, status, payment status, or Kanban column changes.
Quote ConvertedQUOTE_CONVERTEDA quote is accepted or paid, converting it into a confirmed order.
Customer Organisation CreatedCUSTOMER_ORGANISATION_CREATEDA new customer organisation is created.
Customer Organisation UpdatedCUSTOMER_ORGANISATION_UPDATEDA customer organisation's details are modified.
Part Specification CreatedSPECIFICATION_CREATEDA new part specification is created.
Cart CreatedCART_CREATEDA new cart is created on the storefront.
Cart UpdatedCART_UPDATEDA customer adds, changes or removes a cart item, or otherwise changes a storefront cart. Carries the whole cart with prices.
Customer CommentedCUSTOMER_COMMENTEDA customer posts a comment on an order or quote.
Manufacturer CommentedMANUFACTURER_COMMENTEDYour team posts a comment visible to the customer. Internal comments don't fire it.

Each event page has the full payload schema and the exact trigger conditions.

Which event to use

  • React to new orders: subscribe to Quote Converted. It fires once when a quote becomes a confirmed order, whether the customer accepts it, pays online, or pays by purchase order or invoice, and also when you create a direct order. That makes it a safe trigger for ERP sync, CRM updates or fulfilment.
  • Keep an order mirrored in another system: subscribe to Order Updated, the most frequent event. It covers quote edits, status and Kanban column moves, shipping changes, and archiving.
  • Keep customer records in sync: subscribe to Customer Organisation Created and Customer Organisation Updated.
  • Follow abandoned or in-progress carts: subscribe to Cart Created and Cart Updated.

What order payloads include

Order webhooks carry the order's parts, pricing, expenses, shipping and production steps, plus:

  • the order's custom reference, so you can tie a Phasio order to an internal PO number or ERP identifier
  • the thread ID of the order's conversation, which you can read through the Manufacturer API
  • only current expenses: deleted expenses are left out

Last updated on

On this page