No-Code Automation

Island Pulse is just a webhook: any no-code tool that can send an HTTP POST can drive it. Island Pulse also accepts common field aliases (body, text, description) so you don’t always need to transform the payload.

Accepted field aliases

When a no-code tool sends a field with a different name, Island Pulse looks for the first non-empty value in this list as the main message:

message → body → text → msg → description → detail → alertBody

This means if Zapier sends {"body": "Build passed"}, it works without any field mapping.

Zapier: Webhooks by Zapier

1. Create a new Zap and set your trigger (e.g., Stripe charge, uptime alert, form response).

2. Add an action: “Webhooks by Zapier” → POST.

3. Configure the action:

Field	Value
URL	`https://api.islandpulse.dev/notify`
Payload Type	`JSON`
Headers	`Authorization: Bearer <token from Island Pulse home screen>`
Data	See below

The token is the secret ID shown in the app — send it only as a Bearer header, not in the URL.

4. Add JSON fields in Data:

job_id      → your-zap-job
layout      → default
message     → (map from trigger, e.g. "{{email_subject}}")
status      → running
accentColor → #00CFFF

5. Turn on the Zap and test on a physical iPhone. The first run starts a Live Activity; later runs with the same job_id update it.

Example: Notify on new Stripe payment

Trigger: Stripe → New Charge

Key	Value
job_id	`stripe-payment`
title	`Payment`
metric	mapped charge amount
message	`New payment from {{customer_name}}`
status	`success`
accentColor	`#34C759`
icon	`creditcard.fill`

Make (Integromat): HTTP module

1. Create a new Scenario and add your trigger module.

2. Add a new module: search for HTTP → Make a request.

3. Configure:

Field	Value
URL	`https://api.islandpulse.dev/notify`
Method	POST
Headers	`Authorization: Bearer <token>`
Body type	Raw
Content type	JSON (application/json)
Request content	JSON payload (see below)

4. Build your payload in the Request content field. You can reference trigger data with Make’s {{variable}} syntax:

{
  "job_id": "make-automation",
  "layout": "default",
  "message": "{{1.subject}}",
  "status": "running",
  "accentColor": "#AA88FF"
}

5. Run the scenario once to test, then schedule it.

n8n: HTTP Request node

In n8n, add an HTTP Request node with:

Method: POST
URL: https://api.islandpulse.dev/notify
Header: Authorization: Bearer <token>
Body Content Type: JSON
Body:

{
  "job_id": "n8n-workflow",
  "message": "={{ $json.message }}",
  "status": "running"
}

Tips for no-code integrations

Ending activities from no-code: When you want to dismiss the activity (e.g., the workflow completed), add a second HTTP step at the end with "action": "end":

{
  "job_id": "your-job",
  "action": "end",
  "message": "Workflow complete"
}

Error branches: Most no-code tools have an error path. Add a parallel HTTP step on the error branch that posts "status": "failed" so you see failures on your Lock Screen.

Multiple steps: If your workflow has multiple steps, post a running update at each step with an updated message and progress value. The same job_id means all updates go to the same Live Activity.