Resources · Make integration

OneDeck Make integrationAutomate OneDeck with Make.

Your OneDeck records can stay in step with the rest of your tools. The OneDeck Make integration gives you 10 modules: 8 actions and 2 searches. This page shows how to link your account, build a first scenario and pick the right module for each job.

Try the OneDeck integration on MakeSee the 10 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the OneDeck Make integration do for you?

The OneDeck Make integration lets Make read and write your OneDeck records and documents without code. You build a scenario, the automation Make runs for you, out of modules, each one a single brick: here, an action or a search on your OneDeck account.

New entries land in OneDeck on their own. Put the trigger of another app first, a form or a CRM for instance, then Create Record. Each new entry becomes a OneDeck record, and nobody retypes it.

Stale records get corrected in one pass. Search Records pulls the records that match your filter, and Update Record rewrites them. A sales team can fix a status on many records after a pricing change, for example.

Documents feed other tools. Search Documents and Get Document pass a document's details to the next module, so a report or a message can reuse them.

Know the limits before you start. OneDeck has no trigger in Make, so a scenario starts on its schedule or on another app's event. Its Make documentation also warns that it is AI-generated and may contain mistakes, so test each module with real data. If OneDeck also has an n8n node, read n8n vs Make before choosing. To go further, the Make training covers scenario design, and the Make pricing page explains how operations are counted.

Connect

How do you connect your OneDeck account to Make?

  1. 01

    Copy your OneDeck credentials

    In OneDeck, open Settings in the main menu, then General. Copy the Account Name and the API key shown on screen. Make needs both to reach your account.

  2. 02

    Add a OneDeck module in Make

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

  3. 03

    Paste the credentials and save

    Give the connection a clear label in Connection name if you want, then paste the account name and API key. Save, and Make can now list what your OneDeck account holds.

First scenario

Your first scenario: refresh OneDeck records in bulk

GoalWhen the scenario runs on its schedule, Make finds the OneDeck records you target and updates each one.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Search for OneDeck and pick Search Records.

  2. 02

    Link your account

    Click Create a connection and paste your account name and API key. Then fill the search so it targets only the records you want to change.

  3. 03

    Add Update Record

    Click the + on the right of Search Records and choose Update Record. Map the record from the search, then set the new values. Each record found is a bundle, one item passed to the next module.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received. Check in OneDeck that the right records changed, and only those.

  5. 05

    Schedule and switch on

    Open the clock on the first module. A new scenario runs every 15 minutes by default; pick the schedule that suits you, then switch the scenario on.

Modules

What each OneDeck module does

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

OneDeck1

Create Record

ActionIn the docs only

You get a fresh OneDeck record built from data that already sits in another tool, with no copy and paste. Make fills it from the modules placed before it.

When to use it
a new lead, order or form entry appears elsewhere and has to exist in OneDeck too.
Watch out
run it once with a test entry first, since every scenario run creates a new record.
OneDeck2

Document Published

ActionIn the docs only

Its name suggests it deals with OneDeck documents once they are published. It is listed as an action, not a trigger, and the documentation does not say what it returns, so that reading is a deduction.

When to use it
your scenario deals with documents that have gone live and you want OneDeck's side of it.
Watch out
it will not start a scenario by itself; test it with Run once and read its output before relying on it.
OneDeck3

Get Document

ActionIn the docs only

Get Document hands the next module the details of one OneDeck document you already know. That makes it the step that turns a reference into content you can map.

When to use it
an earlier module or a search has given you a specific document and you need what it holds.
Watch out
it reads one document; to find documents by a criterion, start with Search Documents.
OneDeck4

Get Record

ActionIn the docs only

With Get Record, your scenario reads the full content of a single OneDeck record and can reuse every value in later modules, such as an email or a spreadsheet row.

When to use it
you already hold a record's identifier, from Create Record or from another app, and need its current data.
Watch out
it returns one record only; if you do not know which one, Search Records fits better.
OneDeck5

Make an API Call

ActionIn the docs only

When the listed modules stop short, this one lets you call any endpoint of the OneDeck API from the scenario, with the connection you already set up. No new credentials are needed.

When to use it
you need an operation that none of the other nine modules offers.
Watch out
you write the request yourself, so keep the OneDeck API documentation open and test it with Run once.
OneDeck6

Record Created

ActionIn the docs only

Record Created is tied, by its name, to records newly added in OneDeck. It is listed as an action, not a trigger, and the documentation does not describe its output, so treat it as a step inside a running scenario.

When to use it
your flow cares about fresh OneDeck records and you want to check what this module returns for them.
Watch out
a scenario still needs a schedule or another app's trigger to start.
OneDeck7

Record Updated

ActionIn the docs only

Its name points to OneDeck records that have changed, which helps when a scenario must react to edits. It is listed as an action, and no official description says what it sends back.

When to use it
you are building a flow around modified records and want to see what OneDeck provides about them.
Watch out
run it once and inspect the bundles before you map its data into other apps.
OneDeck8

Search Documents

SearchIn the docs only

Search Documents gives you the list of OneDeck documents that match what you look for, so later modules can work through them. It can return zero, one or several documents.

When to use it
you do not know the exact document yet and need to find it first.
Watch out
each document found runs the following modules once, and every run counts as an operation on your plan.
OneDeck9

Search Records

SearchIn the docs only

Search Records returns the OneDeck records that match your criteria, ready to be updated, copied or sent elsewhere. The result may be empty, a single record or many.

When to use it
you need a batch of records, or you must check whether a record exists before creating it.
Watch out
a loose filter can return far more records than you expect, and each one costs operations in the modules that follow.
OneDeck10

Update Record

ActionIn the docs only

Update Record keeps an existing OneDeck record accurate by writing new values into it, instead of adding a duplicate next to it.

When to use it
something changed in another tool and the matching OneDeck record must reflect it.
Watch out
it needs to know which record to change, so place Search Records or Get Record before it and test on a single record first.
Need help

Need help automating OneDeck with Make?

A person reads every message.

FAQ

OneDeck and Make: frequent questions

01Is the OneDeck Make integration free?
Yes, on the Make side. OneDeck is a standard app, so its modules are available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. Each module run on one bundle counts as an operation. You still need an active OneDeck account, whose own pricing is set by OneDeck.
02What do you need to connect OneDeck to Make?
You need an active OneDeck account and two values from it: the Account Name and the API key. Both appear in OneDeck under Settings, then General. In Make, add a OneDeck module, click Create a connection, optionally name the connection, then paste the two values. The connection is saved once and every OneDeck module in your scenarios reuses it, so you do not repeat this step for each module you add later.
03Does the OneDeck Make integration react in real time?
No. OneDeck has no trigger module in Make, neither scheduled nor instant, so it cannot start a scenario by itself. You have two options. Put the trigger of another app first, such as a form or a CRM, and let it call the OneDeck modules. Or begin with a OneDeck search and let Make run the scenario on its schedule, every 15 minutes by default, down to 15 minutes on the Free plan and 1 minute on paid plans.
04What if a OneDeck module is missing in Make?
Use Make an API Call. It reaches any endpoint of the OneDeck API from your scenario and reuses the connection you already created, so there is nothing new to authorize. You write the request yourself, which takes some care, so test it with Run once and read the returned bundle. Keep in mind that the OneDeck page of the Make documentation is flagged as AI-generated and may contain mistakes, so check important details with OneDeck directly.
05Make or n8n for OneDeck?
It depends on the tool your team already uses. In Make, OneDeck comes with 10 modules: 8 actions, 2 searches and Make an API Call among them, and it is available from the Free plan. The same app often has an n8n node too, so check whether one exists before deciding. If both tools cover what you need, pick the one your team already runs and knows, since the scenario logic stays the same either way.
Same platform

Other docs you might need on this stack.

Browse all integrations