Custom Webhook AI Integration: How It Works and How to Connect It
The Custom Webhook AI integration lets MessageMind's AI agent read live Custom Webhook data and reply across WhatsApp, SMS, Instagram, email and web chat.
The Custom Webhook AI integration connects Custom Webhook to MessageMind so an AI agent can read live context and reply across every channel your customers use. The Custom Webhook trigger starts a campaign whenever another tool you use sends a contact's details to a URL that MessageMind gives you. You won't find it on the Integrations page: you pick it as the trigger when you build a campaign under Campaigns in the Workspace.
What is the Custom Webhook AI integration?
The Custom Webhook trigger starts a campaign whenever another tool you use sends a contact's details to a URL that MessageMind gives you. You won't find it on the Integrations page: you pick it as the trigger when you build a campaign under Campaigns in the Workspace. Each request finds the contact by phone number or email, or creates them, and starts the campaign for that person. A Custom Webhook goal has its own URL and moves someone who is already in the campaign on to the step after the goal.
You can see every supported integration on the MessageMind integrations page, and the full technical reference for this one lives in the Custom Webhook documentation. If you prefer to see it in action first, book a demo and we will walk you through the live flow.
What the Custom Webhook integration can do
The Custom Webhook AI integration ships with the following capabilities out of the box:
- Start a campaign from any tool that can send a request to a URL with a header of your choice, for example Zapier, Make or your own code.
- Find the contact by phone number or email, or create a new contact when there's no match.
- Fill in the contact's company from companyName when their record doesn't have one yet.
- Save the extra values you send as custom fields on the contact. They're available as variables, such as {{order_id}}, in messages and in conditions.
- Move someone who is already in the campaign straight to the step after a Custom Webhook goal when your tool calls that goal's URL.
- Reuse values from a goal request, such as an order number, in the steps after the goal.
Data read and written
The Custom Webhook AI integration touches a scoped set of fields. Here is exactly what moves between the two systems:
| Direction | What it covers |
|---|---|
| Read | name, phone, email and companyName from each request sent to the trigger URL. |
| Read | The custom field values your tool sends inside customFields. |
| Read | On a goal URL, the phone or email that identifies the contact, plus the fields you list under Variables from this webhook. Anything else in a goal request is ignored. |
How to set up the Custom Webhook AI integration
Setup takes a few minutes once your Custom Webhook account is live. The outline:
- Click Workspace in the top bar, then click Campaigns in the left rail.
- Click Create campaign, type a Campaign name, keep Create an Automation selected and click Create. The new campaign opens in the editor.
- Click Add a Trigger. In the Choose a trigger window, click Custom Webhook under Webhook. The Configure trigger window opens.
- Click Copy next to Webhook URL and paste the URL into your other tool as the address to send to.
- Set your tool to send a POST request with the content type application/json.
- Back in MessageMind, click Copy next to Secret token.
The step-by-step walkthrough, including every button and field, is in the Custom Webhook documentation.
Limitations to know
The Custom Webhook integration ships with a deliberately scoped surface. These are the limits worth knowing before you depend on it:
- The URL only accepts requests while the campaign is Published, so you can't try it from your tool on a Draft. Use your own contact details for the first test.
- A request is refused if it has no name, or if it has neither a phone number nor an email address. Goal requests only need the phone or the email.
- Phone numbers have to be valid. Send them with + and the country code, as in the sample. A number without a country code is read as a number from your account's country.
- Data only goes one way. Your tool gets a short reply saying whether the request was accepted, and MessageMind sends nothing else back to it.
- A goal's URL only works in campaigns that start with the Custom Webhook trigger.
Pricing and plan availability
The Custom Webhook AI integration is available on MessageMind's paid plans. The MessageMind pricing page lists which plan is required and what each tier includes. There is no extra per-integration fee; the connection is part of your account.
Frequently asked questions
What is the Custom Webhook AI integration?
The Custom Webhook AI integration is the native connection between Custom Webhook and MessageMind. Once connected, the AI agent can read live Custom Webhook context during a conversation and act on it (for example answering a stock question, booking an appointment or updating a contact) across WhatsApp, Instagram, SMS, email and web chat.
How do I connect Custom Webhook to MessageMind?
Open Connections in your MessageMind dashboard, find Custom Webhook and follow the connect flow. The full step-by-step with every field label and screenshot is in the Custom Webhook documentation.
How does authentication work for the Custom Webhook integration?
Your tool sends the campaign's Secret token in a header named X-Webhook-Token with every request. There's no sign-in and no account link between MessageMind and the other tool. MessageMind stores these credentials encrypted at rest and uses them only server-side, so they never reach the browser or any third party.
What does the AI agent do once Custom Webhook is connected?
It works with live Custom Webhook data during the conversation. The first capability in the Custom Webhook documentation reads: "Start a campaign from any tool that can send a request to a URL with a header of your choice, for example Zapier, Make or your own code." The full list, with every field the integration reads and writes, is in the documentation.
Your tool gets the reply "Invalid webhook token." What should I do?
Check that the campaign is Published and saved, that the header is named X-Webhook-Token, and that its value is the current Secret token. After a Regenerate, only the new token works. For a goal URL, the campaign must also start with the Custom Webhook trigger.
Ready to automate your customer service?
Book a 30-minute working call. We'll show up with your AI agent already built for your business by our professional prompt engineering team. No commitment.
Connect Custom Webhook