--- title: "Connect Grist to Ashby - APIANT.ai" description: "When \"New or Updated Record\" fires in Grist, your agent runs \"Create Candidate Note\" in Ashby." canonical: "https://apiant.ai/connect/grist-to-ashby" --- # Connect Grist to Ashby When **New or Updated Record** fires in [Grist](https://apiant.ai/connections/grist), your agent runs **Create Candidate Note** in [Ashby](https://apiant.ai/connections/ashby). Describe the whole flow and it is built, tested on every scenario and kept running. Grist **4** triggers Grist **21** actions Ashby **17** actions What the catalog holds today. Ask for anything missing and your agent reads the API documentation and adds it. ## What do you want Grist and Ashby to do together? Give your AI client this address. `https://mcp.apiant.ai` One 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.ai` Start Claude Code there, approve the server, and sign in in the browser page it opens. [Claude Code guide (opens in a new tab)](https://apiant.ai/docs/mcp/claude-code) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### Zed Open Settings, then AI, then MCP Servers, then Add Server, then Add Remote Server. [Setup guide (opens in a new tab)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) ### 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)](https://apiant.ai/docs/mcp) Example flows ## What Grist can start in Ashby - When **New or Updated Record** in Grist then **Create Candidate Note** in Ashby - When **New Record** in Grist 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 Grist and Ashby ## Triggers and actions 4 triggers · 38 actions - Trigger **New or Updated Record** Triggered when a row in a Grist table is created or updated. - Trigger **New or Updated Record (Instant)** Triggers when a Record is updated, or a new Record is added. - Trigger **New Record** Triggered when a new row is added to a Grist table. - Trigger **New Record (Instant)** Triggers when a new Record is created - Action **Add Column** Adds a column to a table in a Grist document. - Action **Add Table** Creates a new table in a Grist document, optionally with a starting set of columns. - Action **Create Document** Creates a new document in a Grist workspace and returns its document ID. - Action **Create or Update Record** Adds a row to a Grist table, or updates the existing row when the match column already holds the match value. Returns the row ID. - Action **Create Record** Adds a new row to a Grist table and returns its row ID. - Action **Create Workspace** Creates a new workspace in a Grist organization and returns its ID. - Action **Delete Document** Deletes a Grist document permanently. - Action **Delete Records** Deletes one or more rows from a Grist table by row ID. - Action **Delete Workspace** Deletes a Grist workspace along with every document inside it. - Action **Find Record** Searches a Grist table for a row whose column holds a given value and returns that row's ID and column values. - Action **Get Document** Returns the details of one Grist document — its name, web address, workspace, and organization. - Action **Get Org** Returns the details of one Grist organization (team site) — its name, subdomain, owner, and your access level. - Action **Get Workspace** Returns the details of one Grist workspace, including the documents it contains. - Action **List Columns** Returns the columns of a Grist table, with each column's ID, label, and type. - Action **List Orgs** Returns every Grist organization (team site) this connection can reach. - Action **List Tables** Returns the tables in a Grist document. - Action **List Workspaces** Returns the workspaces in a Grist organization, each with the documents it contains. - Action **Run SQL Query** Runs a read-only SELECT statement against a Grist document and returns the rows. - Action **Update Document** Renames a Grist document or changes whether it is pinned. Anything left blank stays as it is. - Action **Update Record** Changes the column values of one row in a Grist table. Columns left blank keep their current values. - Action **Update Workspace** Renames a Grist workspace. - Action **Add candidate tag** Adds an existing tag to a candidate in Ashby and returns the updated candidate. - Action **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. - Action **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. - Action **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. - Action **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. - Action **Create Candidate** Creates a new candidate in Ashby with their name, contact details, social profiles, location and source. - Action **Create Candidate Note** Adds a note to a candidate's profile in Ashby, optionally as HTML, private, or with notifications to subscribed users. - Action **Find Candidate** Returns up to 100 candidates whose email address and/or name match the values you supply. - Action **Find Job** Returns up to 100 jobs whose title or requisition ID matches the text you search for. - Action **Find Job Consideration** Returns the applications (candidates being considered) for a job in Ashby, optionally narrowed by application status and creation date. - Action **Find Opening** Returns the openings whose identifier matches the one you supply, including each opening's state, jobs, locations, hiring team and custom fields. - Action **Get candidate** Returns the full details of a single Ashby candidate, including contact info, tags, applications, files and custom field values. - Action **List departments** Returns all departments and teams in your Ashby account, optionally including archived ones or only those changed since a previous sync. - Action **List locations** Returns the office and remote locations set up in your Ashby account, optionally including archived locations and regions. - Action **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. - Action **Update job** Updates an existing job in Ashby — its title, team, location, default interview plan, employment type or requisition id. - Action **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. ## Each app on its own - [ **Grist** Grist combines the flexibility of a spreadsheet with the robustness of a database to organize your data...](https://apiant.ai/connections/grist) - [ **Ashby** Ashby's all-in-one recruiting software consolidates your ATS, Analytics, Scheduling, and CRM.](https://apiant.ai/connections/ashby) Reviews ## What our customers say ## More from Grist - [ **Grist to Gmail** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/grist-to-gmail) - [ **Grist to Clickhouse** Column-oriented database for real-time analytical SQL queries at petabyte scale.](https://apiant.ai/connect/grist-to-clickhouse) - [ **Grist to Mistral AI** Mistral AI is a platform for building, customizing, and deploying advanced AI models and agents for...](https://apiant.ai/connect/grist-to-mistral-ai) - [ **Grist to OpusClip** OpusClip is a AI video tool that turns long videos into viral shorts with captions and transcripts.](https://apiant.ai/connect/grist-to-opusclip) - [ **Grist to Postman** Postman is a platform for building and testing APIs.](https://apiant.ai/connect/grist-to-postman) - [ **Grist to RuneScape** The RuneScape Wiki API exposes data for RuneScape and Old School RuneScape.](https://apiant.ai/connect/grist-to-runescape) ## More into Ashby - [ **HubSpot to Ashby** HubSpot is your all-in-one stop for all of your marketing software needs.](https://apiant.ai/connect/hubspot-to-ashby) - [ **Salesforce to Ashby** Salesforce is a leading enterprise customer relationship management (CRM) platform.](https://apiant.ai/connect/salesforce-to-ashby) - [ **Slack to Ashby** Slack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...](https://apiant.ai/connect/slack-to-ashby) - [ **Google Sheets to Ashby** Google Sheets is Google's online spreadsheet app for creating, editing and sharing spreadsheets.](https://apiant.ai/connect/google-sheets-to-ashby) - [ **Gmail to Ashby** Gmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...](https://apiant.ai/connect/gmail-to-ashby) - [ **Google Calendar to Ashby** Google Calendar is a time management tool providing scheduling features, event reminders, and integration...](https://apiant.ai/connect/google-calendar-to-ashby) Questions ## Grist and Ashby, answered ### ### What can start an automation from Grist? Any of Grist's 4 triggers in the catalog, including New or Updated Record, New or Updated Record (Instant), New Record and New Record (Instant). Describe the moment in plain language and your agent picks the right one. ### ### What can your agent do in Ashby when something happens in Grist? 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 Grist? Ashby has no triggers in the catalog today, so automations start in Grist. 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 Grist 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 Grist 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.