--- title: "UseINBOX Integration" description: "UseINBOX bundles INBOX for email marketing, INBOXNotify for transactional email, and INBOXIys for filing consent records with Turkey's national message registry. Agents manage subscribers and campaigns, send transactional messages, and record consent, all from one account." url: https://flowrunner.ai/integrations/useinbox date_modified: 2026-09-04T14:28:58-07:00 --- # UseINBOX [Email Marketing](https://flowrunner.ai/integrations/category/email-marketing) UseINBOX bundles INBOX for email marketing, INBOXNotify for transactional email, and INBOXIys for filing consent records with Turkey's national message registry. Agents manage subscribers and campaigns, send transactional messages, and record consent, all from one account. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 77 actions · Session · available [UseINBOX website](https://useapi.useinbox.com/) · [Platform Documentation](https://developers.useinbox.com) · Capability data verified 2026-08-19 1. A batch of web form signups is ready to be filed and mailed 2. Agent reads each signup's address, the exact moment consent was given, and which form captured it 3. Agent groups the batch by consent source, because an import fixes the source for every row in it 4. Import Contacts To List writes the addresses and returns an import ID 5. Get Import Status confirms which rows landed and which were refused 6. Agent posts any batch that mixes consent sources to the compliance channel with the split named 7. The person who owns consent records approves each homogeneous batch before Import Consents files it with the registry ## What This Integration Enables UseINBOX is three products behind one account. INBOXNotify handles transactional email, INBOX handles marketing campaigns, and INBOXIys files consent records with Turkey's national message registry. That third product is the reason a team picks this platform, and it is not a marketing feature: the vendor documents that a commercial message in Turkey may only be sent to a recipient whose consent is filed with Ileti Yonetim Sistemi. The consent record is the thing that makes the message lawful, and everything else on the platform sits downstream of it. FlowRunner agents work across all three. They send transactional mail with or without a stored template, maintain senders, templates, newsletters, campaigns, groups, custom fields, and contact lists, read the transactional statistics and event streams, and register webhooks. They also write the consent side: brands, consent records, bulk consent imports, and the retailer access model that decides which of your resellers can act on those records. The credential here is an account email and password rather than a scoped key, which is exactly the kind of thing the [connectors](https://flowrunner.ai/concepts/connectors) layer should hold once and never hand around, and exactly the kind of platform where the [digital andon cord](https://flowrunner.ai/concepts/digital-andon-cord) belongs on the writes that leave your account and reach a regulator. ### Without FlowRunner **Consent filed after the fact**: Records reach the registry days later with a filing date standing in for the consent date **One account login shared around**: The credential is an email and password, so access is passed between people rather than scoped **Replace and update chosen by feel**: Both verbs are published for the same resource, and the replacing one blanks the fields left out ### With FlowRunner **Consent date carried from the source**: The agent reads the moment the person actually consented from the form record and keeps it attached **The login held once, by the platform**: The credential lives in one FlowRunner connection, and the token exchange happens inside the connector **Replace and update are separate operations**: The connector ships them as distinct actions, so an accidental blanking cannot happen by picking the wrong verb ## Use Case Scenarios ### Storefront signups that arrive with their provenance intact Checkout opt-ins from [Shopify](https://flowrunner.ai/integrations/shopify) reach the agent with a timestamp and the form that captured them. The agent calls Add Contact To List for individuals and Import Contacts To List for batches, which takes a bare JSON array and returns an import ID rather than a result, so Get Import Status is what turns acceptance into a known outcome. Custom fields on the marketing side are addressed as pairs of field ID and value, which means List Custom Fields runs first and the merge placeholders in the newsletter resolve against real IDs rather than guessed names. The day's totals land in [Google Sheets](https://flowrunner.ai/integrations/google-sheets) alongside the refusals, so nobody discovers a failed import a week later. ### Transactional mail whose reputation is actually watched Order confirmations go out through Send Email With Template against a stored INBOXNotify template, with values substituted into the platform's hash-delimited placeholders. On a schedule, the agent reads Get Aggregate Transactional Stats and List Transactional Events, and when the bounce rate on a sending domain moves, it posts the detail to [Microsoft Teams](https://flowrunner.ai/integrations/microsoft-teams) rather than clearing anything. Clear Bounces exists and makes previously bounced addresses deliverable again, but an address that hard bounced is usually gone for good, so the agent treats that operation as a remedy for a fixed underlying cause and never as a way to make a number look better. ### Reseller access that shrinks when it should An account with retailers filing consent on its behalf has to keep that list current. Add Retailer and Remove Retailer maintain who exists. Access is where the care goes: Add Retailer Access is additive, while Set Retailer Access replaces, so any retailer not named in the call loses access. The agent uses the additive form for onboarding, reads List Retailer Access before any replacement so the difference is visible, and posts that difference to [Slack](https://flowrunner.ai/integrations/slack) before running it. Remove All Retailer Access exists for a genuine cutoff and is never reached by a scheduled workflow. ## Human-in-Loop Highlight Import Consents is the operation on this platform where a mechanical mistake becomes a false record in a national registry. The reason is a quiet one: the import fixes the channel, the source, and the recipient type for the entire batch, while each entry carries only its recipient, its status, and its consent date. So a batch assembled from two different signup paths, a web form and a phone conversation, will be filed with one source for both. Nothing errors. The rows land. Every record whose source was actually the other one is now wrong, and the field that is wrong is the one describing how consent was obtained. The agent can see the shape of the batch. It cannot decide what to do about it. So it stops and posts: "412 consent records ready to file. 388 carry source HS\_WEB from the signup form. 24 came from the call center export and have no source recorded. Consent dates range from 3 March to yesterday, and all are approvals. File the 388 now and hold the 24, or split them into two imports with the second source confirmed?" The person who owns consent records answers. Reading the forms, checking the dates, grouping the batch, and filing the clean part are all work an agent should do without being asked. Asserting to a regulator how a stranger came to say yes is not. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 77 actions ### Transactional 6 - **Send Email** Sends a transactional message with inline content. Placeholders are hash-delimited and filled from a custom fields object keyed by name. - **Send Email With Template** Sends a transactional message from a stored INBOXNotify template. The route for order confirmations and password resets. - **Get Transactional Stats** Reads transactional sending figures for a period. - **Get Aggregate Transactional Stats** Reads rolled-up transactional figures. The input to a scheduled deliverability check. - **List Transactional Events** Lists individual delivery and engagement events. The answer to a question about one specific message. - **Clear Bounces** Makes previously bounced addresses deliverable again. Worth reaching for only after the underlying cause is fixed, because mailing known-dead addresses is what damages a sending reputation. ### Transactional Setup 10 - **List Notify Senders** Lists the sender identities configured for transactional mail. - **Create Notify Sender** Adds a transactional sender identity. - **Replace Notify Sender** Overwrites a transactional sender record in full. Fields left out are blanked. - **Update Notify Sender** Updates part of a transactional sender record. The safer of the two verbs. - **Delete Notify Sender** Removes a transactional sender identity. - **List Notify Templates** Lists stored transactional templates. - **Create Notify Template** Creates a transactional template. - **Replace Notify Template** Overwrites a transactional template in full. Fields left out are blanked. - **Update Notify Template** Updates part of a transactional template. - **Delete Notify Template** Removes a transactional template. Sends referencing it stop resolving, so cleanup checks first. ### Webhooks 5 - **List Webhooks** Lists registered webhooks. - **Create Webhook** Registers a webhook for platform events. - **Replace Webhook** Overwrites a webhook registration in full. - **Update Webhook** Updates part of a webhook registration. - **Delete Webhook** Removes a webhook registration. ### Campaigns 4 - **List Campaigns** Lists marketing campaigns and their state. - **Get Campaign** Reads one campaign. - **Create Campaign From Newsletter** Creates a campaign from a stored newsletter. The route when the content already exists on the platform. - **Create Campaign From HTML** Creates a campaign from supplied HTML. The route when an agent assembled the content upstream. ### Newsletters 6 - **List Newsletters** Lists stored newsletters. - **Get Newsletter** Reads one newsletter. - **Create Newsletter** Creates a newsletter. - **Replace Newsletter** Overwrites a newsletter in full. Fields left out are blanked. - **Update Newsletter** Updates part of a newsletter. - **Delete Newsletter** Removes a newsletter. ### Marketing Setup 17 - **List Marketing Senders** Lists the sender identities configured for marketing mail. - **Create Marketing Sender** Adds a marketing sender identity. - **Replace Marketing Sender** Overwrites a marketing sender record in full. - **Update Marketing Sender** Updates part of a marketing sender record. - **Delete Marketing Sender** Removes a marketing sender identity. - **List Groups** Lists contact groups. - **Create Group** Creates a contact group. - **Replace Group** Overwrites a group record in full. - **Update Group** Updates part of a group record. - **Delete Group** Removes a group. - **List Custom Fields** Lists custom fields with their IDs. Marketing-side personalization is keyed by field ID, so this read comes first. - **Create Custom Field** Creates a custom field. - **Replace Custom Field** Overwrites a custom field definition in full. - **Update Custom Field** Updates part of a custom field definition. - **Delete Custom Field** Removes a custom field. Content referencing its ID stops resolving. - **List Segments** Lists segments. Segments are built in the interface, so a workflow can target one but cannot create one. - **Delete Segment** Removes a segment. ### Contacts 4 - **List Contacts** Lists contacts with paging. - **Get Contact** Reads one contact. - **Update Contact** Updates a contact's stored fields. - **Change Contact Status** Sets a contact's status. All three accepted values are negative, and there is no value that re-subscribes someone, which is deliberate. ### Contact Lists 9 - **List Contact Lists** Lists the account's contact lists. - **Create Contact List** Creates a contact list. - **Replace Contact List** Overwrites a contact list record in full. - **Update Contact List** Updates part of a contact list record. - **Delete Contact List** Removes a contact list. - **Add Contact To List** Adds one contact to a list. The individual write behind form and checkout signups. - **Import Contacts To List** Imports a batch of contacts and returns an import ID. Returning does not mean the data is in. - **Get Import Status** Reports the outcome of a contact import. The step that turns acceptance into a known result. - **Remove Contact From List** Removes one contact from a list without deleting them from the account. ### Consent Registry 16 - **List Brands** Lists the brands consent records can be filed under. - **List Consents** Lists filed consent records. - **Get Consent** Reads one filed consent record. - **Add Consent** Files one consent record. The consent date is when the person actually consented, not when the record is filed. - **Import Consents** Files a batch of consent records under one channel, source, and recipient type. Each entry carries only its recipient, status, and date, which is why a mixed batch has to be split, and why this operation waits for a person. - **List Consent Imports** Lists consent import jobs. - **Get Consent Import** Reports which records in a consent import failed. - **List Retailers** Lists the retailers registered on the account. - **Get Retailer** Reads one retailer. - **Add Retailer** Registers a retailer. - **Remove Retailer** Removes a retailer. - **Add Retailer Access** Grants a retailer access additively, leaving existing grants in place. - **Set Retailer Access** Replaces the access list, so any retailer not named loses access. The name is close to the additive one and the effect is not. - **List Retailer Access** Lists current retailer access for a recipient. The read that makes a replacement's blast radius visible before it runs. - **Remove Retailer Access** Revokes one retailer's access. - **Remove All Retailer Access** Revokes every retailer's access. Reserved for a genuine cutoff rather than for scheduled maintenance. ## Frequently Asked Questions ### What can FlowRunner do with UseINBOX? FlowRunner agents can run Send Email, Send Email With Template, and Get Transactional Stats in UseINBOX, plus 74 more actions. ### Does connecting UseINBOX to FlowRunner require OAuth? No. UseINBOX connects to FlowRunner with session-based authentication, no OAuth flow required. ### Can UseINBOX trigger a FlowRunner workflow automatically? UseINBOX doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at UseINBOX?** This integration exposes UseINBOX to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/useinbox. Site index: https://flowrunner.ai/llms.txt