MOCO

· #355 most-used

Run your agency's projects, time, and finances without the admin drag

CRMProjectsAnalyticsFinanceHRAccounting

MOCO is a lean cloud ERP built for agencies, consultancies, and IT service providers — covering the full delivery cycle from lead to invoice. It combines time tracking, project controlling, resource planning, CRM, invoicing, and expense management in one GDPR-compliant SaaS that is especially popular in the DACH region. Connect MOCO to Actionist and your agents can log billable hours, create and update leads, generate invoices, monitor project budgets, sync contacts, and react to real-time webhook events — all without leaving the chat.

Try MOCO with Actionist Visit MOCO

Average time saved

10 hours

per person · per month

≈ 1 workdays back

Eliminates manual work. Agents eliminate the manual cycle of logging time entries, chasing invoice status, updating lead stages, and pulling utilisation reports by hand each week.

Schedule

What your MOCO agent runs on autopilot

A week of scheduled jobs your Actionist agent will execute on your behalf.

28Scheduled jobs

7Agents at work

24/7Always on

Agents

Tue–Thu

Tue

Wed

Thu

10a

11a

12p

Multi-app workflows

MOCO × every other app you use

End-to-end automations that span multiple apps — each one a real business outcome.

6Workflows

7Apps spanned

~11 hrsSaved / week

5Personas served

For finance

Featured4 apps

Overdue invoice chase triggered automatically

Within about a minute of an invoice tipping to Overdue in MOCO, the agent retrieves the client contact details, sends a polite but firm payment reminder via Gmail, posts a comment on the invoice recording the chase, alerts the finance channel in Slack, and logs the debtor in the overdue tracker sheet — all before any human has opened their inbox.

~3 hrs

Time saved for your team — every week, on autopilot

The flow

Trigger·When a MOCO invoice status changes to Overdue

Trigger

Step 1

MOCO

New Invoice Status change to Overdue

read

Step 2

MOCO

Find Invoice to retrieve client contact and amount

write

Step 3

Gmail

Send payment reminder email to client contact

write

Step 4

MOCO

Create Comment on invoice logging the chase date and method

write

Step 5

Slack

Post overdue alert to #finance channel with amount and client

write

Step 6

Google Sheets

Append row to debtor log with invoice number, client, days overdue

Result

Send payment reminder email to client contactCreate Comment on invoice logging the chase date and methodPost overdue alert to #finance channel with amount and clientAppend row to debtor log with invoice number, client, days overdue

The win

Saved per run

20 min

Runs / week

~8×

No overdue invoice goes un-chased — every one triggers action within about a minute of the status change

Driven byFinance Agent

ROI

Savings

What your team gets back — two angles: what you stop doing manually, and what that's worth.

Without Actionist

What you do manually today

With Actionist

What your agent runs for you

Sales
40 min / week
Manual pipeline update in MOCO
Reps log into MOCO after each call to update lead stages, add activity notes, and mirror the update into the CRM — 10 minutes of admin per lead interaction.
Sales Agent
0 min
Agent updates pipeline across tools automatically
When a sales activity fires in MOCO, the agent mirrors it to HubSpot, posts to Slack, and schedules the follow-up task in ClickUp — reps focus on calls, not CRM hygiene.
Marketing
30 min / week
Manual lead source export and analysis
Marketing manually exports MOCO contacts and lead data to a spreadsheet each week, adds source attribution by hand, and calculates channel conversion rates.
Marketing Agent
0 min
Agent delivers attribution digest automatically
Every Wednesday the agent pulls MOCO lead data grouped by source tag and writes the pipeline-value-by-channel report to Google Sheets, no export required.
Customer Support
35 min / week
Manual project budget monitoring
PMs check each project's hours consumed in MOCO individually, comparing against budget by eye, and manually flag at-risk projects in the weekly status meeting.
Customer Support Agent
0 min
Agent flags at-risk projects before the stand-up
Every Monday the agent checks all active projects for budget consumption pace and posts a traffic-light summary to Slack before the team arrives, with comments on at-risk projects already logged.
Human Resources
45 min / week
Manual utilisation and capacity reporting
The resourcing manager manually pulls planning entries from MOCO, cross-checks against contracted hours, and compiles a capacity report in a spreadsheet before each Monday meeting.
Human Resources Agent
0 min
Agent surfaces utilisation and conflicts automatically
Every Monday at 7:30 AM the agent calculates planned allocation per team member, flags over-allocations and under-utilised capacity, and posts the overview to Slack before the resourcing meeting.
Finance
60 min / week
Manual invoice chase and payment reconciliation
Finance checks MOCO for overdue invoices, sends chase emails manually, logs payment receipts one by one, and maintains a separate debtor tracker in a spreadsheet.
Finance Agent
0 min
Agent handles chase, payment logging, and reporting automatically
Within about a minute of an invoice going overdue, the agent sends the chase email, creates a MOCO comment, posts to Slack, and updates the debtor tracker — no human action required.
Operations
90 min / week
Manual project setup after each contract signing
After a contract is signed, operations manually creates the MOCO project, adds task categories, creates planning entries, and sets up Slack and Notion for the client — 45 minutes of setup per project.
Operations Agent
0 min
Agent runs the full project setup sequence automatically
When a lead moves to Won, the agent creates the MOCO project, adds standard tasks, creates planning entries, spins up the Slack channel, and populates the Notion brief — everything ready before the PM's first call.
Legal
25 min / week
Manual contract billing schedule checks
Legal manually compares each new invoice against the associated contract's billing schedule by opening the contract document and the MOCO invoice side by side, once per billing run.
Legal Agent
0 min
Agent flags invoice-contract deviations before dispatch
Every Thursday the agent compares all recent MOCO invoices against contractual billing schedules and flags any deviation to legal and finance before the invoice reaches the client.

+ 100s of other MOCO automations

Average time saved

33 hrs / person / month

Calculator

Calculate what your team saves

Team size

5 people

Hourly rate

$75 / hr

Hours saved / week

Hours saved / year

625

Annual ROI

$46,875

Based on MOCO's typical team usage — the visible tasks plus a few other automations the agent runs: ~2.5 hrs / person / week of admin work automated.

Connect

How to plug MOCO into Actionist

Pick the connection method that suits your environment.

Connect MOCO to Actionist using your personal or account API key — the standard and recommended path for all MOCO integrations.

Open your MOCO profile

Copy your personal API key

Your personal key is shown on the Integrations tab. Copy it and store it somewhere safe — treat it like a password.

Paste into Actionist

Enter your API key and your MOCO account subdomain in the fields below, then click Test connection. Actionist will confirm access before any agent task runs.

Credentials you'll need

API Key*

MOCO → User profile → Integrations → Personal API key (or Settings → Extensions → API & Webhooks → API Keys for an account key)

Account subdomain*

The subdomain of your MOCO account, e.g. myagency (from myagency.mocoapp.com)

Actions

17 actions your agent can call

Read and write operations available to your Actionist agent.

Triggers

8 events your agent can react to

Events your agent watches for, and the actions it kicks off in response.

FAQs

Questions about MOCO + Actionist

How does Actionist connect to MOCO?

Go to the Apps tab in Actionist, find MOCO, and click Connect. MOCO uses API key authentication: log in to your MOCO account, open your user profile, navigate to Integrations, and copy your personal API key. If you need an account-level key (shared across users), an admin can create one under Settings > Extensions > API & Webhooks > API Keys. Paste the key into Actionist and click Test connection — Actionist makes a read-only call to confirm access before any action runs.

What permissions does the Actionist agent need in MOCO?

The permissions the agent inherits depend on the API key you provide. A personal API key gives the agent access aligned with your own MOCO role — if you can create invoices, so can the agent. An account API key created by an admin can be scoped more narrowly. For read-only agent tasks (finding time entries, looking up contacts, checking invoice status), a read-only user role is sufficient. For write tasks (creating projects, logging time, recording payments), the user associated with the key must have the relevant permissions in MOCO.

Can Actionist react to events in MOCO in close to real time?

Yes. MOCO supports webhooks, which Actionist uses to trigger agent tasks within about a minute of events such as new time entries, invoice status changes, new leads, project budget alerts, and new planning entries. Actionist registers a webhook subscription with MOCO during setup. If you need to handle events that MOCO does not yet publish as webhooks, the agent can also run scheduled polling tasks (for example, checking overdue invoices every Monday morning).

Which MOCO entities can Actionist read and write?

Actionist can read and write: time entries (Activities), projects, project tasks, companies, contacts (people), leads (Deals), invoices and payments, purchases and outgoing payments, expenses, planning entries (resource scheduling), presence records, and comments. For a full list of every API endpoint, see the MOCO API documentation at everii-group.github.io/mocoapp-api-docs.

Can I use Actionist to automate the full invoicing cycle in MOCO?

Yes, though invoice creation itself is not listed as a direct Actionist action — the agent uses the Find Invoice action to locate drafts, monitors invoice status changes via webhook triggers, logs incoming payments when a transfer clears, and sends payment reminders when invoices go overdue. For raising new invoices programmatically, you would use MOCO's bookkeeping export API to trigger the billing run, or pre-create invoice drafts in MOCO and let the agent handle the status tracking from there. The full receivables lifecycle — from draft to paid — is manageable within Actionist.

How does MOCO work with my other tools in an Actionist workflow?

MOCO slots into multi-app workflows as a source, destination, or both. Common patterns: when a deal closes in HubSpot, the agent creates a MOCO project; when a MOCO time entry is logged, the agent writes hours to a Google Sheets utilisation dashboard; when a MOCO invoice goes overdue, the agent sends a chase email via Gmail and posts to Slack. Any of Actionist's 500+ connected apps can send or receive data alongside MOCO in the same workflow.

Does Actionist work with the MOCO webhook for budget alerts?

Yes. MOCO fires a webhook when a project crosses a budget threshold — this is the New Project Budget Alert trigger in Actionist. When it fires, the agent can pull the current hours breakdown, post a warning to the project Slack channel, draft a scope extension note in Notion, and update a margin tracker in Google Sheets — all within about a minute of the alert. The exact threshold that triggers the webhook is configured inside MOCO itself under Settings > Extensions > API & Webhooks.

Is MOCO GDPR-compliant and where is data stored?

MOCO is a GDPR-compliant SaaS that stores data on servers in Germany (EU). It is ISO 27001 certified and specifically designed for the DACH market where data residency requirements are strict. When Actionist connects to MOCO, it reads data via the MOCO API and passes it only to the tools your workflow specifies — no MOCO data is stored in Actionist's own database. You control which agent actions run and which data flows where, through the Approval Modes setting in Actionist.