Core

Notifications

Chirp Form can notify you when new submissions arrive using emails or webhooks. Notifications are configured per form, so you can tailor how each form alerts your team or systems.

Both notification types can be triggered on every new submission. Submissions belong to a form and each form manages its own notification settings.

Emails

Available on Lite plan and up

Email notifications send a message to the recipients you specify whenever a new submission is captured. Use this to keep teammates informed without logging into the dashboard.

How It Works

When a submission is created, Chirp Form sends an email to each configured address for that form. You control who receives these alerts by adding or removing recipients in the form’s notification settings.

Set Up

  1. Go to the form edit page (click Edit in the top-right).
  2. Open the dropdown and choose Notifications (Email).
  3. Review the list of existing notifications. Select an item to edit it or click the trash icon to delete.
  4. To add a new notification, click New in the top-right and enter a valid email address.
  5. Save your changes. New submissions will now trigger emails to the listed recipients.

Webhooks

Available on Starter and Pro

Webhooks send an HTTP POST to your endpoint when a submission is created. Use this to automate workflows, sync data or trigger downstream systems.

How It Works

When a submission is created, Chirp Form posts the submission payload to each configured webhook URL for that form.

Set Up

  1. Go to the form edit page (click Edit in the top-right).
  2. Open the dropdown and choose Webhooks.
  3. Review the list of existing webhooks. Select an item to edit it or click the trash icon to delete.
  4. To add a new webhook, click New in the top-right.
    • Enter a name (make it easily identifiable).
    • Enter the URL endpoint that will receive the POST requests.
  5. Save your changes. New submissions will now trigger POSTs to your endpoints.

Security

Each webhook request includes an X-Webhook-Signature header. Use this signature to verify the request came from Chirp Form before processing it. Your server should reject requests with missing or invalid signatures.