Integration
Connect Bread & Butter and wethod
When New Authentication fires in Bread & Butter, your agent runs Create a contact in wethod, or New Client in wethod to Add contact us submission in Bread & Butter. 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 Bread & Butter and wethod 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 Bread & Butter and wethod can do together
From Bread & Butter to wethod
When New Authentication in Bread & Butter
then Create a contact in wethod
When New Contact Us Submission in Bread & Butter
then Create an invoice in wethod
From wethod to Bread & Butter
When New Client in wethod
then Add contact us submission in Bread & Butter
When New Contact in wethod
then Add lead list in Bread & Butter
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 Bread & Butter and wethod
Triggers and actions 13 triggers · 73 actions
Trigger
New AuthenticationTriggers every time a user signs in.
Trigger
New Contact Us SubmissionTriggers when a user submits the Contact Us tool.
Trigger
New Custom FieldsTriggers when a user submits the Custom Fields for Registration.
Trigger
New Custom User EventTriggers when a user subscribes to custom events, selected in the triggers section below.
Trigger
New Email CapturedTriggers when a user enters their email address, or signs in with SSO for the first time.
Trigger
New Profile VerifiedTriggers when a user signs in for the first time.
Action
Add contact us submissionRecords a Contact Us submission from a visitor's device in a Bread & Butter app.
Action
Add eventRecords an event (such as a page view or custom event code) for a device in a Bread & Butter app.
Action
Add form submissionRecords a form submission from a visitor's device in a Bread & Butter app, capturing their email, name and any extra form fields.
Action
Add lead listCreates a lead list in a Bread & Butter app from a set of leads, returning the new list with its lead count and credit quote.
Action
Add tagCreates a new tag in a Bread & Butter app.
Action
Add user custom valuesSaves custom field values (key/value pairs) for a visitor in a Bread & Butter app.
Action
Create custom event definitionCreates a custom event definition in a Bread & Butter app, which users can then trigger and which can be subscribed to.
Action
Delete tagDeletes a tag from a Bread & Butter app.
Action
Get credit balanceReturns the credit balance for a Bread & Butter app, including credits used this period, the monthly allowance and pending enrichments.
Action
Get device profileReturns the sign-in options and the visitor's profile state for one registered device.
Action
Get lead listReturns a Bread & Butter lead list by its ID, including its processing status, lead counts and credit usage.
Action
Identify userIdentifies an anonymous visitor's device as a known person in a Bread & Butter app by attaching their email address and name.
Action
List app triggersReturns the triggers set up in a Bread & Butter app, including webhook subscriptions, with their kind, filters and activity state.
Action
List custom event definitionsReturns the event definitions configured in a Bread & Butter app, optionally filtered to enabled or disabled ones.
Action
List EventsReturns the events recorded in a Bread & Butter app — sign-ins, page views, custom events, form submissions and more — optionally narrowed to one user or a date range.
Action
List lead listsReturns all lead lists in a Bread & Butter app, including each list's status, lead counts and credit usage.
Action
List tagsReturns every tag defined in a Bread & Butter app, with each tag's id and name.
Action
List user eventsReturns the page views and events (sign-ins, custom events, form submissions and more) a user recorded during one of their sessions in a Bread & Butter app.
Action
List usersReturns the users (visitors and leads) recorded in a Bread & Butter app, optionally narrowed to one email address or user state.
Action
List user sessionsLists the sessions of one Bread & Butter user, newest first, with each session's ID, start time, location, device and page view count.
Action
Record external authenticationRecords that a visitor signed in through your own login system, linking their device to the user with that email address.
Action
Register deviceRegisters a new visitor device in a Bread & Butter app and returns its device ID.
Action
Update user lead statusUpdates a user's lead status in a Bread & Butter app by setting their lead status rank.
Trigger
New ClientRequired permissions: - **crm.view**: allows view all resources. Here the dedicated support page.
Trigger
New ContactRequired permissions: - **crm.view**: allows view resources. Here the dedicated support page.
Trigger
New InvoiceRequired permissions: - **invoices.view**: allows view of invoices for projects where the user is PM or Account. - **invoices.view_other**: allows view of all invoices. Here the dedicated support page.
Trigger
New PersonHere the dedicated support page.
Trigger
New ProjectThis endpoint handles both the Project List and the Pipeline Opportunities as a single "project" resource. Required permissions: - **pipeline.view**: allows view resources where the user is the PM or the Account. - **pipeline.view_other**: allows view resources where the user is not the PM nor the
Trigger
Sent InvoiceTriggers when an invoice is in sent status.
Trigger
Updated ProjectTriggers when a project is created or updated.
Action
Archive a projectRequired permissions: - **pipeline.edit**: to update a project where the user is PM or Account - **pipeline.edit_other**: to update a project where the user is not PM nor Account Here the dedicated support page.
Action
Create a clientRequired permissions: - **crm.edit**: allows to create resources. Here the dedicated support page.
Action
Create a contactRequired permissions: - **crm.edit**: allows edit resources. Here the dedicated support page.
Action
Create an invoiceRequired permissions: - **invoices.create**: required to create invoices for projects where the user is PM or Account. - **invoices.create_other**: required to create invoices for projects where the user is not PM or Account.
Action
Create a personCreates a new person as a **placeholder**: a member of the team who can be planned and allocated on projects, but cannot sign in until invited. Required permissions: - **team.edit_user** or **team.edit_placeholder**: allows creation of placeholder persons. [Here the dedicated support page](https:/
Action
Create a person allocationRequired permissions: - **planning.modify**: to create allocation for a project where the user is PM or Account - **planning.modify_other**: to create allocation for a project where the user is not PM nor Account - **planning.modify_past**: to create allocation on today or in a date in the past [He
Action
Create a projectRequired permissions: - **pipeline.create**: to create a project the user is PM or Account - **pipeline.create_other**: to create a project where the user is not PM nor Account Here the dedicated support page. ### Project met
Action
Create a project statusRequired permissions: - **project_status.create**: allows to create resources of projects where the user is the PM or the Account. - **project_status.create_other**: allows to create resources of projects where the user is not the PM nor the Account.
Action
Create a timesheetRequired permissions: - **timetracking.view**: allows to create resources. Here the dedicated support page.:::warning Detailed mode is not supported yet.
Action
Delete a clientRequired permissions: - **crm.edit**: allows to delete resources. Here the dedicated support page.
Action
Delete a contactRequired permissions: - **crm.edit**: allows edit resources. Here the dedicated support page.
Action
Delete an invoiceRequired permissions: - **invoices.delete**: required to delete invoices for projects where the user is PM or Account. - **invoices.delete_other**: required to delete invoices for projects where the user is not PM or Account. - **invoices.edit_sent**: required to delete sent/paid invoices.
Action
Delete a person allocationRequired permissions: - **planning.modify**: to delete allocation for a project where the user is PM or Account - **planning.modify_other**: to delete allocation for a project where the user is not PM nor Account - **planning.modify_past**: to delete allocation on today or in a date in the past [He
Action
Delete a projectRequired permissions: - **pipeline.delete**: to delete project where the user is PM or Account - **pipeline.delete_other**: to delete project where the user is not PM nor Account Here the dedicated support page.
Action
Delete a timesheetRequired permissions: - **timetracking.view**: allows to delete resources. Here the dedicated support page.
Action
Find ClientFinds the first client whose name matches the search text.
Action
Find PersonFinds the first person whose name or email matches the search text.
Action
Get a budgetRequired permissions: - **budget.view**: allows view resources of projects where the user is the PM or the Account. - **budget.view_other**: allows view resources of projects where the user is not the PM nor the Account. Here the dedicated support page.
Action
Get a clientRequired permissions: - **crm.view**: allows view all resources. Here the dedicated support page.
Action
Get a contactRequired permissions: - **crm.view**: allows view resources. Here the dedicated support page.
Action
Get an expenseRequired permissions: - **expenses.view**: allows view the expense if the user is the owner. - **expenses.view_other**: allows view the expense if the user is not the owner. Here the dedicated support page.
Action
Get an invoiceRequired permissions: - **invoices.view**: allows view of invoices for projects where the user is PM or Account. - **invoices.view_other**: allows view of any invoice. Here the dedicated support page.
Action
Get a personHere the dedicated support page.
Action
Get a projectThis endpoint handles both the Project List and the Pipeline Opportunities as a single "project" resource. Required permissions: - **pipeline.view**: allows view resources where the user is the PM or the Account. - **pipeline.view_other**: allows view resources where the user is not the PM nor the
Action
Get a stream:::warning Requires **Streams** to be enabled in company settings. :::
Action
Get the authenticated personReturns the person data associated with the currently authenticated user. No specific permissions are required beyond authentication.
Action
List budgetsRequired permissions: - **budget.view**: allows view resources of projects where the user is the PM or the Account. - **budget.view_other**: allows view resources of projects where the user is not the PM nor the Account. Here the dedicated support page.
Action
List business unitsRequired permissions: - **settings.company**: allows view of company business units.
Action
List clientsRequired permissions: - **crm.view**: allows view all resources. Here the dedicated support page.
Action
List contactsRequired permissions: - **crm.view**: allows view resources. Here the dedicated support page.
Action
List expensesRequired permissions: - **expenses.view**: allows view expenses where the user is the owner. - **expenses.view_other**: allows view expenses where the user is not the owner. Here the dedicated support page.
Action
List invoicesRequired permissions: - **invoices.view**: allows view of invoices for projects where the user is PM or Account. - **invoices.view_other**: allows view of all invoices. Here the dedicated support page.
Action
List job titlesRequired permissions: - **settings.company**: allows view of job titles. Here the dedicated support page.
Action
List people allocationsRequired permissions: - **planning.view**: allows view of resources owned by the user. - **planning.view_other**: allows of view resources not owned by the user. Here the dedicated support page.
Action
List personsHere the dedicated support page.
Action
List projectsThis endpoint handles both the Project List and the Pipeline Opportunities as a single "project" resource. Required permissions: - **pipeline.view**: allows view resources where the user is the PM or the Account. - **pipeline.view_other**: allows view resources where the user is not the PM nor the
Action
List project statusesRequired permissions: - **project_status.view**: allows view resources of projects where the user is the PM or the Account. - **project_status.view_other**: allows view resources of projects where the user is not the PM nor the Account.
Action
List project typesList project types
Action
List streams:::warning Requires **Streams** to be enabled in company settings. :::
Action
List timesheetsRequired permissions: - **timetracking.view** Here the dedicated support page.
Action
Set an invoice as paidRequired permissions: - **invoices.edit_sent**: allows setting invoices as paid.
Action
Set an invoice as unpaidRequired permissions: - **invoices.edit_sent**: allows setting invoices as unpaid.
Action
Unarchive a projectRequired permissions: - **pipeline.edit**: to update a project where the user is PM or Account - **pipeline.edit_other**: to update a project where the user is not PM nor Account Here the dedicated support page.
Action
Update a clientRequired permissions: - **crm.edit**: allows to update resources. Here the dedicated support page.
Action
Update a contactRequired permissions: - **crm.edit**: allows edit resources. Here the dedicated support page.
Action
Update an invoiceRequired permissions: - **invoices.edit**: required to update invoices for projects where the user is PM or Account. - **invoices.edit_other**: required to update invoices for projects where the user is not PM or Account. - **invoices.edit_sent**: required to update sent/paid invoices.
Action
Update a personRequired permissions: - **team.edit_user** or **team.edit_placeholder**: allows update of placeholder persons. - **team.edit_user**: allows update of invited and active persons. Here the dedicated support page.
Action
Update a person allocationRequired permissions: - **planning.modify**: to create allocation for a project where the user is PM or Account - **planning.modify_other**: to create allocation for a project where the user is not PM nor Account - **planning.modify_past**: to create allocation on today or in a date in the past [He
Action
Update a projectRequired permissions: - **pipeline.edit**: to update a project where the user is PM or Account - **pipeline.edit_other**: to update a project where the user is not PM nor Account - **pipeline.job_order**: to update a project job order [Here the dedicated support page].
Action
Update a timesheetRequired permissions: - **timetracking.view**: allows to update resources. Here the dedicated support page.:::warning Detailed mode is not supported yet.
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 Bread & Butter
Bread & Butter to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Bread & Butter to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Bread & Butter to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Bread & Butter to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Bread & Butter to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Bread & Butter to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into wethod
HubSpot to wethodHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to wethodSalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to wethodSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to wethodGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to wethodGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to wethodGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Bread & Butter and wethod, answered
What can start an automation from Bread & Butter?
Any of Bread & Butter's 6 triggers in the catalog, including New Authentication, New Contact Us Submission, New Custom Fields and New Custom User Event. Describe the moment in plain language and your agent picks the right one.
What can your agent do in wethod when something happens in Bread & Butter?
Any of wethod's 50 actions, including Create a client, Create a contact, Create an invoice and Create a person. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from wethod to Bread & Butter?
Yes. When something happens in wethod, your agent can act in Bread & Butter too. This page covers both directions: wethod's triggers and Bread & Butter's actions are listed here as well.
Do I have to build a connector for Bread & Butter or wethod?
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 Bread & Butter and wethod 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.