Integration
Connect Grist and SendPulse
When something happens in Grist or SendPulse, your agent does the next thing in the other. 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 SendPulse 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 and SendPulse can do together
From Grist to SendPulse
When New or Updated Record in Grist
then Add Subscriber in SendPulse
When New Record in Grist
then Create Webhook in SendPulse
From SendPulse to Grist
When New Subscriber in SendPulse
then Add Column in Grist
When New Subscriber in SendPulse
then Add Table in Grist
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 SendPulse
Triggers and actions 5 triggers · 30 actions
Trigger
New or Updated RecordTriggered 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 RecordTriggered when a new row is added to a Grist table.
Trigger
New Record (Instant)Triggers when a new Record is created
Action
Add ColumnAdds a column to a table in a Grist document.
Action
Add TableCreates a new table in a Grist document, optionally with a starting set of columns.
Action
Create DocumentCreates a new document in a Grist workspace and returns its document ID.
Action
Create or Update RecordAdds 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 RecordAdds a new row to a Grist table and returns its row ID.
Action
Create WorkspaceCreates a new workspace in a Grist organization and returns its ID.
Action
Delete DocumentDeletes a Grist document permanently.
Action
Delete RecordsDeletes one or more rows from a Grist table by row ID.
Action
Delete WorkspaceDeletes a Grist workspace along with every document inside it.
Action
Find RecordSearches a Grist table for a row whose column holds a given value and returns that row's ID and column values.
Action
Get DocumentReturns the details of one Grist document — its name, web address, workspace, and organization.
Action
Get OrgReturns the details of one Grist organization (team site) — its name, subdomain, owner, and your access level.
Action
Get WorkspaceReturns the details of one Grist workspace, including the documents it contains.
Action
List ColumnsReturns the columns of a Grist table, with each column's ID, label, and type.
Action
List OrgsReturns every Grist organization (team site) this connection can reach.
Action
List TablesReturns the tables in a Grist document.
Action
List WorkspacesReturns the workspaces in a Grist organization, each with the documents it contains.
Action
Run SQL QueryRuns a read-only SELECT statement against a Grist document and returns the rows.
Action
Update DocumentRenames a Grist document or changes whether it is pinned. Anything left blank stays as it is.
Action
Update RecordChanges the column values of one row in a Grist table. Columns left blank keep their current values.
Action
Update WorkspaceRenames a Grist workspace.
Trigger
New SubscriberTriggers when a new subscriber is created.
Action
Add SubscriberAdds a subscriber (email address, with optional variables and tags) to a SendPulse mailing list, with single or double opt-in.
Action
Change Variable for SubscriberUpdates one or more variable values for a subscriber in a SendPulse mailing list.
Action
Create WebhookCreates an Email service webhook that sends the chosen events to a URL. SendPulse creates one webhook per event.
Action
Delete ContactRemoves a contact's email address from a SendPulse mailing list.
Action
Get SubscriberFetches one subscriber of a mailing list by email address, including their status and variables. An error occurs if the email is not in the list.
Action
List Mailing ListsReturns the mailing lists (address books) in the SendPulse account.
Action
List WebhooksReturns the Email service webhooks registered on the account, optionally only those for one event.
Action
Unsubscribe UserMarks a contact as unsubscribed in a SendPulse mailing list without deleting it.
Action
Update SubscriberUpdates the variable values (such as name, phone or city) of an existing subscriber in a SendPulse mailing list.
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 SendPulse
HubSpot to SendPulseHubSpot is your all-in-one stop for all of your marketing software needs.
Salesforce to SendPulseSalesforce is a leading enterprise customer relationship management (CRM) platform.
Google Sheets to SendPulseGoogle Sheets
Gmail to SendPulseGmail is Google’s email service, featuring spam protection, search functions, and seamless integration with...
Google Calendar to SendPulseGoogle Calendar is a time management tool providing scheduling features, event reminders, and integration...
Google Drive to SendPulseGoogle Drive is a cloud storage solution for uploading, sharing, and collaborating on files across devices...
Questions
Grist and SendPulse, 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 SendPulse when something happens in Grist?
Any of SendPulse's 9 actions, including Create Webhook, Update Subscriber, Add Subscriber and Change Variable for Subscriber. Your agent maps the data both ways and tests every scenario before it ships.
Can it also run from SendPulse to Grist?
Yes. When something happens in SendPulse, your agent can act in Grist too. This page covers both directions: SendPulse's triggers and Grist's actions are listed here as well.
Do I have to build a connector for Grist or SendPulse?
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.