Integration
Connect Guru to Ashby
When Card Created fires in Guru, 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 Guru 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)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 Guru can start in Ashby
When Card Created in Guru
then Create Candidate Note 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 Guru and Ashby
Triggers and actions 8 triggers · 28 actions
- Announcement Sent
Triggers when a new Announcement is sent to your Guru team.
- Card Created
Triggers when a new Card is published in Guru.
- Card Unverified
Triggers when a Guru Card becomes unverified and needs review.
- Card Updated
Triggers when a Guru Card is edited.
- New Collection
Triggers when a new Collection is created in your Guru team.
- New Folder
Triggers when a new Folder is created in Guru.
- New Group
Triggers when a new user Group is created in your Guru team.
- User Added to Group
Triggers when a user is added to the chosen Guru Group.
- Add User to Group
Adds a team member to a Guru Group by email address.
- Archive Card
Archives a Guru Card so it no longer appears in its Collection.
- Ask a Question
Asks Guru a question and returns the AI answer drawn from your team's knowledge.
- Create Card
Creates a new Guru Card with a title and content in a Collection.
- Create Group
Creates a new user Group in your Guru team.
- Find Card
Finds Guru Cards matching search terms and returns the best match.
- Find Tag
Returns one Guru Tag by its ID.
- Remove User From Group
Removes a team member from a Guru Group.
- Search With Sources
Searches Guru and connected sources, returning matching documents with their sources.
- Unverify Card
Marks a Guru Card as unverified so its verifier is asked to review it.
- Verify Card
Marks a Guru Card as verified by the connected user.
- Add candidate tag
Adds an existing tag to a candidate in Ashby and returns the updated candidate.
- Add job
Creates a new job in Ashby with a title, department/team and location, optionally applying a job template, interview plan, employment type and brand.
- Add offer
Creates an offer for a candidate's application in Ashby by submitting the offer form for an offer process that has already been started.
- Change Job Consideration Stage
Moves a candidate's application (their consideration for a job) to a different interview stage, optionally with an archive reason and rejection email when archiving.
- Consider Candidate for Job
Considers 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.
- Create Candidate
Creates a new candidate in Ashby with their name, contact details, social profiles, location and source.
- Create Candidate Note
Adds a note to a candidate's profile in Ashby, optionally as HTML, private, or with notifications to subscribed users.
- Find Candidate
Returns up to 100 candidates whose email address and/or name match the values you supply.
- Find Job
Returns up to 100 jobs whose title or requisition ID matches the text you search for.
- Find Job Consideration
Returns the applications (candidates being considered) for a job in Ashby, optionally narrowed by application status and creation date.
- Find Opening
Returns the openings whose identifier matches the one you supply, including each opening's state, jobs, locations, hiring team and custom fields.
- Get candidate
Returns the full details of a single Ashby candidate, including contact info, tags, applications, files and custom field values.
- List departments
Returns all departments and teams in your Ashby account, optionally including archived ones or only those changed since a previous sync.
- List locations
Returns the office and remote locations set up in your Ashby account, optionally including archived locations and regions.
- Update Candidate
Updates an existing candidate's name, contact details, social links, source, credited user and location in Ashby. Fields left blank are not changed.
- Update job
Updates an existing job in Ashby — its title, team, location, default interview plan, employment type or requisition id.
- Update Opening
Updates 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 Guru
Guru to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Guru to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Guru to SlackSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Guru to MailchimpMailchimp marketing automation and email platform.
Guru to StripeStripe is a payment processing platform for online businesses.
Guru to ShopifyShopify is a commerce platform for online stores and retail point-of-sale.
More into Ashby
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
Guru and Ashby, answered
What can start an automation from Guru?
Any of Guru's 8 triggers in the catalog, including Card Created, Card Updated, New Collection and New Folder. Describe the moment in plain language and your agent picks the right one.
What can your agent do in Ashby when something happens in Guru?
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 Guru?
Ashby has no triggers in the catalog today, so automations start in Guru. 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 Guru 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 Guru 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.