🔌Zapier & Make

Zapier and Make (Integromat) let you connect OnRaven to thousands of other apps — CRMs, spreadsheets, email, forms, and more — without writing code. You create webhooks in OnRaven, then build Zaps or Make scenarios that send or receive data when something happens (e.g. new conversation, user choice, or external event).

This page covers:

• How to set up Zapier and Make in OnRaven

• Using Zapier and Make nodes in the Workflow Builder

• Automation rules (what happens when data arrives at a webhook)

• Recipe examples you can copy and adapt

---

How to open Zapier or Make

In the left sidebar, click Integrations. Find Zapier or Make and click Connect (or Manage if already connected). You’ll see:

• Webhooks — The endpoints that receive or send data. Create one per “trigger” or “action” (e.g. “New lead from form”, “Send conversation to CRM”).

• Automation rules (Zapier/Make) — Rules that run when data hits a webhook: create contact, create lead, move lead stage, add tags, add to audience, send broadcast, send message.

---

Set up a webhook

1. Go to Integrations → Zapier (or Make).

2. Click Add webhook (or Create webhook).

3. Give it a name (e.g. “Landing page leads”, “Order notification”).

4. Copy the Webhook URL and, if shown, the API key or secret.

5. In Zapier or Make, create a Zap/Scenario that uses Webhooks by Zapier or Webhooks (Make) and paste this URL as the destination.

Each webhook has a unique URL. Use one URL per use case so you can attach automation rules to the right webhook.

---

Zapier / Make node in the Workflow Builder

You can use a Zapier or Make node inside a bot flow in two ways:

Mode	What it does
Outbound	When the flow reaches this node, it sends a payload (conversation ID, contact name, custom fields, etc.) to the webhook you select. Use this to “notify” Zapier/Make that something happened (e.g. user chose “Book demo”).
Inbound	The flow pauses at this node until someone (e.g. a Zap or Make scenario) POSTs data to your webhook. When data arrives, the flow continues and you can use the received data in the next nodes.

Configuration: Select the Webhook (created in Integrations), add Payload fields (for outbound) with variables like {{client.name}}, {{customFields.answer}}, and set an Output field to store the response or inbound data. See Configure each bot node – Zapier & Make for all fields.

---

Automation rules (when data arrives)

When data is POSTed to a Zapier or Make webhook, automation rules can run before or alongside your bot. You define rules in Integrations → Zapier (or Make) → Rules (or Automation rules).

Each rule has:

• Name — e.g. “Create contact when lead arrives”

• Webhook — Which webhook this rule applies to (or “any webhook”)

• Filters — Optional: only run if payload has certain fields/values (e.g. source equals landing_page)

• Action — What to do with the payload

Available actions (recipes):

Action	What it does	Example use
Create contact	Creates or updates a contact in OnRaven (name, email, phone, tags, custom fields).	Form submit → create contact; Zapier “New Row in Google Sheet” → create contact.
Update contact	Updates an existing contact (e.g. add tags, change custom fields).	CRM update → sync to OnRaven contact.
Create lead	Creates a lead in Leads Manager (optional pipeline/stage).	Form or ad → create lead.
Move lead stage	Moves a lead to a different stage (e.g. Qualified → Won).	CRM stage change → move lead in OnRaven.
Add tags	Adds tags to a contact.	Survey response → tag “interested”.
Add to audience	Adds the contact to a broadcast audience.	Signup → add to “Newsletter” audience.
Send broadcast	Sends a broadcast message (template) to the contact.	Welcome series; one-off notification.
Send message	Sends a message into an existing conversation (e.g. via conversation ID in payload).	External system → inject a reply into a chat.

You can map payload fields to action parameters (e.g. email → contact email, {{attendee}} → name). Use field mapping and filter conditions so the right rule runs for the right payload.

---

Recipe examples

1. Form or landing page → Create contact + add to audience

Goal: When someone submits a form (e.g. Typeform, Google Forms, your site), create a contact in OnRaven and add them to an audience.

1. OnRaven: Integrations → Zapier → Create webhook (e.g. “Form submits”).

2. Zapier/Make: Trigger = your form (e.g. “New Typeform Response”). Action = Webhooks – POST to your OnRaven webhook URL. Body: { "name": "{{name}}", "email": "{{email}}", "phone": "{{phone}}" } (use the field names your form provides).

3. OnRaven: Add an Automation rule for that webhook: Action = Create contact; map name, email, phone from the payload. Add a second rule (or second action if supported): Add to audience → choose your “Newsletter” or “Leads” audience.

Variation (Make): Same idea in a Make scenario: Form module → Webhook module (POST to OnRaven). In OnRaven, the same rules run when the webhook receives the data.

---

2. Bot choice → Send to Zapier/Make (outbound node)

Goal: When the user selects “Book a demo” in the bot, send their contact info and choice to Zapier so a Zap can create a calendar event or CRM deal.

1. OnRaven: Integrations → Zapier → Create webhook (e.g. “Demo request”).

2. Workflow Builder: In your bot, add a Zapier node after the Options node where the user picks “Book a demo”. Mode = Outbound. Select the “Demo request” webhook. Payload fields: e.g. contact_name = {{client.name}}, email = {{client.email}}, choice = demo.

3. Zapier: Create a Zap: Trigger = Webhooks – Catch Hook (use the same webhook URL). Actions = e.g. “Create Google Calendar event” or “Create deal in HubSpot” using the payload fields.

---

3. Inbound webhook → Resume bot with external data

Goal: The bot asks for “approval”; an external system (or human) POSTs approval to a webhook, and the bot continues with a “You’re approved” message.

1. Workflow Builder: Add a Zapier (or Make) node. Mode = Inbound. Enable Wait for inbound. Copy the webhook URL shown.

2. Connect the node to the next step (e.g. Send Message: “You’re approved!”).

3. When the flow runs, it stops at this node. Your external system (or a Zap/Make “Webhooks – POST”) sends data to that URL. OnRaven receives it and continues the flow; you can use the payload in custom fields or the next node.

---

4. New lead in CRM → Create lead + send WhatsApp message

Goal: When a new lead is created in your CRM (e.g. HubSpot, Pipedrive), create a lead in OnRaven and optionally send a WhatsApp message.

1. OnRaven: Integrations → Zapier → Create webhook (“CRM new lead”).

2. Zapier: Trigger = “New Lead in HubSpot” (or your CRM). Action = Webhooks – POST to the OnRaven webhook. Body: lead name, email, phone, stage, etc.

3. OnRaven: Automation rule for that webhook: Action = Create lead (map fields). Optional: second rule Send message (if you have conversation ID) or use Send broadcast with a template to the contact’s phone.

---

5. Notion Database → Create lead via Make HTTP request

Goal: When a new row is added to a Notion database (e.g. a lead tracker), send the data to an OnRaven leads webhook using Make's HTTP – Make a request module.

Notion property types and how to map them:

Notion type	Example property	Make mapping
Rich text array	Name, Source, Location	{{6.properties_value.Name[].plain_text}}
Email	Email	{{6.properties_value.Email}}
Phone	Phone	{{6.properties_value.Phone}}
Number	Score	{{6.properties_value.Score}}
URL	Website, Instagram	{{6.properties_value.Website}}
Select	Segment, City, Status	{{6.properties_value.Segment.name}}
Date	Date Added	{{6.properties_value.Date Added.start}}

Note: Property names that contain spaces must be wrapped in backticks inside the Make expression — e.g. {{6.properties_value.`Recommended Opener`[].plain_text}}.

HTTP request body (paste into Make's Body field, set type to application/json):

{
  “name”: “{{6.properties_value.Name[].plain_text}}”,
  “email”: “{{6.properties_value.Email}}”,
  “phone”: “{{6.properties_value.Phone}}”,
  “source”: “{{6.properties_value.Source[].plain_text}}”,
  “score”: “{{6.properties_value.Score}}”,
  “customFields”: {
    “instagram”: “{{6.properties_value.Instagram}}”,
    “website”: “{{6.properties_value.Website}}”,
    “location”: “{{6.properties_value.Location[].plain_text}}”,
    “recommendedOpener”: “{{6.properties_value.`Recommended Opener`[].plain_text}}”,
    “segment”: “{{6.properties_value.Segment.name}}”,
    “city”: “{{6.properties_value.City.name}}”,
    “country”: “{{6.properties_value.Country.name}}”,
    “status”: “{{6.properties_value.Status.name}}”,
    “whyOnraven”: “{{6.properties_value.`Why OnRaven`[].plain_text}}”,
    “dateAdded”: “{{6.properties_value.`Date Added`.start}}”,
    “_displayNames”: {
      “instagram”: “Instagram”,
      “website”: “Website”,
      “location”: “Location”,
      “recommendedOpener”: “Recommended Opener”,
      “segment”: “Segment”,
      “city”: “City”,
      “country”: “Country”,
      “status”: “Status”,
      “whyOnraven”: “Why OnRaven”,
      “dateAdded”: “Date Added”
    }
  }
}

Steps:

1. Make: Add a Notion – Watch Database Items trigger pointing to your database.

2. Make: Add an HTTP – Make a request module. Set:

   • URL → your OnRaven leads webhook URL (from Integrations → Leads Webhooks)

   • Method → POST

   • Headers → x-api-key: <your webhook API key>

   • Body type → application/json

   • Body → paste the JSON above and adjust property names to match your Notion columns.

3. Fields mapping directly to the lead (name, email, phone, source, score) are auto-detected. Everything inside customFields is stored as structured data on the lead and visible in the lead detail view.

---

6. Move lead stage (e.g. “Won”) → Notify or tag contact

Goal: When a deal is marked “Won” in your CRM, move the lead in OnRaven and add a tag or send a message.

1. OnRaven: Webhook + rule: Action = Move lead stage. Map payload fields to pipeline/stage (e.g. stage → “Won”).

2. Optional: Add Add tags rule (e.g. tag “customer”) or Send broadcast with a “Thank you” template.

---

API Transaction Logs

To debug webhooks (e.g. “Why didn’t my Zap trigger?” or “What payload did we get?”), use API Transaction Logs (sidebar). Filter by Provider = Zapier or Make and by time range. Open a request to see the request body, response status, and response body. See API Transaction Logs.

---

Troubleshooting

Problem	What to try
Webhook not firing	Check that the Zap/Make scenario is on and the URL is correct. In API Transaction Logs, confirm that requests are reaching OnRaven (filter by Zapier/Make).
Rule doesn’t run	Check filter conditions on the rule — the payload must match. Check that the rule is Active and tied to the right webhook.
Wrong data in contact/lead	In the rule, check field mapping: payload keys (e.g. email, name) must match what you send. Use the same keys in your Zap/Make POST body.
Bot node “no webhook”	Create the webhook in Integrations first, then select it in the Zapier/Make node.

---

For the exact configuration of each node (fields, variables), see Configure each bot node (Zapier, Make, OpenTable, Calendly). For a list of all integrations, see Integrations.