API and Webhooks for WhatsApp, Instagram, Messenger and RCS

The complete guide

API and Webhooks for WhatsApp, Instagram, Messenger and RCS: everything you need to know

What are API and webhooks in Com.Bot

Short answer: API and webhooks in Com.Bot are the two ways the platform talks to software outside it. The API lets your systems send instructions to Com.Bot, such as creating a contact or sending a template message. Webhooks let Com.Bot push events out, such as a new inbound message, a completed order or a payment confirmation. Both live inside the automation builder.

API and webhooks are the two ways Com.Bot talks to software outside the platform. The API lets your systems send instructions to Com.Bot, such as creating a contact, sending a template message or starting a bot flow. Webhooks let Com.Bot send events out to your systems the moment something happens, such as a new inbound message, a completed order or a payment confirmation.

In Com.Bot, both live inside the automation builder. You do not need a separate middleware layer to connect a WhatsApp reply to your order system. A bot step can call an external API, read the response and decide what to send next. A webhook can push that same event to your CRM so a sales agent sees the conversation in context.

This matters because chat is rarely the only system a business runs. A D2C brand has a store, a courier partner and a support desk. A coaching institute has a payment gateway and a student database. API and webhooks are how Com.Bot fits into that picture instead of becoming another silo.

• Send and receive data through REST-style API calls
• Fire webhooks on message, order, payment and bot events
• Use API responses inside bot logic and branching
• Connect to 1,000+ integrations or your own endpoints
• Run the same automation across four messaging channels

Who API and webhooks are for

Short answer: Com.Bot API and webhooks are for teams whose chat volume has outgrown manual copy-paste, including D2C brands syncing orders, agencies managing multiple client inboxes, service businesses booking appointments and developers building custom bot actions. They connect the chat channel to tools a business already pays for, so systems stay in sync without retyping.

API and webhooks are for teams whose chat volume has outgrown manual copy-paste. A D2C brand that sends order updates from a spreadsheet, an agency managing DMs for several clients, or a service business that books appointments over WhatsApp all hit the same wall. The conversation is easy. Keeping every other system in sync is not.

Small and growing businesses use Com.Bot API and webhooks to connect the chat channel to the tools they already pay for. A skincare brand might push every WhatsApp order to its fulfillment system. A coaching institute might pull batch details from its student database into a bot reply. An agency might route Instagram leads into a shared CRM without an account manager retyping them.

Developers use the same layer to build custom flows when an off-the-shelf integration does not exist. The visual builder covers most cases. The API and webhooks cover the rest, so you are not blocked by a missing connector.

• D2C brands syncing orders and delivery status
• Agencies managing multiple client inboxes
• Service businesses booking and reminding
• Support teams routing tickets to a helpdesk
• Developers building custom bot actions

How to set up API and webhooks in Com.Bot

Short answer: Setting up API and webhooks in Com.Bot starts in the automation builder. You create a flow, add a bot trigger, then add an external action step that calls your API endpoint or fires a webhook. You set the method, URL, headers and body, and can use the response in the next bot step. Com.Bot also ships with 1,000+ integrations.

Setup starts in the automation builder. You create a flow, add a bot trigger, then drop in an external action step. That step can be an API call to your endpoint or a webhook that fires when the flow reaches that point. You choose the method, the URL, the headers and the body. Com.Bot sends the request and can use the response in the next step.

For inbound events, you point your system at a Com.Bot webhook URL. When a message arrives, an order is placed or a payment is collected, Com.Bot posts the event to that URL. Your system decides what to do with it. This is how a CRM gets a new contact the moment someone replies to a WhatsApp template.

You do not need to write code for every connection. Com.Bot ships with 1,000+ integrations, so common tools like CRMs, helpdesks and ecommerce platforms are already mapped. API and webhooks are for the gaps, the custom logic and the systems that need a direct line. Plan limits apply to external actions and bot triggers, so check your tier before you build a high-volume flow.

• Open the automation builder and add a bot trigger
• Add an external action step for API or webhook
• Set the URL, method, headers and body
• Map the response into the next bot step
• Test with a live conversation before publishing

What can you automate with API and webhooks

Short answer: Com.Bot API and webhooks automate anything that needs chat and another system to agree, such as order status lookups inside WhatsApp replies, routing Instagram DM leads to a CRM, Messenger booking flows with calendar APIs, RCS payment or verification handoffs and abandoned cart recovery with store webhooks. The bot handles the first response and the API or webhook does the handoff.

The short answer is anything that needs chat and another system to agree. On WhatsApp, a customer replies to an order confirmation template. That reply opens a 24-hour service window. A webhook sends the reply to your helpdesk, and an API call pulls the latest delivery status back into the chat. The customer gets an answer without an agent leaving the inbox.

On Instagram, a comment or story reply can trigger a DM. That DM can call an API to check if the person is already a customer, then branch the reply. On Messenger, a Page conversation can push a lead to your CRM and pull back a booking link. On RCS, a suggested reply button can fire a webhook that starts a verification or payment flow.

The common thread is that the bot does the first response and the API or webhook does the handoff. Your team only steps in when the conversation needs a human. That is the difference between a chat tool and a communication platform that runs with your business.

• Order status lookups inside WhatsApp replies
• Lead routing from Instagram DMs to a CRM
• Messenger booking flows with calendar APIs
• RCS payment or verification handoffs
• Abandoned cart recovery with store webhooks

Rules and compliance for API and webhooks

Short answer: API and webhook automation in Com.Bot must follow platform rules. On WhatsApp Business API, business-initiated messages need Meta-approved templates and opted-in contacts, with marketing, utility and authentication categories applied correctly. A customer reply opens a 24-hour service window for free-form replies. Instagram and Messenger follow the same window, and RCS needs agent verification before launch.

The platform rules still apply when you automate. On WhatsApp Business API, business-initiated messages must use Meta-approved templates and go only to contacts who opted in. Template categories matter. Marketing templates cover offers, abandoned cart reminders and re-engagement. Utility templates cover order updates, delivery notifications and appointment reminders for something the customer already started. Authentication templates are for one-time passcodes only.

A customer reply opens a 24-hour customer service window. Inside that window you can send free-form replies. Outside it, you need a template. Meta charges per delivered template message by category and country. WhatsApp message charges are billed separately from the plan, based on message category and the recipient's country, and there is no monthly conversation cap.

Instagram DM automation runs through Meta's official messaging API for professional accounts. Automated replies are triggered by user actions such as comments, story replies, mentions or DMs, and the 24-hour window applies. Messenger works the same way on Facebook Pages. RCS requires agent verification before launch. Across all channels, quality rating and messaging limits grow with good engagement. Spamming lowers them. The green tick is granted by Meta, not by a provider.

• Use approved templates for business-initiated WhatsApp messages
• Match template category to the message purpose
• Respect the 24-hour service window on every channel
• Keep opt-in records for every contact you message
• Never call a cart reminder or offer a utility template

Mistakes to avoid with API and webhooks

The most common mistake is treating API and webhooks as a replacement for the bot builder. They are not. A webhook that fires on every message without a filter will flood your CRM with noise. An API call that runs on every bot step will burn through your external action limit. Use triggers and conditions so the automation only runs when it needs to.

The second mistake is ignoring the 24-hour window. A flow that sends a promotional follow-up outside the window on WhatsApp will fail or require a marketing template. The same applies to Instagram and Messenger. Build the window into your logic. If the customer replied recently, you can send free-form. If not, use a template or wait.

The third mistake is skipping error handling. APIs fail. Webhooks time out. A bot that stops when an endpoint is down leaves the customer waiting. Add a fallback step that sends a human handoff or a holding message. Test with real conversations before you publish. And keep an eye on your plan limits for external actions and bot triggers so a busy week does not break a flow.

• Do not fire webhooks on every message without filters
• Do not ignore the 24-hour service window
• Do not skip fallback steps for failed API calls
• Do not exceed your external action or trigger limits
• Do not publish without testing a live conversation

Frequently asked questions