All integrations

n8n

Trigger notifications and Live Activities from any n8n workflow.

LiveWebhooksigned URL

n8n is a workflow automation platform that can connect hundreds of services. Its HTTP Request node sends HTTP requests directly, making it a straightforward way to push notifications or start Live Activities with Chirp.

You can trigger Chirp from any n8n workflow — after a database backup completes, when a form is submitted, when an RSS feed updates, or at the end of any multi-step automation.

Prerequisites

  • An n8n instance (cloud or self-hosted).
  • A Chirp account and webhook URL from your dashboard.

Setup

  1. 1

    Grab your Chirp webhook URL

    In the Chirp dashboard, copy your inbound webhook URL. It looks like https://api.chirpapp.dev/v1/webhooks/inbound?key=YOUR_KEY.

  2. 2

    Add an HTTP Request node

    In your n8n workflow, add an **HTTP Request** node wherever you want the notification to fire. Set the method to POST and paste your Chirp webhook URL.

  3. 3

    Configure the JSON body

    Enable **Send Body**, set **Body Content Type** to JSON, then add the fields you want to send. At minimum, add title and body. For notifications, that's all you need.

    shell
    # Notification (one-shot push):
{
  "title": "Workflow complete",
  "body": "Daily report generated and emailed"
}

# Live Activity (persistent card on lock screen):
# POST to /v1/activity/start instead:
{
  "schema_id": "@deploy",
  "data": {
    "title": "n8n deploy",
    "status": "running"
  }
}
  4. 4

    (Optional) Use expressions for dynamic content

    n8n expressions let you pull values from previous nodes into the body. For example, set body to ={{ $json.status }} to forward a result from an earlier step. This is useful for passing build times, error messages, or row counts.

What you’ll see

A push notification on your lock screen with the title and body you configured. If you used the activity endpoints instead, a persistent Live Activity card that updates as your workflow progresses.

Troubleshooting

Node returns 401 Unauthorized.
The webhook key in the URL is wrong or expired. Copy a fresh URL from the Chirp dashboard.
Notification doesn't arrive but the node succeeds.
Check the Chirp dashboard activity log. The request may have been accepted but the device push token is stale — re-open the Chirp app on your phone to refresh it.
External docs →
Browse all integrations