Resources · Make integration

OnePageCRM Make integrationAutomate OnePageCRM with Make.

Can Make keep your OnePageCRM pipeline moving while you sell? The OnePageCRM Make integration gives you 16 modules: 4 instant triggers, 10 actions and 2 searches. This guide is for sales teams and founders, and it walks you from the API key to a first working scenario.

Try the OnePageCRM integration on MakeSee the 16 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the OnePageCRM Make integration do for you?

The OnePageCRM Make integration links your CRM account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a single brick such as a trigger, an action or a search. OnePageCRM tells Make when contacts, deals, notes or actions change, and Make can write contacts, notes and next actions back into the CRM.

No lead left without a next step. A web form in another app hands Make a new prospect, Create a Contact files it in OnePageCRM and Create a Next Action for a Contact puts the first call on a rep's list. Nobody has to remember to open the CRM.

Deals that reach the rest of the company. Watch New Deal fires as soon as a salesperson logs a deal, so an agency can post it to the team chat or add a row to a shared sheet for the delivery lead.

Notes that follow the customer. Watch New Note picks up what the account manager wrote after a call, and Search Notes or Get a Note fetches older notes when another tool needs the history.

The listed modules cover contacts, notes and next actions. For anything else in the OnePageCRM API, Make an API Call reuses the same connection. The same CRM often has an n8n node too; if you are weighing both tools, read n8n vs Make. To learn the editor properly, Make training is a good next stop, and Make pricing explains how operations are counted.

Connect

How do you connect OnePageCRM to Make?

  1. 01

    Copy your API key in OnePageCRM

    In OnePageCRM, click your profile icon at the top right, choose Apps and Integrations, then API under Utilities. Open the Configuration tab, click Show API key and copy the key. You need an active OnePageCRM account for this.

  2. 02

    Add a OnePageCRM module

    In your Make scenario, add any OnePageCRM module and click Create a connection. A connection is your OnePageCRM account linked to Make once, then reused by every OnePageCRM module you add later.

  3. 03

    Name it and paste the credentials

    Give the connection a clear label in Connection name (optional, but handy with several accounts), paste the credentials you copied from OnePageCRM or follow the on-screen instructions, and save. The module can now read your CRM.

First scenario

Your first scenario: new lead to next action

GoalWhen a form in another app sends a new lead, Make creates the contact in OnePageCRM and gives it a next action.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Pick the app that collects your leads, such as your form tool, and connect it.

  2. 02

    Add Create a Contact

    Click the + on the right, search OnePageCRM and pick Create a Contact. Link your account, then map the name and email the form module received into the matching contact fields.

  3. 03

    Plan the first call

    Add Create a Next Action for a Contact after it. Map the contact that the previous module just created, then write the action text, for example a discovery call for the new lead.

  4. 04

    Test with Run once

    Click Run once and submit a test entry in your form. Each module shows the bundles it received, a bundle being one item passed along, here one lead. Check OnePageCRM for the new contact.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, or use an instant trigger if your form app has one. Then switch the scenario on so every new lead gets its next step.

Triggers

Which OnePageCRM events can start a scenario?

4 modules start a scenario when something happens in OnePageCRM. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by OnePageCRM as soon as it happens.

OnePageCRM1Watch Action Events

Watch Action Events

Instant trigger

In Make“Triggers when an action is created or completed.”

Starts your scenario whenever a next action is created or marked done in OnePageCRM, so the follow-up work around a task happens without anyone copying it by hand.

How it fires
instant, OnePageCRM calls Make through a webhook as soon as the action is created or completed, which is shown by the lightning badge on the module.
When to use it
to log completed calls in a reporting sheet or to ping a manager when a rep closes a task.
Watch out
creation and completion both fire it, so add a filter if you only care about one of the two.
OnePageCRM2Watch Contact Events

Watch Contact Events

Instant trigger

In Make“Triggers when a contact is created or updated.”

Hands Make every contact that is added or edited in your CRM, which keeps other tools in step with the record your sales team trusts.

How it fires
instant, OnePageCRM pushes the event to Make through a webhook the moment the contact is created or updated.
When to use it
to copy fresh contacts into an email tool or a billing app as soon as a rep saves them.
Watch out
if the same scenario later runs Update a Contact on that record, the edit counts as an update too and may start the scenario again.
OnePageCRM3Watch New Deal

Watch New Deal

Instant trigger

In Make“Triggers when a new deal is created.”

Tells Make about each deal the moment it is created, which lets the people who deliver the work hear about a sale without opening OnePageCRM.

How it fires
instant, the CRM calls Make through a webhook as soon as the deal exists, with no polling interval to wait for.
When to use it
to announce a signed deal in a team channel or to open a project in your delivery tool.
Watch out
only new deals start it; changes to an existing deal do not reach this trigger.
OnePageCRM4Watch New Note

Watch New Note

Instant trigger

In Make“Triggers when a new note is created.”

Passes each new note to your scenario, so what a salesperson wrote after a meeting can land where the rest of the team works.

How it fires
instant, OnePageCRM notifies Make through a webhook right after the note is saved.
When to use it
to forward meeting notes to the account owner, or to keep a customer timeline in a shared document.
Watch out
edits to an older note do not fire it; pair Update a Note and Get a Note with another trigger if edits matter.
Modules

What can Make do inside OnePageCRM?

OnePageCRM gives you 12 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

OnePageCRM1

Create a Contact

Action

In Make“Creates a new contact.”

Adds a person to OnePageCRM from data another module brought in, so a lead from a form, a webinar or an inbox lands in the CRM without retyping.

When to use it
right after the step that captures a new prospect.
Watch out
it always creates a new record; run Search Contacts first if the person may already exist.
OnePageCRM2

Create a Next Action for a Contact

Action

In Make“Creates a next action for the selected contact.”

Puts a task on a chosen contact, the next action that OnePageCRM uses to tell a rep what to do next, so no new lead sits without a step.

When to use it
after Create a Contact, or when a trigger shows a customer needs a call back.
Watch out
it needs the contact it belongs to, so map it from an earlier module.
OnePageCRM3

Create a Note

Action

In Make“Creates a new note.”

Writes a note into the CRM from anything your scenario knows, such as a support ticket summary or a form answer, so the sales team sees the context in one place.

When to use it
when an event outside OnePageCRM deserves a trace on the customer record.
Watch out
a new note also wakes Watch New Note in any other active scenario.
OnePageCRM4

Delete a Contact

Action

In Make“Deletes the selected contact.”

Removes the chosen contact from OnePageCRM, which helps when a cleanup rule or a removal request comes from another system.

When to use it
at the end of a flow that has already confirmed the person must go, for example a deletion request logged elsewhere.
Watch out
Make cannot undo a delete, so test it with Run once on a dummy contact first.
OnePageCRM5

Delete a Note

Action

In Make“Deletes the selected notes.”

Erases the notes you select, handy for clearing notes that another scenario added by mistake or that hold data you should not keep.

When to use it
after Search Notes has isolated exactly the notes to remove.
Watch out
there is no undo, and a broad search passed straight into this module can wipe more than you meant.
OnePageCRM6

Get a Contact

Action

In Make“Returns the selected contact.”

Fetches one contact you already know, so the rest of the scenario can use its current details as they stand when the scenario runs.

When to use it
after Watch Action Events or Watch New Note, when you need the full person behind the event.
Watch out
it reads one known record; to find someone by a value, use Search Contacts.
OnePageCRM7

Get a Note

Action

In Make“Returns the selected note.”

Reads one specific note back from OnePageCRM, which is useful when a scenario must quote or forward what was written on a record.

When to use it
when an earlier module gives you the note and you want its full text before sending it on.
Watch out
it returns a single note; to go through several, use Search Notes instead.
OnePageCRM8

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the OnePageCRM API with the connection you already set up, so you can reach what the other modules leave out, as long as the OnePageCRM API offers it.

When to use it
when no listed module does what you need, for instance something about deals, which only Watch New Deal touches today.
Watch out
you write the request yourself, so keep the OnePageCRM API documentation open next to the editor.
OnePageCRM9

Update a Contact

Action

In Make“Updates the selected contact.”

Changes the details of an existing contact, so information collected elsewhere, like a new phone number from a support form, keeps the CRM record current.

When to use it
after Search Contacts has found the person to edit.
Watch out
if Watch Contact Events runs in the same scenario, this edit counts as a contact update and may trigger it again.
OnePageCRM10

Update a Note

Action

In Make“Updates the selected note.”

Rewrites an existing note, which lets a scenario append a status or correct a note it created earlier instead of piling up new ones.

When to use it
when one note per customer should stay current, such as a running summary.
Watch out
Watch New Note ignores edits, so other scenarios will not see the change.
OnePageCRM11

Search Contacts

Search

In Make“Searches for contacts.”

Looks up contacts in the CRM and returns every match as a separate bundle, which is how a scenario checks whether someone is already there.

When to use it
before Create a Contact, to avoid duplicates, or before Update a Contact to find the record.
Watch out
it can return zero, one or several contacts, and each one runs the next modules and costs operations.
OnePageCRM12

Search Notes

Search

In Make“Searches for notes.”

Finds notes matching your criteria and sends each one on as its own bundle, so you can collect a customer's history or target notes for cleanup.

When to use it
ahead of Delete a Note or Update a Note, or to export notes to another tool.
Watch out
an empty result stops the rest of the path, so test with a search that you know returns something.
Need help

Need help automating OnePageCRM with Make?

A person reads every message.

FAQ

OnePageCRM and Make: frequent questions

01Is the OnePageCRM Make integration free?
Yes, on the Make side. OnePageCRM is a standard app, available from the Free plan, which allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per run and files up to 5 MB. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and remove the scenario cap. Each module run on one bundle counts as one operation. You still need your own active OnePageCRM subscription, which is billed by OnePageCRM.
02What do you need to connect OnePageCRM to Make?
An active OnePageCRM account and its API key. You find the key under your profile icon, Apps and Integrations, API in the Utilities section, then the Configuration tab and Show API key. In Make, add a OnePageCRM module, click Create a connection and paste what you copied. For one of the Watch modules, create the webhook first, then the connection. After that, every OnePageCRM module reuses the same connection. If the connection fails, copy the key again from the Configuration tab and check that the OnePageCRM account is still active.
03Do OnePageCRM triggers in Make work in real time?
Yes. All four triggers are instant: Watch Action Events, Watch Contact Events, Watch New Deal and Watch New Note. OnePageCRM calls Make through a webhook as soon as the event happens, so your scenario does not wait for a polling interval. The 15 minutes schedule only matters when your scenario starts on another app's scheduled module. Keep in mind that each trigger covers a precise event: Watch New Deal sees new deals, not deal changes.
04What if a OnePageCRM module is missing in Make?
Use Make an API Call. It sends any request the OnePageCRM API accepts, with the connection you already created, so you can reach what the 16 listed modules leave out; deals are the obvious gap, since only Watch New Deal covers them. Check in the API documentation that what you need is there. You write the request yourself from the OnePageCRM API documentation. Test it with Run once and read the bundle it returns before you map it into the next modules.
05Should you use Make or n8n for OnePageCRM?
It depends on the tool your team already runs. On Make, OnePageCRM brings 16 modules, including 4 instant triggers and a Make an API Call module for the rest of its API, and it works from the Free plan. The same CRM often has an n8n node as well. Compare the modules each tool offers for the events you care about, then pick the editor you are comfortable maintaining. Whichever you pick, start small: one trigger, one action, a test run, then switch it on.
Same platform

Other docs you might need on this stack.

Browse all integrations