Integration
Connect Bento to Instatus
When New Tag fires in Bento, your agent runs Add component in Instatus. Describe the whole flow and it is built, tested on every scenario and kept running.
What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it.
Build solutions, not workarounds.
What do you want Bento and Instatus to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiOne connection does both: ask your client to act in an app once, or have it build an automation that keeps running. Any client that takes a remote MCP server. Nothing to install. Create your free account, then sign in once in your browser.
Set it up in your client
Claude Code
Run this in the directory you want to work in.
claude mcp add --transport http -s project apiant-ai https://mcp.apiant.aiStart Claude Code there, approve the server, and sign in in the browser page it opens.
Claude Code guide (opens in a new tab)Claude, web and desktop
Open Customize, then Connectors, then Add custom connector, and paste the address. On Team and Enterprise an owner adds it first.
Setup guide (opens in a new tab)Cursor
Add the address to your MCP configuration as a server URL. Cursor signs you in in your browser.
Setup guide (opens in a new tab)Zed
Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server.
Setup guide (opens in a new tab)Codex and the ChatGPT desktop app
Open Settings, then MCP servers, then Add server, and choose Streamable HTTP. From the terminal, Codex takes the address with its own add command and then signs you in.
Setup guide (opens in a new tab)Any other MCP client
Paste the address where the client asks for a remote MCP server URL, and name the server apiant-ai where it lets you. APIANT's skills reach the client over the same connection.
Setup guide (opens in a new tab)Example flows
What Bento can start in Instatus
When New Tag in Bento
then Add component in Instatus
Starting points drawn from the triggers and actions in the catalog today. Describe the flow you need, at any depth, and your agent builds it and tests every scenario before it ships.
Everything your agent can do with Bento and Instatus
Triggers and actions 1 trigger · 37 actions
- New Tag
Triggers when a new tag is created on your Bento site.
- Add broadcast
Creates a broadcast email draft in Bento, optionally scheduled and approved for sending to tagged or segmented subscribers.
- Create Field
Creates a custom subscriber field on your Bento site.
- Create or Update User
Creates a Bento subscriber, or updates the name of an existing one, by email address.
- Create or Update User and Apply Tag
Creates or updates a Bento subscriber by email and applies one or more tags, without triggering Flows.
- Create or Update User and Apply Tag (Trigger Flows)
Applies a tag to a Bento subscriber (creating them if needed) through an event, so any Flows listening for that tag start.
- Create Tag
Creates a tag on your Bento site.
- Delete tag
Discards a tag in Bento by name (running it on an already-discarded tag restores it).
- Fetch Site Metrics
Returns your Bento site's user, subscriber and unsubscriber counts.
- Fetch Subscriber
Returns a Bento subscriber's details, tags and custom fields by email address.
- Get email template
Returns one email template, including its name, subject and HTML content.
- Get segment
Returns one segment, including its name, description and filter definition.
- Import subscribers
Queues up to 1,000 subscribers for import or update in Bento. Imports do not trigger automations.
- List Broadcasts
Returns one page of Bento broadcasts with the chosen status, including their send stats.
- List Fields
Returns every custom subscriber field on your Bento site.
- List segments
Returns all segments in your Bento site.
- List sequences
Returns the sequences on your Bento site, including each sequence's email templates.
- List Tags
Returns every tag on your Bento site.
- List workflows
Returns all workflows on the Bento site, with their name, status and email templates.
- Remove Tag from Subscriber
Removes a tag from a Bento subscriber by email.
- Track Subscribe Event
Subscribes or unsubscribes a Bento subscriber by email.
- Update email template
Updates the subject, HTML content, or editor type of a Bento email template.
- Update Subscriber Field
Sets one custom field value on a Bento subscriber.
- Validate Email
Checks whether an email address looks valid and deliverable.
- Add component
Creates a new component on an Instatus status page and returns the created component.
- Add incident update
Posts a new update to an existing incident on an Instatus status page, optionally changing the incident status and affected component statuses.
- Add maintenance
Schedules a new maintenance on an Instatus status page, with its affected components, timing and subscriber notification options.
- Add subscriber
Adds a subscriber (by email or phone) to a status page, subscribed to all components or to specific ones.
- Create Incident
Creates a new incident on an Instatus status page, optionally marking affected components and notifying subscribers.
- Delete incident
Deletes an incident from an Instatus status page.
- Get component
Returns one component on an Instatus status page, including its name, current status, description and group.
- Get incident
Returns a single incident on a status page, including its updates, affected components and the teammate who created it.
- Get maintenance
Returns one scheduled maintenance on a status page, including its updates and affected components.
- List components
Returns the components on an Instatus status page, with each component's name, status and group.
- List maintenances
Returns the scheduled, in-progress and completed maintenances on an Instatus status page.
- List status pages
Returns the status pages in your Instatus account, including each page's id, name, subdomain and current status.
- List subscribers
Returns the subscribers of an Instatus status page, optionally filtered by email/phone search or subscription status.
- Update component
Updates a component on an Instatus status page, such as its name, description, status, order or group.
No trigger or action matches that. Ask your agent to add it: it reads the API documentation and builds what you describe.
Each app on its own
Reviews
What our customers say
More from Bento
Bento to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Bento to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Bento to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Bento to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Bento to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Bento to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Instatus
Questions
Bento and Instatus, answered
What can start an automation from Bento?
Any of Bento's 1 trigger in the catalog, including New Tag. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Instatus when something happens in Bento?
Any of Instatus's 14 actions, including Create Incident, Update component, Add component and Add incident update. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Instatus to Bento?
Instatus has no triggers in the catalog today, so automations start in Bento. If you need the other direction, ask: your agent reads Instatus's API documentation and adds it.
Do I have to build a connector for Bento or Instatus?
No. Both are in the catalog with their triggers and actions. You describe the automation; your agent builds it, tests every scenario and keeps it running.
Can my AI client use Bento and Instatus without building an automation?
Yes. With your AI client connected to APIANT, ask it to do something in either app once and it runs that action on the spot. Ask for an automation and your agent builds it, tests every scenario and keeps it running. One connection covers both.
What happens when something fails?
Your agent works that out for you. It plans the failure paths along with the happy path, then tests every scenario before it ships.
Is there a free plan?
Yes. Every plan includes the agent, including free, and building from your own AI client spends no assistant credits.