Integration
Connect Feathery to Chatbase
When Data Received fires in Feathery, your agent runs Add ticket message in Chatbase. 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 Feathery and Chatbase 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 Feathery can start in Chatbase
When Data Received in Feathery
then Add ticket message in Chatbase
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 Feathery and Chatbase
Triggers and actions 2 triggers · 29 actions
- Data Received
Triggers when an end user submits or updates data on a Feathery form.
- Form Completion
Triggers when an end user completes a Feathery form.
- Create Hidden Field
Creates a hidden field in your Feathery account.
- Create One-Time Link
Creates a one-time link that opens one submission of a Feathery form, optionally prefilled.
- Create or Fetch User
Creates a Feathery end user with the given ID, or returns the existing user, including its SDK key.
- Create or Update Submission
Sets field values for a Feathery user and initializes submissions on the given forms.
- Delete User
Deletes a Feathery end user and their submissions.
- Get User Field Data
Returns every field value a Feathery user submitted across forms.
- Get User Form Session
Returns a Feathery user's form session: every form they are working on and their progress.
- List Document Templates
Returns document templates uploaded by your Feathery team, optionally filtered by name or tags.
- List Forms
Returns your Feathery forms, optionally filtered by tags or active status.
- List Form Submissions
Returns submissions for a Feathery form, optionally filtered by user, completion and update time.
- List Hidden Fields
Returns all hidden fields in your Feathery account.
- List Users
Returns your Feathery end users, optionally filtered by creation time or a field value.
- Add agent
Creates a new Chatbase agent (chatbot), optionally trained on supplied text.
- Add source
Adds a training source (text, Q&A, or website link) to a Chatbase agent. The source starts training immediately.
- Add ticket message
Posts a customer-visible reply to a Chatbase helpdesk ticket on behalf of a team member. Delivery to the customer happens asynchronously.
- Delete agent
Permanently deletes a Chatbase agent and all of its associated data.
- Delete conversation
Deletes a conversation from an agent, whatever channel it came from. It no longer appears in chat logs.
- Delete source
Deletes a source from a Chatbase agent, removing its knowledge from the agent. Returns the source in its final state.
- Find conversations by text
Searches an agent's conversations by free text and optional filters, returning matching conversations with highlighted snippets.
- Get agent
Returns a single Chatbase agent with its instructions, model, visibility, styles and training status.
- Get conversation
Returns a conversation's details and its most recent messages. Only conversations created through the API are returned.
- List agents
Returns all agents (chatbots) in your Chatbase account, with each agent's name, model, training status and settings.
- List conversations
Returns the conversations created through the API for a Chatbase agent, optionally limited to a creation date window.
- List sources
Returns the training sources (links, files, Q&A, Notion pages, text) of a Chatbase agent, optionally filtered by type or name.
- List tickets
Returns the helpdesk tickets for a Chatbase agent, optionally filtered by status, channel, assignee, team, priority and creation date.
- Send Prompt
Sends a message to a Chatbase agent and returns the agent's reply, starting a new conversation or continuing an existing one.
- Update agent
Updates an existing Chatbase agent's name, instructions, model and other settings. Only the fields you fill in are changed.
- Update source
Updates an existing text, Q&A or link source on a Chatbase agent. Changing content retrains the source.
- Update ticket
Updates a Chatbase helpdesk ticket's status, assignee, team or priority. Only the fields you fill in are changed.
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 Feathery
Feathery to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Feathery to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Feathery to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Feathery to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Feathery to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Feathery to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Chatbase
Questions
Feathery and Chatbase, answered
What can start an automation from Feathery?
Any of Feathery's 2 triggers in the catalog, including Data Received and Form Completion. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Chatbase when something happens in Feathery?
Any of Chatbase's 17 actions, including Send Prompt, Update agent, Update source and Update ticket. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Chatbase to Feathery?
Chatbase has no triggers in the catalog today, so automations start in Feathery. If you need the other direction, ask: your agent reads Chatbase's API documentation and adds it.
Do I have to build a connector for Feathery or Chatbase?
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 Feathery and Chatbase 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.