Integration
Connect FeedHive to Ashby
When New Label fires in FeedHive, your agent runs Create Candidate Note in Ashby. 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 FeedHive and Ashby 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 FeedHive can start in Ashby
When New Label in FeedHive
then Create Candidate Note in Ashby
When Post Failed in FeedHive
then Add candidate tag in Ashby
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 FeedHive and Ashby
Triggers and actions 4 triggers · 31 actions
Trigger
New LabelTriggers when a FeedHive label is created.
Trigger
Post FailedTriggers when a FeedHive post fails to publish.
Trigger
Post PublishedTriggers when a FeedHive post is published.
Trigger
Post ScheduledTriggers when a FeedHive post is scheduled.
Action
Create LabelCreates a FeedHive label.
Action
Create PostCreates a FeedHive post as a draft or scheduled for a future time.
Action
Delete LabelDeletes a FeedHive label and returns the deleted label.
Action
Delete PostDeletes a FeedHive post and returns the deleted post.
Action
Get LabelReturns one FeedHive label.
Action
Get PostReturns one FeedHive post.
Action
Get Post AnalyticsReturns analytics for every social publication of a FeedHive post.
Action
Get Social AccountReturns one connected social account.
Action
Get Social Account AnalyticsReturns the latest analytics for a connected social account.
Action
List LabelsReturns your FeedHive labels.
Action
List PostsReturns your FeedHive posts, optionally filtered by status, label or social account.
Action
List Social AccountsReturns the social accounts connected to your FeedHive account or workspace.
Action
Update LabelRenames a FeedHive label.
Action
Update PostUpdates a FeedHive post. Each field you send replaces its current value.
Action
Add candidate tagAdds an existing tag to a candidate in Ashby and returns the updated candidate.
Action
Add jobCreates a new job in Ashby with a title, department/team and location, optionally applying a job template, interview plan, employment type and brand.
Action
Add offerCreates an offer for a candidate's application in Ashby by submitting the offer form for an offer process that has already been started.
Action
Change Job Consideration StageMoves a candidate's application (their consideration for a job) to a different interview stage, optionally with an archive reason and rejection email when archiving.
Action
Consider Candidate for JobConsiders a candidate for a job in Ashby by creating a new application, optionally placing it in a specific interview plan and stage with a source and credited user.
Action
Create CandidateCreates a new candidate in Ashby with their name, contact details, social profiles, location and source.
Action
Create Candidate NoteAdds a note to a candidate's profile in Ashby, optionally as HTML, private, or with notifications to subscribed users.
Action
Find CandidateReturns up to 100 candidates whose email address and/or name match the values you supply.
Action
Find JobReturns up to 100 jobs whose title or requisition ID matches the text you search for.
Action
Find Job ConsiderationReturns the applications (candidates being considered) for a job in Ashby, optionally narrowed by application status and creation date.
Action
Find OpeningReturns the openings whose identifier matches the one you supply, including each opening's state, jobs, locations, hiring team and custom fields.
Action
Get candidateReturns the full details of a single Ashby candidate, including contact info, tags, applications, files and custom field values.
Action
List departmentsReturns all departments and teams in your Ashby account, optionally including archived ones or only those changed since a previous sync.
Action
List locationsReturns the office and remote locations set up in your Ashby account, optionally including archived locations and regions.
Action
Update CandidateUpdates an existing candidate's name, contact details, social links, source, credited user and location in Ashby. Fields left blank are not changed.
Action
Update jobUpdates an existing job in Ashby — its title, team, location, default interview plan, employment type or requisition id.
Action
Update OpeningUpdates an existing opening in Ashby, such as its identifier, description, department, target dates, backfill flag or employment type. Returns the updated opening.
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 FeedHive
FeedHive to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
FeedHive to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
FeedHive to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
FeedHive to Google SheetsGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
FeedHive to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
FeedHive to Google CalendarGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
More into Ashby
HubSpot to AshbyHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to AshbySalesforce is a leading enterprise customer relationship management (CRM) platform.
Slack to AshbySlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Sheets to AshbyGoogle Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.
Gmail to AshbyGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to AshbyGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
FeedHive and Ashby, answered
What can start an automation from FeedHive?
Any of FeedHive's 4 triggers in the catalog, including New Label, Post Failed, Post Published and Post Scheduled. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Ashby when something happens in FeedHive?
Any of Ashby's 17 actions, including Create Candidate, Create Candidate Note, Update Candidate and Update job. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Ashby to FeedHive?
Ashby has no triggers in the catalog today, so automations start in FeedHive. If you need the other direction, ask: your agent reads Ashby's API documentation and adds it.
Do I have to build a connector for FeedHive or Ashby?
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 FeedHive and Ashby 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.