--- title: "Power Automate + OmniChannels.ai: messaging steps in your flows" description: "Send WhatsApp and SMS from Power Automate flows with the premium HTTP action or a custom connector, and start flows from OmniChannels.ai delivery statuses." canonical: "https://omnichannels.ai/integrations/power-automate/" language: "en" updated: "2026-10-10" publisher: "BroadNet Technologies" brand: "OmniChannels.ai" --- # Power Automate + OmniChannels.ai: messaging steps in your flows Canonical: https://omnichannels.ai/integrations/power-automate/ Language: en Publisher: OmniChannels.ai by BroadNet Technologies **In short:** Power Automate works with OmniChannels.ai through its own HTTP features, not a certified connector. The premium HTTP action calls our REST API with your Bearer token to send WhatsApp, SMS and other messages, or you can build a custom connector. The When an HTTP request is received trigger accepts delivery statuses and inbound messages. Both need a Power Automate premium licence. Connect via API & webhooks ## What you can do ### Send a WhatsApp template when a new row is added When a row is added to a SharePoint list, Excel table or Dataverse table, send an approved WhatsApp template with the row's values, to contacts who have opted in. ### Notify customers when a record changes When a case, order or appointment changes status in a Microsoft or connected system, send an SMS or WhatsApp update to the customer. ### Alert the team when a delivery fails An HTTP request trigger receives delivery statuses; a condition passes FAILED and REJECTED events to a Teams message or email instead of resending. ### Reuse one connector across flows A custom connector defines the send operations once, so makers can add a messaging action to their flows without handling the URL and headers. ### Track message status in Dataverse Store each message ID on the record that triggered it, then update the status as events arrive, ignoring late or duplicate events. ## How it connects The quickest route is the HTTP action: method POST, the channel's send path on https://api.broadnet.me, an Authorization header with Bearer and your token, and a JSON body. Bulk and most other channel sends take multipart form data, which needs a multipart body in the action and more care to build. Keep the token in a secure input, an environment variable or a key vault rather than in plain text in the flow. For reuse, create a custom connector. Its OpenAPI import expects OpenAPI 2.0, while our public spec is OpenAPI 3.1, so convert the operations you need or define them in the connector wizard. To receive events, add the When an HTTP request is received trigger, save the flow and send the generated URL to our team or your account admin. - Send: HTTP action, POST to https://api.broadnet.me with Authorization: Bearer - Reuse: custom connector, defined manually or from a converted OpenAPI 2.0 file - Receive: When an HTTP request is received trigger URL configured on your account - HTTP, the HTTP request trigger and custom connectors are premium; check Microsoft's licensing - Never resend automatically from a status flow ## Set it up 1. **Request API access:** Request test access and receive an API token. Test sends go only to your own verified numbers. (Guide: https://omnichannels.ai/developers/quickstart/) 2. **Check your licence:** Confirm the flow's owner has a Power Automate licence that includes premium connectors, which the HTTP action, HTTP request trigger and custom connectors require. 3. **Add the sending step:** Add an HTTP action with POST, the channel's send URL, the Authorization header and the body mapped from your trigger, or use a custom connector built from the operations you need. (Guide: https://omnichannels.ai/developers/openapi/) 4. **Receive delivery statuses:** Create a flow with the When an HTTP request is received trigger, save it, and send the generated URL to our team or your account admin. (Guide: https://omnichannels.ai/developers/webhooks/) 5. **Test with your own number:** Run the flow against your verified number and check the run history for the send and the status events. ## Example workflow Microsoft 365 or Dataverse (A new row, list item, case or order change) → Power Automate HTTP action (POST to the REST API, or a custom connector) → OmniChannels.ai API (Sends the message and returns a message ID) → Customer's phone (WhatsApp or SMS message delivered) → HTTP request trigger (Delivery statuses and inbound messages start a flow) ## Questions ### Is there a certified OmniChannels.ai connector for Power Automate? No. Flows use the built-in HTTP action and HTTP request trigger, or a custom connector that you create in your own environment from our API documentation. ### Can I import your OpenAPI spec into a custom connector? Not directly. Custom connector import expects OpenAPI 2.0 and our public spec is OpenAPI 3.1. Convert the operations you need to OpenAPI 2.0, or define them by hand in the connector wizard. ### Do I need a premium licence? The HTTP action, the When an HTTP request is received trigger and custom connectors are premium. Check Microsoft's current Power Automate licensing for your plan. ### Can a flow send WhatsApp templates? Yes, through the WhatsApp send operation from our API documentation. Business-initiated messages outside the 24-hour service window need an approved template and an opted-in recipient. ## Developer guides - https://omnichannels.ai/developers/openapi/ - https://omnichannels.ai/developers/webhooks/ - https://omnichannels.ai/developers/authentication/ - https://omnichannels.ai/developers/whatsapp/ ## Vendor documentation - [Custom connectors overview — Microsoft Learn](https://learn.microsoft.com/en-us/connectors/custom-connectors/) - [Create a custom connector from an OpenAPI definition — Microsoft Learn](https://learn.microsoft.com/en-us/connectors/custom-connectors/define-openapi-definition) ## Related integrations - https://omnichannels.ai/integrations/microsoft-copilot-studio/ - https://omnichannels.ai/integrations/dynamics-365/ - https://omnichannels.ai/integrations/zapier/ - https://omnichannels.ai/integrations/make/ Power Automate is a trademark of its owner. OmniChannels.ai is not affiliated with or endorsed by Power Automate; this page describes a connection built with Power Automate's own MCP, HTTP or webhook features. Updated: 2026-10-10