Grist and Moco automations
Grist holds records you edit like a sheet, and Moco books “Create Incoming Payment” when “New Record” runs.
Set up an automation: when new record in Grist, create incoming payment in Moco
Build itOr have an AI agent work across Grist and Moco: it decides what to do in each on every run, on a schedule or when you ask it in its chat.
Grist and Moco in practice
Used for
Grist holds records you edit like a sheet, and Moco books “Create Incoming Payment” when “New Record” runs.
Best template
“New Record” in Grist, then “Create Incoming Payment” in Moco. A payment row added in Grist is booked in Moco, so the books follow the sheet.
Watch out
“Updated Record” in Grist also fires on edits, so using it with “Create Incoming Payment” can book a payment twice.
Grist and Moco templates
Pick one and Captain builds it with you.


When new record in Grist, create comment in Moco
Build this

When updated record in Grist, create comment in Moco
Build this

When new record in Grist, create incoming payment in Moco
Build this

When updated record in Grist, create incoming payment in Moco
Build this
Grist and Moco triggers and actions
Every one of both apps. A trigger starts the work; actions are the steps.
Triggers
4- New recordTriggers when a new Record is created.
- Updated recordTriggers when a Record is updated.
- New team createdTrigger When A new Team Create
- New or updated recordTriggers when a Record is updated, or a new Record is added.
No triggers match.
Actions
9- Create recordCreate a New Record in a Table
- Update recordUpdate an Existing Record in a Grist Table
- Delete record/sDelete existing records from a table
- Create tableCreate a New Table
- List team'sGet All Team's in grist
- Update an teamUpdate Your Team in Grist.
- Delete teamDelete team in grist
- Find or create recordFinds a Record in a Table Optionally, create a record if none are found.
- Create or update recordCreates a new Record in a Table, or Updates an existing matching Record.
No actions match.
Triggers
31- New projectTriggers when a new project is created
- New userTriggers when a new user is created
- New commentTriggers when a new comment is created
- New companyTriggers when a new company is created
- New contact personTriggers when a new contact person is created.
- New leadTriggers when a new lead was created.
- New expenseTriggers when a new expense is created.
- Project updatedTriggers when an existing project is updated.
- User updatedTriggers when an existing user is updated.
- Contact person updatedTriggers when a existing contact person is updated.
- New invoiceTriggers when a new invoice is created.
- Invoice updatedTriggers when a invoice is updated.
- Comment updatedTriggers when a comment is updated.
- Deal updatedTriggers when an existing lead is updated
- Company updatedTriggers when an existing company is updated
- New purchaseTriggers when a new purchase is created
- Purchase updatedTriggers when an existing purchase is updated
- New presenceTriggers when a new presence is created
- Presence updatedTriggers when an existing presence is updated
- New holiday requestAdd page-based pagination to fetch new MOCO holiday requests in scheduled runs.
- Holiday request updatedUpdate the timestamp format sent to MOCO’s holiday endpoint.
- New exported purchase [bookkeeping]Runs when a new purchase bookkeeping export is created.
- New exported invoice [bookkeeping]Runs when a new invoice bookkeeping export is created.
- New incoming paymentFormat updated_after as UTC ISO 8601 without milliseconds to satisfy the documented API format.
- New offerTriggers when a new offer is created.
- Updated offerEnter trigger Description Here
- New planning entryTriggers when a new planning entry is created.
- Planning entry updatedTriggers when an existing planning entry is updated, using native updated_after incremental sync.
- New project assignmentTriggers when a new project is assigned to the current user.
- Expense updatedTriggers when an existing project expense is updated.
- New taskUpdated scheduled New Task trigger to use Moco's documented updated_after pagination, added required validation, errorComponent handling, and improved sample fallback.
No triggers match.
Actions
22- Create projectCreates a new project.
- Create commentCreates a new comment.
- Create companyCreates a new company (customer only).
- Create contactUpdated Create Contact perform code to stop forcing company_id and user_id to Number, resolving 422 validation errors.
- Create expenseCreates a new Project Expense.
- Create incoming paymentCreates a new incoming payment.
- Create dealCreates a new lead in MOCO using the provided name, contact, company, tags, and dates.
- Create outgoing paymentCreates a new outgoing payment.
- Create purchaseCreates a new purchase.
- Create taskCreates a new task inside a project in MOCO.
- List companyFinds an existing Company.
- List contactFinds an existing Contact.
- List expenseRepair missing input fields and add boolean expense filters without changing perform code.
- List invoiceFinds an existing Invoice.
- List offerFinds an existing Offer.
- List planning entryFinds an existing Planning Entry.
- List projectFinds an existing project.
- List purchaseFinds an existing Purchase.
- List userFinds an existing active user.
- List taskFinds an active Task for a Project.
- List purchase categoryFinds an existing purchase category.
- List dealApply the approved visibility-only fix to Filters, Filter Values, and Pagination; preserve all other fields, perform code, and component mappings.
No actions match.
Questions about Grist and Moco
What can start a Grist and Moco automation?
“New record” and “Updated record”.
Which other apps work with both Grist and Moco?
HubSpot, Notion, ATZ CRM and Zoho Sheet. Each one has templates with Grist and with Moco, so a third app can join the same job.
All Grist integrations · All Moco integrations · Every app, A to Z