Learn Mokapen

Zapier

Zapier connects Mokapen to thousands of other apps. In Mokapen there is no account to authorize with OAuth: the page tells you there is nothing to connect here. Zapier talks to Mokapen via API, and Mokapen only needs a token.

Overview: Integrations. Internal automations (when a card changes, do this) stay in Automations. Zapier is for when the other app has no dedicated Mokapen integration.

Requirements

• Mokapen Small plan or higher. Below that, the button opens the upgrade.
• An API token created in Developers. It is created by whoever has access to that section: Administrator, with Large plan or higher for the Developer area.
• A Zapier account where Mokapen is trigger or action.

How you connect, since the page does not authorize

1. In Mokapen open Developers and create an API token. Keep it: Zapier asks for it once, and anyone with the token acts with that token’s permissions.
2. On the Zapier card in Integrations press the button. It opens the Mokapen page on Zapier (zapier.com/apps/mokapen/integrations).
3. In the Zap choose Mokapen as trigger or as action and paste the token when Zapier asks for it.

There is no second “Connect” step in Mokapen. If the Zap fails, the token is expired, revoked or pasted wrong, or the token’s user cannot perform that operation in the CRM. Roles and visibility also apply to API calls: a Limited User’s token does not invite colleagues and does not open someone else’s private card.

When you do not need Zapier

• The app already has a guide in this section (Brevo, Slack, Shopify, calendars). The direct integration keeps sync, errors and permissions inside Mokapen. Zapier adds a third place where sync can stop.
• The rule is “when a Mokapen card changes, update another Mokapen card”. That is an internal automation.
• You only want to send emails in sequence. That is Sequences, with the SMTP mailboxes.