Connect an Activity Messenger form to Zapier

Activity Messenger does not have a native Zapier app, but a form can trigger a Zap through its outgoing webhook. Activity Messenger sends the completed form submission to a Webhooks by Zapier Catch Hook URL.

Before you begin

You need:

  • Permission to edit the Activity Messenger form.
  • A Zap with Webhooks by Zapier as its trigger.
  • A form or payment form. Contract forms do not expose the webhook option.

Treat the Zapier Catch Hook URL as a secret. Anyone with the URL can send data to the Zap.

Create the Zapier trigger

  1. Create or open a Zap.
  2. Select Webhooks by Zapier for the Trigger step.
  3. Select Catch Hook as the event.
  4. Continue to the Test tab and copy the webhook URL.

Use Catch Hook, not Retrieve Poll. Activity Messenger sends an HTTP POST with a JSON request body.

Add the webhook to the form

  1. In Activity Messenger, open the form you want to connect.
  2. Select the Options tab.
  3. In the Confirmation section, enable Enable webhook.
  4. Paste the Zapier Catch Hook URL into the webhook URL field.
  5. Click Save.
Enable the outgoing webhook in the form's Options and Confirmation settings

The setting belongs to this form. Repeat these steps for every form that should trigger a Zap.

Test and finish the Zap

  1. Keep Zapier's trigger test open.
  2. Complete and submit a new test response in the Activity Messenger form.
  3. For a payment form, complete the payment-form workflow.
  4. Return to Zapier and test the trigger.
  5. Map the received fields to the actions in your Zap.
  6. Test the actions, then publish the Zap.

The payload includes:

  • id
  • email
  • mobile
  • first_name
  • last_name
  • created_at
  • form_answers

form_answers contains the answers collected by the form. Submit a realistic test response so Zapier can discover the answer fields you plan to use.

Important behavior and limits

  • The webhook is sent after a completed form submission. Payment forms send it after the form's invoice processing is finalized.
  • Activity Messenger sends the webhook in the background, so the respondent does not wait for Zapier to finish.
  • A form stores one webhook URL.
  • Contract forms do not show the webhook setting.
  • Activity Messenger does not sign the request or add a custom authentication header. Keep the unguessable Catch Hook URL private.
  • If Zapier changes the Catch Hook URL, update the URL in the Activity Messenger form.

Example

To add every registration to a spreadsheet, create a Catch Hook trigger, paste its URL into the registration form, and submit a test registration. In the next Zap step, map first_name, last_name, email, and the required form_answers values to spreadsheet columns.

Related resource