Make (Integromat) Integration
Receive Swft order events in Make and route them through any visual automation scenario.
Setup — Webhooks module
Section titled “Setup — Webhooks module”- In Make, create a new scenario
- Add a Webhooks → Custom webhook trigger module
- Click Add to create a new webhook and copy the URL — it looks like:
https://hook.eu1.make.com/abc123xyz
- Register this URL as a Swft subscription by calling the API (you can do this from Make using an HTTP module, or from any API client):
POST https://api.swft.co.uk/merchants/zapier/subscribex-swft-api-key: YOUR_API_KEYContent-Type: application/json
{ "target_url": "https://hook.eu1.make.com/abc123xyz", "event": "order.completed", "provider": "make"}Available events: order.completed, order.failed, cart.abandoned, refund.issued
- Click Run once in Make, then complete a test order in Swft to send a sample payload
- Make will detect the payload structure and map all fields automatically
Determining the payload structure
Section titled “Determining the payload structure”If you need Make to learn the structure before a real event fires, use the sample endpoint:
GET https://api.swft.co.uk/merchants/zapier/sample/order.completedx-swft-api-key: YOUR_API_KEYThis returns an array containing one sample payload with all fields populated.
Unregistering
Section titled “Unregistering”When you deactivate a scenario, remove the subscription:
DELETE https://api.swft.co.uk/merchants/zapier/unsubscribex-swft-api-key: YOUR_API_KEYContent-Type: application/json
{ "target_url": "https://hook.eu1.make.com/abc123xyz" }Sample scenario — Order completed → Google Sheets row
Section titled “Sample scenario — Order completed → Google Sheets row”::: v-pre
| Step | Module | Config |
|---|---|---|
| 1 | Webhooks → Custom webhook | Listens for order.completed |
| 2 | Tools → Set variable | order_total = {{1.data.total_pence / 100}} |
| 3 | Google Sheets → Add a row | Map fields from step 1 |
Useful field mappings:
| Google Sheets column | Make expression |
|---|---|
| Order ID | {{1.data.order_id}} |
| Customer name | {{1.data.customer.first_name}} {{1.data.customer.last_name}} |
{{1.data.customer.email}} | |
| Total | {{1.data.total_pence / 100}} |
| Currency | {{1.data.currency}} |
| Payment method | {{1.data.payment_method}} |
| Country | {{1.data.shipping_address.country}} |
| Created | {{1.created_at}} |
| ::: |
HTTP module (alternative — polling or one-off)
Section titled “HTTP module (alternative — polling or one-off)”For workflows that need to pull data on a schedule rather than receive events:
| Field | Value |
|---|---|
| URL | https://api.swft.co.uk/merchants/analytics?range=7d |
| Method | GET |
| Headers → Name | x-swft-api-key |
| Headers → Value | Your merchant API key |
| Parse response | Yes |
Payload reference
Section titled “Payload reference”See the Zapier integration page for the full payload field reference — the payload shape is identical across all integrations.