rapidform / Documentation

Notifications

RapidForm can notify you whenever a new submission is received, via email or webhook.

Email Notifications

Default Behavior

By default, the workspace owner's email address receives a notification for every new submission. No configuration is needed — this works out of the box.

Custom Notification Emails (Pro/Business)

On Pro and Business plans, you can add additional email addresses to receive submission notifications:

  1. Go to your form's Settings tab.
  2. In the Notification Emails section, enter an email address and click Add.
  3. Add as many email addresses as you need.
  4. Click Save to apply.

When custom notification emails are configured, they replace the default owner email. Make sure to include the owner's email in the list if they should still receive notifications.

Email Content

Each notification email includes:

  • The form name
  • All submitted field data (labels and values)
  • Submission timestamp
  • Metadata (IP address, user agent, referrer)

Over-Limit Behavior

If you exceed your plan's monthly submission quota, notification emails change:

  • Instead of the full submission data, you receive an upgrade notification informing you that your quota has been reached.
  • The submission is still stored — no data is lost. You just won't see the details in the email until you upgrade or the next billing cycle begins.

Webhooks (Pro/Business)

Webhooks let you send submission data to external services in real time — perfect for integrating with Slack, Zapier, custom APIs, or any system that accepts HTTP POST requests.

Setting Up a Webhook

  1. Go to your form's Settings tab.
  2. Enter a Webhook URL in the webhooks section.
  3. Click Save.

The webhook fires for every new submission to that form.

How Webhooks Work

  • RapidForm sends an HTTP POST request to your URL.
  • The request body is JSON with Content-Type: application/json.
  • The request has a 10-second timeout. If your endpoint does not respond in time, the webhook silently fails (the submission is still stored).
  • Failed webhooks are logged but not retried.

Example Payload

{
    "form": {
        "id": 42,
        "name": "Contact Form",
        "slug": "contact-form-a1b2c3"
    },
    "submission": {
        "id": 156,
        "data": {
            "Name": "Jane Smith",
            "Email": "[email protected]",
            "Message": "I'd like to learn more about your services."
        },
        "metadata": {
            "ip": "192.168.1.1",
            "user_agent": "Mozilla/5.0...",
            "referrer": "https://example.com"
        },
        "submitted_at": "2026-03-24T14:30:00+00:00"
    }
}

Webhook Tips

  • Use a service like webhook.site to test your webhook URL before connecting a production endpoint.
  • Respond with a 2xx status code quickly. Heavy processing should be done asynchronously on your end.
  • The submission data keys match the field labels you configured in the form builder.
← Previous Analytics Next → Workspaces