Resources · Zapier integration

Mokapen Zapier integrationAutomate Mokapen with Zapier.

The Mokapen Zapier integration gives you 9 triggers, 8 actions and 0 searches. Every trigger is instant, so a new deal, contact or ticket in your CRM can start work in another app straight away, and the actions let other tools create records in Mokapen.

Beta app Zapier still marks this integration as beta.

See the 17 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Mokapen Zapier integration actually does

It connects Mokapen, a CRM built for small and medium teams and for freelancers, to the rest of your tools. You build a Zap (an automation that starts from one event and runs one or more steps after it), and Zapier carries it out every time that event happens. Zapier lists the Mokapen integration as beta.

A deal log outside the CRM. New Deal starts a Zap the moment a deal is created in Mokapen. Put a spreadsheet after it and every new deal becomes a row the whole team can read without opening Mokapen.

Leads that land in Mokapen on their own. Create New Contact and Create New Company let another app write into your CRM. A sign-up form or a booking tool can feed Mokapen directly, so nobody retypes names from an inbox.

Support that turns into work. New Ticket can hand each new ticket to Create New Task, so the request shows up in someone's task list instead of waiting to be noticed.

What Zapier does not do for Mokapen. Every action creates something; none updates or deletes a record. There is no search step, so a Zap cannot fetch a record that is already in Mokapen. Quotes can start a Zap, but no action creates one. And every trigger is about something new: none is offered for a change on an existing record.

If you are still deciding whether Zapier fits your CRM work, see our Zapier review.

Vocabulary

Zapier vocabulary in one minute

Eight words carry this page. Here they are once, in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it. Mokapen has nine, from deals to tickets.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you, like creating a task.
Task
The unit Zapier bills: one action your Zap completes successfully. Not to be confused with a Mokapen task.
Instant vs polling
An instant trigger is reported by the app the moment it happens. A polling trigger is checked on a timer. All of Mokapen's are instant.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes it one, and it then needs a paid plan.
Connection
Your Mokapen account linked to Zapier once, then reused by every step that reads from or writes to Mokapen.
Cost

What it really costs in tasks

Mokapen is not a premium app, so it works from the free plan. Zapier bills in tasks, and only completed actions count.

  • Premium appNo, available on the free plan
  • Free plan100 tasks a month, two-step Zaps only
  • Trigger cost0 tasks
  • Mokapen triggersAll 9 instant, the grid does not apply

None of the nine triggers costs a task. Each action that succeeds counts once, so a Zap that creates a company and then a contact uses two tasks per run. An action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, each capped at two steps: one trigger, one action. A filter or a second action turns it into a multi-step Zap, which needs a paid plan. The grid below sets how often Zapier checks polling triggers on each plan. It does not apply to Mokapen, whose triggers are all instant and fire straight away on every plan.

Connect

Connect your Mokapen account

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need an account on Mokapen, plus read or write access on anything you do not own yourself and want the Zap to touch.

  2. 02

    Pick Mokapen

    Search for Mokapen by name in the dialog, select it, then click Add connection. A new tab opens so you can sign in to the Mokapen account your team works in.

  3. 03

    Grant access

    Sign in to Mokapen in that tab and allow Zapier to use the account. The connection is saved once, then reused by every Mokapen trigger and action you add later.

First Zap

Your first Zap: copy the deals that matter into a spreadsheet

GoalEach new Mokapen deal that meets your condition becomes a row in a spreadsheet anyone on the team can read.

  1. 01

    Build: set the trigger

    Create a Zap, pick Mokapen as the starting app and New Deal as the event, then choose your connection. The trigger is instant, so there is no interval to think about.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent deals of the connected account, so you map the next steps on a real one. Note which fields come back.

  3. 03

    Add the filter

    Click the plus icon and add Filter. Fill the three boxes: the field to look at, the rule, the value. The filter makes this a multi-step Zap, which needs a paid plan.

  4. 04

    Add the spreadsheet action

    Add your spreadsheet app and its add-a-row action, then map the deal fields from the test into the columns. Test the step and read what came back.

  5. 05

    Publish

    Click Publish to switch the Zap on. Deals created before that moment stay out of the sheet; only the new ones go through from then on.

Triggers

The 9 Mokapen triggers

9 events start a Zap when something happens in Mokapen, and 9 of them are instant: the app calls Zapier straight away, whatever your plan.

1

New Company

Instant trigger

In Zapier“Triggers when there's a new Company.”

Fires each time a company record is added to Mokapen and passes that account to the next steps. Useful when an organization, not a person, is what your other tools need to hear about.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when your invoicing or project tool should get a matching client entry once a new account is logged in the CRM.
Watch out
companies already in Mokapen when you publish never reach the Zap; only those added afterwards do.
2

New Contact

Instant trigger

In Zapier“Triggers when there's a new Contact.”

Hands every person newly added to your CRM to the following steps. Which contact details travel with it is something to read in the test rather than guess.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
to add each new contact to your mailing tool, so nobody exports a list by hand before a campaign.
Watch out
contacts already in Mokapen when you publish never reach the Zap; only those added afterwards do.
3

New Deal

Instant trigger

In Zapier“Triggers when there's a new Deal.”

Starts a Zap the moment an opportunity enters your pipeline. Whoever needs to act on it hears about it without opening Mokapen.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
to log each new deal in a shared spreadsheet, or to warn a colleague who has to prepare something for it.
Watch out
map the deal fields from the test, not from memory; what Mokapen sends is what the test shows.
4

New Product

Instant trigger

In Zapier“Triggers when there's a new Product is created.”

Reports each item added to the product list of your Mokapen account. It concerns your catalogue, not your customers, so it suits Zaps that keep another tool's list of what you sell in step with the CRM.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when a new product should also appear in your shop or invoicing tool.
5

New Project

Instant trigger

In Zapier“Triggers when there's a new project .”

Picks up each project opened in Mokapen. For a freelancer or a small team, that is the point where sold work becomes delivery work, and other tools need to know.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
to create a matching folder or board in the tool where the delivery happens.
Watch out
the test brings back the three most recent projects of the account, so map the fields on one of those, not on a project you remember.
6

New Quote

Instant trigger

In Zapier“Triggers when new Quote is created.”

Fires when a quote is created in Mokapen. It is the only quote operation in the integration: Zapier can react to quotes, but no action creates one.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
to tell your team that a new quote is out, in the chat tool it reads.
Watch out
quotes that existed before you publish the Zap never reach it.
7

New Service

Instant trigger

In Zapier“Triggers when new Service is created.”

Reacts to a service added to your Mokapen account, the counterpart of New Product for what you sell as time or expertise rather than as goods.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
when a new service line should be added to the list kept in your booking page or invoicing tool.
Watch out
each service it sends on costs one task in the action after it, not in the trigger.
8

New Task

Instant trigger

In Zapier“Triggers when there's a new Task.”

Sends each new Mokapen task to the next steps. Here task means a to-do in your CRM, not the unit Zapier bills, and the two are easy to mix up on the same screen.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
to mirror CRM to-dos into the calendar or task app where someone actually plans the day.
Watch out
each to-do it copies elsewhere costs one Zapier task in the action that follows.
9

New Ticket

Instant trigger

In Zapier“Triggers when new ticket is created.”

Catches each support ticket opened in Mokapen. Since it is instant, it is the trigger to pick when a request should reach a person without anyone refreshing the CRM.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
to post each new ticket in the channel your team reads, or to turn it into a task.
Actions

The 8 Mokapen actions

Mokapen gives you 8 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Store Ticket

Action

In Zapier“Create a ticket in the mokapen”

Opens a support ticket in Mokapen from a message or a form received in another app, so requests end up in one queue.

When to use it
when customers write through a contact form that is not connected to your CRM.
Watch out
Title is required; pick the incoming field that fits it in the test.
2

Create New Company

Action

In Zapier“Used to Create new Company in Mokapen”

Adds an organization to your CRM from data that arrived in another app, such as the company field of a sign-up form.

When to use it
before creating the people who work there, so contacts have an account to belong to.
Watch out
Name is required, so the step before must hand over a company name.
3

Create New Contact

Action

In Zapier“Used to create New contact”

Writes a new person into Mokapen: a lead captured somewhere else becomes a contact your team can work, with no retyping.

When to use it
behind a form, a booking tool or a newsletter sign-up.
Watch out
look in the test at which fields the step offers and what lands in Mokapen before you publish.
4

Create New Deal

Action

In Zapier“Used to create new Deal”

Opens an opportunity in your pipeline from an event elsewhere, so a request for a proposal turns into something your team can follow.

When to use it
when a quote request form or a qualified reply should go straight into the pipeline.
Watch out
a Title is required, so map something meaningful there.
5

Store New Product

Action

In Zapier“Used to store new product in mokapen”

Adds an item to your Mokapen product list from another catalogue, so the CRM offers the same things your shop or stock tool does.

When to use it
when products are created first in another tool and the CRM has to follow.
Watch out
Title is required; pick in the test the incoming field that best names the product.
6

Store New Project

Action

In Zapier“Used to create new Project in Mokapen”

Creates a project in Mokapen from a signal in another tool, once the work is confirmed outside the CRM.

When to use it
when a signed document or a paid invoice elsewhere means delivery can start.
Watch out
Title is required; if the trigger app has no obvious name for the project, build one from the fields the test shows.
7

Store Service

Action

In Zapier“Creates a Service in the Mokapen”

Creates a service entry in Mokapen, for offers sold as time or expertise rather than as goods.

When to use it
when a new offer defined in another tool should also be available in the CRM.
Watch out
Title is required, so the step before must provide one.
8

Create New Task

Action

In Zapier“Used to create new Task”

Puts a to-do in Mokapen for someone to act on. Each one created by a Zap also costs one Zapier task, two words for two different things.

When to use it
to turn an email, a ticket or a form reply into a follow-up nobody can forget.
Watch out
Title is required, and it is the line people read first.
When it breaks

When a Mokapen Zap breaks

Zapier ties no help article to Mokapen and lists no limit specific to it. What goes wrong is what goes wrong on any Zap.

  • Existing records are not picked up

    A Zap only reacts to what happens after you switch it on. Deals, contacts or tickets created before publishing never reach it; moving that backlog is a separate job.

  • A Zap that sets itself off again

    As a general precaution: a Zap that writes into the very place its own trigger watches can start itself again and again, and burn through your tasks fast.

  • A sudden huge batch

    If a trigger suddenly returns a very large batch, after a bulk import or a migration into the CRM, Zapier's flood protection can hold those items back.
Need help

Need help automating Mokapen with Zapier?

A person reads every message.

FAQ

Mokapen Zapier integration: frequent questions

01Is the Mokapen Zapier integration free?
Yes. Mokapen is not a premium app, so every one of its triggers and actions works on the free plan. That plan gives 100 tasks a month and unlimited Zaps, each limited to two steps: one trigger and one action. A Zap that logs every new deal in a spreadsheet fits. A Zap that logs only some deals does not, because the filter makes it multi-step, and multi-step Zaps need a paid plan. The triggers themselves never use a task.
02How many tasks does a Mokapen Zap use?
One task for each action that completes, nothing for the trigger. A Zap that turns each new ticket into a Mokapen task spends one task per ticket. A Zap that creates a company and then a contact spends two per run. Actions that fail are not counted. Do not confuse the two kinds of task: a to-do created in Mokapen is a CRM task, while the Zapier task is the unit on your bill, and each created to-do costs one of those.
03Does Mokapen send events to Zapier in real time?
Yes, all nine triggers are instant: the app tells Zapier the moment something happens, so the Zap starts right away, whatever your plan. The polling interval grid of the plans does not apply to them, and a Zap built on one shows a lightning bolt in the editor. That makes the free plan as fast as the paid ones for this app. The type of a trigger is set by the app itself and cannot be changed from the editor.
04What do you need to connect Mokapen to Zapier?
An account on Mokapen, plus read or write access on anything you do not own yourself and want the Zap to touch. Start from the Apps page of your Zapier account, click + Add connection, search for Mokapen, then sign in in the tab that opens and grant access. Use the account your team actually works in, since the records your Zaps create will land there. One connection serves every Mokapen trigger and action afterwards.
05Why does almost every Mokapen action ask for a Title?
Because Zapier marks that field as required on Store Ticket, Create New Deal, Store New Product, Store New Project, Store Service and Create New Task, and asks for a Name on Create New Company. The step that runs before the action has to deliver a value for it. When the trigger comes from a form or an inbox, pick the field that best names the record, such as a subject line, and look at the test result before you publish. A record with a clear title is also the one your team will find later in the CRM.
06What if the Mokapen operation you want is not available?
Then no Mokapen step can do it. The editor offers nine triggers for new records and eight actions that create records, and nothing that updates, deletes or searches. The Mokapen page on Zapier shows the current list, so check it before you design around a missing step. Moving a deal to another stage, closing a ticket or editing a contact stays in Mokapen itself; Zapier handles the moment something is created, on either side.
07Zapier, Make or n8n for Mokapen?
Pick on criteria rather than on a ranking. First, check that the other tool has a Mokapen connector at all, since this page only covers the one on Zapier. Second, look at your steps: on Zapier a trigger plus one action runs on the free plan, and every Mokapen trigger fires instantly there. Third, list the operations you need; if updates or searches matter, compare what each connector offers. Fourth, decide who in your team will look after the automation once it is published.
Same platform

Other docs you might need on this stack.

Browse all integrations