FlourivateHelp Center

Connect another app with webhooks

Last reviewed October 21, 2026

An overview of inbound and outbound webhooks in workflows, for when a developer or a tool like Zapier is helping you.

A webhook lets another app talk to Flourivate. An inbound webhook lets another system start one of your workflows (and create the contact). An outbound webhook sends contact details from a workflow to another system. You'll rarely set these up alone; this page tells you enough to work with whoever is helping.

Before you start

  • You'll need the other app's webhook details, or a developer.
  • Treat a webhook address like a password. Anyone who has it can send data into your workflow.

Steps

Start a workflow from another app (inbound)

  1. Create a workflow and choose the Inbound Webhook trigger.
  2. Click the trigger card. Copy the Webhook URL and give it to your developer or paste it into the other app.
  3. Leave the Webhook Intake Policy switches off unless your developer asks otherwise. They block empty or unusable requests.
  4. Optional: add a shared secret under Webhook Source Authentication (Required header name and Required header value / secret). Requests without it are logged but don't create contacts.
  5. Use Smart Contact Creation and the field mapping so the email and phone in the incoming data create or update the right contact.
  6. Have your developer click Send Test POST or send a test from their system, then check Event Debugger for the event.
  7. Add the rest of your steps, Save, and switch to Active.

Send data to another app (outbound)

  1. In a workflow, add the Outbound Webhook action ("Send data to external URL").
  2. Set the Method (usually POST) and paste the other app's URL.
  3. In Body, choose JSON and map the fields to send, for example contact_email as {{contact.email}}.
  4. Save and test with your own contact.

Workspace-wide webhooks

To send events from your whole workspace (not one workflow) to another system, a developer can use Settings > API & Webhooks > Webhooks. That's separate from workflow webhooks. See API keys and webhooks.

Check it worked

  • The test event appears in Event Debugger with status Processed.
  • A test contact appears in Contacts with the mapped fields filled in.

If something's off

  • The event arrives but no contact is created: check the field mapping for email or phone, and the shared secret if you set one. If it stopped working right after you saved new field mappings, tell us and we'll look into it.
  • The webhook stopped working after someone clicked Regenerate URL: the old address no longer works. Paste the new one into the other app.
  • Nothing arrives at all: the other app is sending to the wrong address, or the workflow is a draft. See Find out why a workflow didn't run.

Related