Integrate Xero with FileMaker using webhooks
Needs changesWhat this workflow does
This workflow has 9 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects FileMaker.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Move Binary Data (Convert to/from binary data): uses Convert to/from binary data
- Set (Edit Fields (Set)): sets or maps fields
- Crypto: hashes or encrypts values
- If: checks a condition and branches into true / false
- Success (Respond to Webhook): sends the response back to the webhook caller
- Unauthorised (Respond to Webhook): sends the response back to the webhook caller
- Create webhook record (FileMaker): uses FileMaker
- Perform processWebhook script (FileMaker): uses FileMaker
Services it uses
Before you upgrade to n8n 3.0
1 thing in this workflow is removed in n8n 3.0. Fix it before you upgrade:
- Convert to/from binary data in Move Binary Data: replace with Convert to File or Extract from File.
Rather not rewrite it? Many of these flows can be rebuilt in Make (free plan).
| Removed in 3.0 | Replace with |
|---|---|
| Convert to/from binary data Move Binary Data | Convert to File or Extract from File |
Rarely used nodes in this template: n8n-nodes-base.filemaker
Nodes used (7)
- Crypto
n8n-nodes-base.crypto - Convert to/from binary data
n8n-nodes-base.moveBinaryData - Edit Fields (Set)
n8n-nodes-base.set - If
n8n-nodes-base.if - Respond to Webhook
n8n-nodes-base.respondToWebhook - FileMaker
n8n-nodes-base.filemaker - Webhook
n8n-nodes-base.webhook
From the author
Integrate Xero with FileMaker using Webhooks Workflow Description This n8n workflow automates the integration between Xero and FileMaker, allowing for seamless data transfer between the two platforms. By listening for webhooks from Xero (e.g., new invoices,…