Webhooks and n8n

Use PayFacile webhooks to connect your store to n8n, Make, or any external tool. JSON format, configuration via workflows, and examples.

What is a webhook?

A webhook is an HTTP notification automatically sent by PayFacile to an external URL when an event occurs. Unlike an API where you query the server, a webhook pushes data to your tool in real time.

Webhooks let you connect PayFacile to any tool that accepts HTTP requests: n8n, Make, Zapier, your own server, a CRM, etc.

Send a webhook via workflows

Webhooks are sent via the Send a webhook action in workflows. To configure a webhook:

  1. Create a workflow in Marketing → Workflows.
  2. Choose a trigger (new order, payment received, etc.).
  3. Add the Send a webhook action.
  4. Enter the destination URL.

Payload format

The webhook sends an HTTP POST request with a JSON body containing the event’s contextual data:

  • Order data — ID, status, amount, product(s), date.
  • Customer data — name, email, customer ID.

The format is structured for easy consumption by any automation tool.

Integration with n8n

n8n is an open-source automation tool that accepts webhooks. To connect PayFacile to n8n:

  1. In n8n, create a workflow with a Webhook node as the trigger.
  2. Copy the n8n webhook URL.
  3. In PayFacile, create a workflow with the "Send a webhook" action and paste the n8n URL.

Each PayFacile event triggers the n8n workflow, which can then send data to Google Sheets, Slack, Notion, a CRM, or any other service connected to n8n.

Other compatible tools

The same approach works with Make (Integromat), Pipedream, Activepieces, or your own HTTP endpoint. Any tool capable of receiving a POST request with a JSON body is compatible.

FAQ

Is the webhook sent in real time?
The webhook is sent when the action executes in the workflow. If you added a delay before the webhook, it will be sent after that delay.
What happens if the destination URL does not respond?
If the destination server does not respond or returns an error, the webhook execution is marked as failed in the workflow run details.
Was this helpful?