Integration
Connect Grist to Aurora Inbox
When something happens in Grist, your agent does the next thing in Aurora Inbox. Describe it 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 Grist and Aurora Inbox to do together?
Ask the assistant
Connect your AI client
Give your AI client this address.
https://mcp.apiant.aiAny 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 Grist can start in Aurora Inbox
When New or Updated Record in Grist
then Add chat in Aurora Inbox
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 Aurora Inbox
Triggers and actions 4 triggers · 41 actions
- New or Updated Record
Triggered when a row in a Grist table is created or updated.
- New or Updated Record (Instant)
Triggers when a Record is updated, or a new Record is added.
- New Record
Triggered when a new row is added to a Grist table.
- New Record (Instant)
Triggers when a new Record is created
- Add Column
Adds a column to a table in a Grist document.
- Add Table
Creates a new table in a Grist document, optionally with a starting set of columns.
- Create Document
Creates a new document in a Grist workspace and returns its document ID.
- 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.
- Create Record
Adds a new row to a Grist table and returns its row ID.
- Create Workspace
Creates a new workspace in a Grist organization and returns its ID.
- Delete Document
Deletes a Grist document permanently.
- Delete Records
Deletes one or more rows from a Grist table by row ID.
- Delete Workspace
Deletes a Grist workspace along with every document inside it.
- Find Record
Searches a Grist table for a row whose column holds a given value and returns that row's ID and column values.
- Get Document
Returns the details of one Grist document — its name, web address, workspace, and organization.
- Get Org
Returns the details of one Grist organization (team site) — its name, subdomain, owner, and your access level.
- Get Workspace
Returns the details of one Grist workspace, including the documents it contains.
- List Columns
Returns the columns of a Grist table, with each column's ID, label, and type.
- List Orgs
Returns every Grist organization (team site) this connection can reach.
- List Tables
Returns the tables in a Grist document.
- List Workspaces
Returns the workspaces in a Grist organization, each with the documents it contains.
- Run SQL Query
Runs a read-only SELECT statement against a Grist document and returns the rows.
- Update Document
Renames a Grist document or changes whether it is pinned. Anything left blank stays as it is.
- Update Record
Changes the column values of one row in a Grist table. Columns left blank keep their current values.
- Update Workspace
Renames a Grist workspace.
- Add chat
Creates a new chat conversation for a contact on a specific channel.
- Add company
Adds a new company.
- Add tag
Creates a tag in Aurora Inbox that can be attached to any chat. If a tag with the same name already exists, that tag is returned.
- Create Opportunity
Create a new opportunity
- Delete contact
Deletes a contact by its ID.
- Find chats by criteria
Returns up to 25 chats that match the specified search term, channel, team, unanswered and unread criteria.
- Get Chat
Returns one chat by id: contact, channel, channel type, owner, agents and status flags.
- Get company
Fetches a single company by id.
- Get contact
Fetches a single contact by id.
- Get or Create Contact
Finds a contact by phone number, or creates one when no contact has that number. When a contact is found, any name, email, company name and custom property values you supply are applied to it.
- List Chat Opportunities
Returns the opportunities (deals) attached to a chat.
- List Chat Tags
Returns all tags currently attached to a chat: attachment id, roomId, tagId, tagName.
- List companies
Lists companies in Aurora Inbox, optionally filtered by a keyword search.
- List tags
Returns all tags configured in the Aurora Inbox account, optionally with the number of chats tagged with each.
- List teams
Returns all teams configured in the Aurora Inbox account, including their members and roles.
- Send media message
Sends a file (image, video, audio or document) to an Aurora Inbox chat, with an optional caption.
- Send message
Sends a text message, or an internal note visible only to agents, to an Aurora Inbox chat.
- Tag chat
Attaches a tag to a chat, either an existing tag or one looked up by name (created if no tag with that name exists). If the chat already has the tag, the existing attachment is returned.
- Update company
Updates fields on an existing company.
- Update Contact
Updates an existing contact's name, phone, email, company name and custom property values. Blank fields keep their current values.
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 Grist
Grist to GmailGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Grist to HubSpotHubSpot is your all-in-one stop for all of your marketing software needs.
Grist to SalesforceSalesforce is a leading enterprise customer relationship management (CRM) platform.
Grist to Google SheetsGoogle Sheets
Grist to Google DriveGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Grist to MailchimpMailchimp marketing automation and email platform.
More into Aurora Inbox
Slack to Aurora InboxSlack is a messaging platform for teams. Post messages, manage channels, users, reminders, and react to...
Google Calendar to Aurora InboxGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Questions
Grist and Aurora Inbox, 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 Aurora Inbox when something happens in Grist?
Any of Aurora Inbox's 20 actions, including Create Opportunity, Send media message, Send message and Update company. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from Aurora Inbox to Grist?
Aurora Inbox has no triggers in the catalog today, so automations start in Grist. If you need the other direction, ask: your agent reads Aurora Inbox's API documentation and adds it.
Do I have to build a connector for Grist or Aurora Inbox?
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.
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.