Connecting Bridgo with Zapier

The Zapier Integration allows you to connect Bridgo with thousands of apps without writing custom code.

You can use Zapier to send data between Bridgo and tools like Google Sheets, Google Forms, Typeform, HubSpot, Shopify, WooCommerce, Calendly, Mailchimp, Stripe, and many other business applications.


📍 Where to Enable Zapier Integration #

Go to:

Settings → WhatsApp Settings → Integration → Zapier Integration

From this section, you can:

  • Enable or disable Zapier access
  • Generate a Zapier API key
  • Rotate an existing key
  • Revoke Zapier access
  • Copy the generated key

🔐 Before You Start #

Before connecting Zapier, make sure:

  • Zapier Integration is enabled in Bridgo.
  • Your subscription plan supports Zapier.
  • You have generated a Zapier API key.
  • You copied the API key when it was shown.
  • Your WhatsApp account is already configured and active.

Zapier uses the key as:

Authorization: Bearer <key>

The key is shown only once. If you lose it, rotate or generate a new one.


🔑 Step 1: Generate a Zapier API Key #

  1. Open WhatsApp Settings.
  2. Go to the Integration tab.
  3. Find Zapier Integration.
  4. Turn the integration on.
  5. Click Generate API Key.
  6. Copy the key immediately.
  7. Store it securely.

Important:

  • Keys are stored securely as a hash and a salt.
  • The original key cannot be viewed again later.
  • Rotating a key revokes the old key immediately.
  • Revoking a key disables Zapier access.

⚡ Step 2: Connect Bridgo in Zapier #

In Zapier:

  1. Create a new Zap.
  2. Search for the Bridgo app.
  3. Choose a trigger, action, or search.
  4. When Zapier asks you to connect an account, paste your Bridgo Zapier API key.
  5. Test the connection.

If the connection is successful, Zapier confirms that your Bridgo account is connected.

The connection test validates:

  • Company account
  • WhatsApp Business Account scope
  • Phone Number ID scope
  • API key authentication

🚀 Available Zapier Triggers #

Triggers start a Zap when something happens in Bridgo.

📨 New Incoming Message #

Trigger event:

message.received

Use this trigger when you want another app to react when a customer sends a WhatsApp message.

Example use cases:

  • Add incoming messages to Google Sheets
  • Create a CRM activity
  • Notify a Slack channel
  • Create a support ticket
  • Start an automation workflow

Trigger data may include:

  • Event ID
  • Event type
  • Occurred date/time
  • Company ID
  • WhatsApp Business Account ID
  • Phone Number ID
  • Contact number
  • Contact name
  • Message ID
  • Message type
  • Message text
  • Media URL
  • Message direction

👤 Contact Created or Updated #

Trigger event:

contact.created_or_updated

Use this trigger when you want Zapier to react when a Bridgo contact is created or updated.

Example use cases:

  • Add new contacts to a CRM
  • Add leads to Google Sheets
  • Sync contacts with email marketing tools
  • Send internal notifications when a lead is updated

Trigger data may include:

  • Contact ID
  • Contact name
  • WhatsApp number
  • Company ID
  • WhatsApp account details
  • Event timestamp

✅ Message Status Updated #

Trigger event:

message.status_changed

Use this trigger when you want another app to react when a WhatsApp message status changes.

Example use cases:

  • Track delivered or read status externally
  • Update CRM message records
  • Log campaign delivery status
  • Alert your team when delivery fails

Status changes can include WhatsApp delivery lifecycle updates, such as sent, delivered, read, or failed, depending on the message event received.


⚙️ Available Zapier Actions #

Actions let Zapier perform work inside Bridgo.


💬 Send Text Message #

Action endpoint:

send-text

Use this action to send a WhatsApp text message from a Zap.

Required fields:

  • Recipient phone number or business-scoped user ID
  • Message text

Optional/related fields:

  • Customer ID, when available

Use cases:

  • Send a follow-up message after a form submission
  • Notify a customer after a CRM stage change
  • Send internal workflow messages through WhatsApp

👤 Create or Update Contact #

Action endpoint:

contact-upsert

Use this action to create a new contact or update an existing contact.

Required fields:

  • Full name
  • Mobile number

Optional fields include:

  • Contact ID
  • Gender
  • Customer source
  • Address
  • Birth date
  • Contact label/type
  • Language
  • Email
  • Subscription status
  • Group IDs
  • Agent IDs

Use cases:

  • Add leads from forms
  • Sync CRM contacts into Bridgo
  • Update contact details from external systems
  • Assign contacts to groups or agents

🏷️ Update Contact Label #

Action endpoint:

contact-label-update

Use this action to assign or update a contact label.

Required fields:

  • Mobile number
  • Label ID

Use cases:

  • Mark a contact as a hot lead
  • Apply a customer type from CRM data
  • Segment contacts based on form answers

👥 Update Contact Group #

Action endpoint:

contact-group-update

Use this action to assign a contact to one or more groups.

Required fields:

  • Mobile number
  • Group IDs

Group IDs can be sent as multiple values.

Use cases:

  • Add contacts to campaign groups
  • Organize leads by source
  • Segment customers by product interest

📝 Add Contact Note #

Action endpoint:

contact-note

Use this action to add a note/comment to a customer profile.

Required fields:

  • Customer ID
  • Comment

Use cases:

  • Add CRM notes to Bridgo
  • Record form submission details
  • Add support context to a contact

👨‍💼 Assign Conversation #

Action endpoint:

conversation-assign

Use this action to assign a conversation/contact to an agent.

Required fields:

  • Customer ID
  • Assignment mode

Assignment modes:

  • Round-robin assignment
  • Direct assignment to a specific agent

For direct assignment, an Agent ID is required.

Use cases:

  • Assign high-value leads to sales agents
  • Route support requests to the right team member
  • Distribute incoming contacts automatically

📩 Send Transactional Template #

Action endpoint:

send-transactional-template

Use this action to send a configured transactional WhatsApp template.

Required fields:

  • Transactional ID
  • Mobile number or business-scoped user ID

Use cases:

  • Send order confirmations
  • Send appointment reminders
  • Send payment notifications
  • Send booking updates
  • Send system-generated alerts

🔍 Available Searches and Lookups #

Searches help Zapier find existing data in Bridgo or populate dropdowns during Zap setup.


🏷️ Contact Labels #

Search endpoint:

contact-labels

Returns available contact labels.

Use this when an action needs a label ID.


👥 Contact Groups #

Search endpoint:

contact-groups

Returns available contact groups.

Use this when an action needs one or more group IDs.


🔎 Find Contact by Phone #

Search endpoint:

contact

Searches for a contact using a phone number.

Returns:

  • Found status
  • Contact ID
  • WhatsApp number
  • Name
  • Email
  • Created date

Use this before adding notes, assigning conversations, or updating contact data.


💬 Find Conversation by Contact #

Search endpoint:

conversation

Searches for a conversation using a phone number.

Returns:

  • Found status
  • Conversation ID
  • Contact ID
  • Last message
  • Last message date
  • Conversation status

Use this when a Zap needs conversation context.


📄 Templates #

Search endpoint:

templates

Returns WhatsApp templates available in the account.

Returns:

  • Template name
  • Language
  • Status

👨‍💼 Agents #

Search endpoint:

agents

Returns active agents.

Use this when assigning conversations to a specific agent.

Returns:

  • Agent ID
  • Name
  • Email

📩 Transactionals #

Search endpoint:

transactionals

Returns active transactional notification configurations.

Use this when sending a transactional template from Zapier.

Returns:

  • Transactional ID
  • Transactional name

🧪 Example Zap Ideas #

Example 1: New Lead from Google Forms to Bridgo #

  1. Trigger: New Google Forms response
  2. Action: Create or Update Contact in Bridgo
  3. Action: Update Contact Group
  4. Action: Send Transactional Template

Example 2: Incoming WhatsApp Message to Slack #

  1. Trigger: New Incoming Message in Bridgo
  2. Action: Send Channel Message in Slack

Example 3: CRM Deal Won to WhatsApp Message #

  1. Trigger: Deal stage changed in CRM
  2. Search: Find Contact by Phone in Bridgo
  3. Action: Send Text Message or Send Transactional Template

Example 4: Contact Updated in Bridgo to Google Sheets #

  1. Trigger: Contact Created or Updated
  2. Action: Create or Update Row in Google Sheets

⚠️ Usage Limits #

Zapier actions and searches may count toward your monthly Zapier API request limits.

If the limit is reached, Zapier may receive a usage limit response, and the Zap may stop until capacity is available or the plan is upgraded.

Usage may apply to:

  • Monthly Zapier Action API Requests
  • Monthly Zapier Search API Requests

🔎 Common Issues #

Zapier Connection Fails #

Check that:

  • Zapier Integration is enabled.
  • The API key is correct.
  • The key was not revoked.
  • The key was copied without extra spaces.
  • Your plan supports Zapier.

API Key Was Lost #

Zapier keys are shown only once.

If the key is lost:

  1. Go to WhatsApp Settings → Integration.
  2. Rotate or generate a new Zapier API key.
  3. Update the connection in Zapier.

Zapier Says Integration Is Disabled #

Check that the Zapier Integration toggle is enabled in Bridgo.


Action Fails Because Required Fields Are Missing #

Check the selected action fields.

Common required fields include:

  • Mobile number
  • Message text
  • Customer ID
  • Label ID
  • Group ID
  • Transactional ID

Search Returns No Results #

Check that:

  • The contact exists in Bridgo.
  • The phone number format is correct.
  • Labels, groups, agents, or transactionals are already created.
  • The connected API key belongs to the correct company/account.

🧠 Best Practices #

  • 🔐 Store Zapier API keys securely.
  • 🔁 Rotate keys if a key is exposed.
  • ❌ Revoke keys no longer in use.
  • 🧪 Test each Zap before turning it on.
  • 📱 Use international phone number format where possible.
  • 🏷️ Use searches to select valid labels, groups, agents, and transactionals.
  • 📊 Monitor Zap history in Zapier for failed runs.
  • 📌 Keep Zapier Integration enabled only when actively used.
  • 🚦 Watch monthly usage limits for high-volume workflows.

✅ Summary #

The Zapier Integration connects Bridgo with external apps using triggers, actions, and searches.

You can trigger workflows from incoming WhatsApp messages, contact updates, and message status changes. You can also create or update contacts, send WhatsApp messages, assign conversations, update groups or labels, add notes, and send transactional templates.

Use Zapier when you want fast, no-code automation between Bridgo and your existing business tools.

What are your feelings

Updated on May 31, 2026