Notificacoes Inteligentes
MessagingConnect AI agents to Notificacoes Inteligentes, a Brazilian platform that sends WhatsApp notifications for ecommerce stores. Agents dispatch order, shipping, and cart events, manage contacts, tags, and lists, and maintain custom variables so every store milestone reaches customers on WhatsApp automatically.
What This Integration Enables
Most messaging connectors send a message. This one does not, and understanding that is the whole page. Notificacoes Inteligentes is a Brazilian platform, operated by GPM Participacoes e Tecnologias, that sends WhatsApp notifications for ecommerce stores. Its API dispatches ecommerce events, abandoned cart, order paid, boleto printed, package out for delivery, NPS survey, and the platform decides which WhatsApp message flow each event triggers and what the customer actually reads. The flow author supplies the fact. The panel supplies the words.
That is a genuinely good division of labor, and it is why a store would choose this over wiring WhatsApp up directly. Notification copy is marketing's work, it changes constantly, and it is written in Portuguese for a Brazilian audience with conventions a developer should not be arbitrating. Keeping it in the panel means a phrase can be reworded without touching an automation, and it means the same event dispatched from three different systems produces one consistent message. The connector's sixteen event routes cover the order lifecycle end to end, plus the two things a Brazilian store needs that a generic platform will not have:
- Dispatch Billet Printed Event carries the boleto URL and the typeable barcode, and supplying the due date is what enables the reminder flow.
- Dispatch Waiting Payment Event uses the payment type of credit card, bank deposit, or Pix to select the downstream flow, and a Pix order can carry the Bacen code, the QR code, the payment URL, and the due date.
The rest of the surface is the audience layer that those flows run against. Full CRUD over contacts, tags, contact lists, and custom variables, with tags on contacts matched by name rather than by identifier, custom variables typed as email, text, CNPJ, CPF, integer, numeric, date, checkbox, multi select, or option list, and variable groups as the folders they are filed under. Look Up Address By Postal Code resolves a Brazilian CEP into street, neighborhood, city, and state, which is a small action that saves a lot of address correction. Two platform behaviors are worth designing around. The event routes are rate limited to sixty requests per minute. And an opt-out is applied account wide across every instance sharing stores with the current one, so a customer who opts out of one store's messages is opted out of all of them.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Cart recovery that knows what is in the cart
A store on Shopify has a checkout abandonment problem, which every store has. The agent watches carts that reach checkout and stall, waits the interval the merchant chose, and dispatches the abandoned cart event with the checkout URL that returns the shopper directly to their purchase rather than to the homepage. The platform matches it to the recovery flow the marketing team wrote and sends the WhatsApp message. What the agent contributes is not the copy, it is the judgment about which carts qualify: excluding shoppers who completed a different order in the meantime, excluding contacts already tagged as recently messaged, and excluding anyone the account opted out. Set Contact Tags applies the recently messaged tag afterward, so the same person does not receive three recoveries in a week from three different stalled sessions.
Boletos and Pix, chased on the schedule Brazilians actually expect
A boleto issued today may be paid in five days or never, and the difference is often whether anyone reminded the buyer. When a boleto is generated in the store, the agent dispatches the billet printed event with the boleto URL, the typeable barcode, and the due date, and it is the due date that switches on the platform's reminder sequence. For Pix and card orders the waiting payment event carries the payment type, which selects a different flow entirely, since a Pix order needs its QR code and payment URL in the message and a declined card needs a retry link. When payment settles, the order paid event fires and the chasing stops. Reconciliation runs against WooCommerce or VTEX so that a payment recorded upstream but never dispatched here becomes an automation exception rather than a customer who keeps getting reminded about something they already paid.
An audience that matches the CRM instead of drifting from it
The platform's flows target contacts, and contacts carry tags, list memberships, and custom variable values. Left alone, those drift from whatever the business actually believes about its customers. A nightly agent reconciles them against RD Station: new customers become contacts, changed attributes flow into Update Contact and the custom variable values it carries, and segment membership is rebuilt with Add Contacts To List and Remove Contacts From List in batched calls rather than one contact at a time. Tag operations are chosen deliberately. Add Tags To Contact is used for additive facts such as a purchase category. Set Contact Tags, which replaces the entire tag set, is used only where the flow genuinely owns every tag on that contact, because replacing a set can strip a tag that a support process put there.
Human-in-Loop Highlight
The gate on Notificacoes Inteligentes is any replay, backfill, or first run against a newly created integration, and it exists because of a property this connector has and almost nothing else in the catalog does: the agent cannot read the message it is about to cause. Dispatching an event does not send text you can inspect. It tells the platform that something happened, and the platform selects a WhatsApp flow configured in the panel and sends whatever that flow says. There is no preview action, no test mode, and no dry run anywhere in this API, and the vendor states it offers no sandbox or test account. So the usual safety net, sending one message to yourself first and reading it, does not exist here.
That makes one specific situation dangerous in a way it would not be elsewhere. An integration goes down for four hours. When it comes back, there are two hundred orders whose state changed while nobody was dispatching. The obvious remediation is to replay them, and the obvious remediation sends two hundred real WhatsApp messages, some of them chasing payment on orders that settled during the gap, some of them announcing delivery of packages that arrived yesterday. It succeeds. It is rate limited to sixty requests per minute, so it takes a few minutes and looks like a healthy catch up run. And because opt-outs here are applied account wide across every instance that shares stores, the customers who react by opting out are lost to every store, not just this one.
So the agent stops before it replays. Into Slack: "Backfill ready for integration 4188 (Loja Principal): 214 events queued from the 09:10 to 13:40 gap. Breakdown: 96 order paid, 71 shipping progress, 34 waiting payment, 13 abandoned cart. 22 of the waiting payment orders have since been marked paid upstream and are excluded. This API has no preview and no test mode, so the WhatsApp text each of these produces is whatever the panel flow for that event says today. Confirm the event to flow mapping for waiting payment and shipping progress, then approve the replay, or approve order paid only?" That is a question about what is configured in a panel the agent cannot see, asked of the person who configured it.
That is the digital andon cord under Orchestration as a Service, placed where the system has no instrument at all rather than where it has a warning light. Steady state dispatch is not gated, and should not be, because an order paid event firing seconds after an order is paid is exactly the automation the merchant bought. Two other calls belong beside the backfill for the same reason: Delete Integration removes an integration and the store it represents, and Set Contact Tags replaces a contact's whole tag set, which can silently move that person into or out of the audience a flow targets.
Agent Capabilities
54 actionsIntegrations
5- List Integrations Returns every integration on the account with its identifier, name, source platform, and integration token. The lookup that resolves a store to the numeric identifier every event route needs.
- Create Integration Creates an integration for one of the supported source platforms. The platform cannot be changed afterward, so this is a decision rather than a setting.
- Get Integration Returns one integration, optionally with its setup fields, its available events, or its onboarding checklist. The available events list is the closest thing to a manifest of what this store can dispatch.
- Update Integration Renames an integration. The source platform is fixed at creation and cannot be changed here.
- Delete Integration Deletes an integration and the store it represents. Permanent, and it takes the store's configuration with it.
Events
16- Dispatch Abandoned Cart Event Reports a cart left at checkout, carrying the checkout URL that returns the shopper directly to their purchase. The event behind every recovery sequence.
- Dispatch Order Paid Event Reports a settled order with its totals, product lines, and optional delivery and address blocks. Also the event that should stop any payment chasing already in flight.
- Dispatch Order Canceled Event Reports a canceled order, so the customer hears it from the store rather than by noticing nothing arrived.
- Dispatch Order Refunded Event Reports a refunded order with its totals, closing the loop on a return the customer is waiting on.
- Dispatch Order Processing Event Reports an order moving into processing. The reassurance message between payment and dispatch.
- Dispatch Order Fulfilled Event Reports an order fulfilled and handed to the carrier.
- Dispatch Order Delivered Event Reports a completed delivery. Often the natural point to follow with the NPS survey event.
- Dispatch Shipping Out For Delivery Event Reports that the package is out for delivery today, which is the tracking update customers actually want on WhatsApp rather than in email.
- Dispatch Shipping Progress Event Reports an intermediate carrier tracking update.
- Dispatch Shipping Arrived For Withdrawal Event Reports that a package has arrived at a collection point and is waiting to be picked up.
- Dispatch Billet Printed Event Reports that a Brazilian boleto has been issued. The billet URL and typeable barcode are required, and supplying the due date is what enables the reminder sequence.
- Dispatch Waiting Payment Event Reports an unsettled payment. The payment type of credit card, bank deposit, or Pix selects the downstream flow, and a Pix order can carry the Bacen code, QR code, payment URL, and due date.
- Dispatch Access Created Event Reports that members area credentials have been issued to a buyer, delivering them over WhatsApp.
- Dispatch Reset Password Event Delivers a one time password reset link over WhatsApp.
- Dispatch NPS Survey Event Sends an NPS questionnaire to the customer.
- Dispatch NPS Answer Event Reports the score a customer gave back into the platform, so the survey result lives with the contact rather than in a spreadsheet.
Contacts
7- Create Contact Creates a contact with name, phone, and email, and can apply tags and custom variable values in the same call. The phone number is the contact's identity.
- List Contacts Returns a paginated contact list, filterable by name, phone, email, or tags. The read behind any reconciliation against a CRM.
- Get Contact Returns one contact, optionally with its lists, tags, or assigned users. The full picture of which audiences a person currently belongs to.
- Update Contact Updates name, email, notes, or custom variable values. The phone number is the identity and cannot be changed here, so a number change is a different operation entirely.
- Delete Contact Deletes a contact. Their list memberships and tag history go with them.
- Add Contact To Lists Changes one contact's membership across several lists in a single call.
- Remove Contact From Lists Removes one contact from several lists at once. Worth reviewing before running in bulk, since list membership is what the platform's flows target.
Contact Lists
7- List Contact Lists Returns the account's contact lists, filterable by name and by type across stream, import, dynamic, auto import, and tags.
- Get Contact List Returns one list with its type, contact count, and tags. The read that tells you how big an audience is before you act on it.
- Update Contact List Renames a list.
- Delete Contact List Deletes a list. The contacts themselves survive, but anything targeting this list stops resolving.
- List Contacts In List Returns the paginated contacts of one list, filterable by name, phone, or email. The way to see who is actually in an audience rather than how many.
- Add Contacts To List Adds several contacts to one list in a single request. The batched form a nightly segment rebuild should use.
- Remove Contacts From List Removes several contacts from one list in a single request.
Tags
8- List Tags Returns paginated tags, sortable by label or identifier in either direction.
- Create Tag Creates a tag with a label, a description, and a hexadecimal color.
- Get Tag Returns one tag.
- Update Tag Changes a tag's label, description, or color. Since tags on contacts are matched by name, renaming one is more consequential than it looks.
- Delete Tag Deletes a tag, removing it from every contact carrying it.
- Add Tags To Contact Applies tags to a contact while keeping the tags it already has. The additive form, and the safe default.
- Set Contact Tags Replaces a contact's whole tag set. Use only where the flow genuinely owns every tag on that contact, because this can strip a tag a support process put there.
- Remove Tags From Contact Removes named tags from a contact, leaving the rest in place.
Custom Variables
10- List Custom Variables Returns the organization's custom variables, filterable by slug, data type, or group name.
- Create Custom Variable Creates a custom variable of a given data type across email, text, CNPJ, CPF, integer, numeric, date, checkbox, multi select, and option list. The slug is derived from the description.
- Get Custom Variable Returns one custom variable with its type and slug.
- Update Custom Variable Changes a custom variable. The data type and slug are fixed at creation and cannot be changed here.
- Delete Custom Variable Deletes a custom variable and the values held against it on every contact.
- List Variable Groups Returns the groups that custom variables are filed under in the panel.
- Create Variable Group Creates a variable group.
- Get Variable Group Returns one variable group.
- Update Variable Group Renames a variable group.
- Delete Variable Group Deletes a variable group.
Account
1- Look Up Address By Postal Code Resolves a Brazilian CEP into street, neighborhood, city, and state. A small action that removes a large amount of address correction from a delivery notification flow.
Frequently Asked Questions
What can FlowRunner do with Notificacoes Inteligentes?
FlowRunner agents can run List Integrations, Create Integration, and Get Integration in Notificacoes Inteligentes, plus 51 more actions.
Does connecting Notificacoes Inteligentes to FlowRunner require OAuth?
No. Notificacoes Inteligentes connects to FlowRunner with an API key, no OAuth flow required.
Can Notificacoes Inteligentes trigger a FlowRunner workflow automatically?
Notificacoes Inteligentes doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Notificacoes Inteligentes
$100 in credits. No card required. Connect in minutes.