Integration
Connect Bento and Fibery
When New Tag fires in Bento, your agent runs Add comment in Fibery, or Entity Updated (Or Created) in Fibery to Send Transactional Email in Bento. 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 Fibery 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)Grok
Open grok.com/connectors, choose New Connector, then Custom, and paste the address. Grok signs you in in your browser.
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 and Fibery can do together
From Bento to Fibery
When New Tag in Bento
then Add comment in Fibery
When New Tag in Bento
then Get Document in Fibery
From Fibery to Bento
When Entity Updated (Or Created) in Fibery
then Send Transactional Email in Bento
When New Entity in Fibery
then Update email template in Bento
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 Fibery
Triggers and actions 4 triggers · 33 actions
Trigger
New TagTriggers when a new tag is created on your Bento site.
Action
Add broadcastCreates a broadcast email draft in Bento, optionally scheduled and approved for sending to tagged or segmented subscribers.
Action
Create FieldCreates a custom subscriber field on your Bento site.
Action
Create or Update UserCreates a Bento subscriber, or updates the name of an existing one, by email address.
Action
Create or Update User and Apply TagCreates or updates a Bento subscriber by email and applies one or more tags, without triggering Flows.
Action
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.
Action
Create TagCreates a tag on your Bento site.
Action
Delete tagDiscards a tag in Bento by name (running it on an already-discarded tag restores it).
Action
Fetch Site MetricsReturns your Bento site's user, subscriber and unsubscriber counts.
Action
Fetch SubscriberReturns a Bento subscriber's details, tags and custom fields by email address.
Action
Get email templateReturns one email template, including its name, subject and HTML content.
Action
Get segmentReturns one segment, including its name, description and filter definition.
Action
Import subscribersQueues up to 1,000 subscribers for import or update in Bento. Imports do not trigger automations.
Action
List BroadcastsReturns one page of Bento broadcasts with the chosen status, including their send stats.
Action
List FieldsReturns every custom subscriber field on your Bento site.
Action
List segmentsReturns all segments in your Bento site.
Action
List sequencesReturns the sequences on your Bento site, including each sequence's email templates.
Action
List TagsReturns every tag on your Bento site.
Action
List workflowsReturns all workflows on the Bento site, with their name, status and email templates.
Action
Remove Tag from SubscriberRemoves a tag from a Bento subscriber by email.
Action
Send Transactional EmailSends an email through Bento to one recipient, optionally as transactional so it reaches unsubscribed people.
Action
Track EventRecords a custom event for a Bento subscriber, optionally updating their profile fields; events can start Flows.
Action
Track Subscribe EventSubscribes or unsubscribes a Bento subscriber by email.
Action
Track Unique EventRecords a purchase for a Bento subscriber with its value, counted once per order ID.
Action
Update email templateUpdates the subject, HTML content, or editor type of a Bento email template.
Action
Update Subscriber FieldSets one custom field value on a Bento subscriber.
Action
Validate EmailChecks whether an email address looks valid and deliverable.
Trigger
Entity Updated (Or Created)Triggered when an entity in the chosen database is created or updated.
Trigger
New EntityTriggers when a new Entity (Task, Document, etc.) is created.
Trigger
New TypeTriggers when a new type is created.
Action
Add commentAdd a comment to an entity.
Action
Add EntityCreates a new Entity (Task, Document, etc.).
Action
Delete EntityDelete an entity by id.
Action
Find EntityFinds an Entity with matching field values.
Action
Get DocumentReturns the content of a Fibery rich-text document (e.g. a comment body or rich-text field) by its document secret.
Action
Get EntityRetrieve one entity by id with selected fields.
Action
Update EntityUpdates existing Entity (Task, Document, etc.).
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 Fibery
Attio to FiberyAttio is the CRM of the future: data-driven, completely customizable and intuitively collaborative.
ActiveCampaign to FiberyActiveCampaign is a marketing automation, email marketing, and CRM platform.
Airtable to FiberyOrganize anything with Airtable, a modern database created for everyone.
Asana to FiberyAsana is a collaborative information manager for workspace.
ClickUp to FiberyClickUp is an all-in-one app to plan, track, and manage your work in a beautifully intuitive environment.
Discord to FiberyDiscord is an all-in-one voice and text chat for gamers.
Questions
Bento and Fibery, 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 Fibery when something happens in Bento?
Any of Fibery's 7 actions, including Update Entity, Add comment, Add Entity and Find Entity. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Fibery to Bento?
Yes. When something happens in Fibery, your agent can act in Bento too. This page covers both directions: Fibery's triggers and Bento's actions are listed here as well.
Do I have to build a connector for Bento or Fibery?
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 Fibery 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.