Resources · Make integration

Pickaform Make integrationAutomate Pickaform with Make.

Can Make create, find and update your Pickaform records for you? Yes: the Pickaform Make integration gives you 13 modules, 12 actions and 1 search, with no trigger. This guide is for anyone who knows Pickaform but is new to Make, and it walks you from the connection to a first working scenario.

Try the Pickaform integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Pickaform Make integration do for you?

The Pickaform Make integration links your Pickaform account to Make, a tool where you build a scenario: an automation made of modules, each one a single brick that acts on one app. Pickaform brings 13 of those bricks, mostly to create, read, update and remove records, so data coming from your other tools lands in Pickaform without copy and paste.

Records that stay in sync. A status changes in your CRM or a spreadsheet row is edited: Find a record locates the matching record in Pickaform and Update a record writes the new value. Nobody has to open two tabs to keep them aligned.

New entries created for you. A sign-up arrives through a form tool, and Create a record turns it into a Pickaform record with the values you map. Each item passing between modules is called a bundle, and each bundle becomes one record.

A clear picture of your account. Get workspaces, Get applications and Get users let you see what Make reads from Pickaform, which helps before you build anything bigger.

Two limits are worth knowing upfront. Pickaform has no trigger in Make, so a scenario starts from another app or from a schedule. And Make itself flags the Pickaform documentation as limited, for lack of public information about the app; the Make an API Call module covers what the list leaves out. If you are new to the editor, the Make training starts from zero, Make troubleshooting helps when a run fails, and n8n vs Make puts the two tools side by side.

Connect

How do you connect Pickaform to Make?

  1. 01

    Open the connection window

    Add any Pickaform module to your scenario and click Create a connection. A connection is your Pickaform account linked to Make once; every Pickaform module of every scenario reuses it afterwards.

  2. 02

    Name the connection and authorize

    Give the connection a name if you like, handy when several accounts are in play. Then authorize Make on the Pickaform page that opens, or paste the key Pickaform gives you, depending on what the window asks for.

  3. 03

    Save and check

    Click Save. Make now reads your account: open a field of the module and it lists what it can see. If the list comes up empty, the connection points to the wrong account or was not authorized.

First scenario

Your first scenario with Pickaform

GoalWhen a new entry lands in another app you use, Make finds the matching Pickaform record and updates it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pickaform has no trigger, so the first module comes from the app where your entries start, such as a form tool or a spreadsheet.

  2. 02

    Add Find a record

    Click the + on the right of that first module, search for Pickaform and pick Find a record. Create the connection, then map the value that identifies the record, taken from the first module.

  3. 03

    Add Update a record

    Click the next + and choose Update a record. Map the record returned by the search, then the new values coming from the first module. Make lists what it can read once the connection exists.

  4. 04

    Test with Run once

    Click Run once and open the bundles each module received. Check that Find a record returned the record you expected, not zero or several, before trusting the update.

  5. 05

    Schedule and switch on

    Click the clock on the first module: a new scenario runs every 15 minutes by default, and the Free plan cannot go below that. Pick the interval, then switch the scenario on.

Modules

What the Pickaform modules do

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

Pickaform1

Create a record

ActionIn the docs only

Every bundle that reaches this module becomes a new record in Pickaform, filled with the values you map from earlier modules.

When to use it
a sign-up collected in another app should exist in Pickaform too, without anyone retyping it.
Watch out
if the same person can come back, run Find a record first, or you will stack duplicates.
Pickaform2

Delete a record

ActionIn the docs only

Removing a record for good is the job of this one: point it at a single record and Make wipes it from Pickaform.

When to use it
a cleanup scenario, where a record located by Find a record no longer has a reason to exist.
Watch out
treat a delete as final, since the doc says nothing about undoing it, and try it on a throwaway record with Run once before switching the scenario on.
Pickaform3

Find a record

SearchIn the docs only

This is the search of the app: it looks through Pickaform and hands the next module zero, one or several bundles, one per matching record.

When to use it
before an update or a delete, to get hold of the right record from a value sent by another app, such as a reference.
Watch out
no match or several? Plan for both, because each bundle runs every module after it.
Pickaform4

Get applications

ActionIn the docs only

Going by its name, this module fetches the applications of your Pickaform account; the doc adds no description to confirm the details.

When to use it
early on, to see what Make can read from your account before building on top of it.
Watch out
click Run once and open the output bundles, which show exactly what comes back and beat any guess.
Pickaform5

Get collections

ActionIn the docs only

Collections are what this module brings back, per its name, which makes it a good way to learn how your Pickaform data is organized before you touch a record.

When to use it
you are about to map values in Create a record and want to know which collection holds what.
Watch out
Make documents nothing about its output, so read the bundles after a test instead of assuming their shape.
Pickaform6

Get groups

ActionIn the docs only

Need the groups of your Pickaform account in front of you? The module name points there, and the bundles from a test show what each group carries.

When to use it
a later step in the scenario has to reference a group rather than a record.
Watch out
without an official description, treat its output as something to check, not as a promise.
Pickaform7

Get records

ActionIn the docs only

Where Find a record hunts for specific matches, Get records reads records in bulk, going by its name, and sends them down the scenario as bundles.

When to use it
an export to another app, or a report built from what Pickaform already holds.
Watch out
each bundle that follows costs operations on your plan, so count what comes back with Run once first.
Pickaform8

Get users

ActionIn the docs only

A view of the people on your Pickaform account is what the name promises here, useful when a later module needs a user rather than a record.

When to use it
checking who is on the account after a team change, before the scenario acts on their behalf.
Watch out
the doc stays silent on what each user bundle contains, so confirm it with a test run.
Pickaform9

Get workspaces

ActionIn the docs only

Start here if your account has more than one space: by its name, Get workspaces returns the workspaces Pickaform shows for your connection.

When to use it
the very first test of a new connection, since a clean result tells you Make reaches the right account.
Watch out
a workspace missing from the bundles may point to the account behind the connection, so check which one you authorized.
Pickaform10

Login

ActionIn the docs only

Login is the least documented module of the list: the doc gives it no description, and its name alone does not tell you what it returns inside a scenario.

When to use it
only once you have tested it with Run once and read its output, or if Pickaform support tells you it is needed.
Watch out
the connection already links your account to every module, so there is no need to add Login by reflex.
Pickaform11

Make an API Call

ActionIn the docs only

When none of the other 12 modules covers what you need, this one lets the scenario call any endpoint of the Pickaform API, with the same connection.

When to use it
an operation the listed modules leave out, which the thin documentation makes more likely here.
Watch out
you need the Pickaform API reference to know which endpoint to call, since this page cannot give it to you.
Pickaform12

Send a record to trash

ActionIn the docs only

Softer than Delete a record, at least by its name: the record goes to the Pickaform trash rather than disappearing outright.

When to use it
an archiving step where someone may still want to rescue the record later.
Watch out
the doc says nothing about how long the trash keeps a record, so check in Pickaform before counting on a restore.
Pickaform13

Update a record

ActionIn the docs only

Changes to an existing record land here: give the module the record and the new values, and Pickaform keeps the fresh version.

When to use it
a status that moves in another app and has to follow in Pickaform.
Watch out
the module needs to know which record to change, so place Find a record before it and map its result.
Need help

Need help automating Pickaform with Make?

A person reads every message.

FAQ

Pickaform and Make: common questions

01Is the Pickaform Make integration free?
Yes. Pickaform is a standard app in Make, available from the Free plan with no extra cost for the app itself inside Make. The Free plan has limits you will feel quickly: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans drop the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module run on one bundle.
02What do you need to connect Pickaform to Make?
A Pickaform account and a Make account. The Make documentation lists no other prerequisite for this app. Add a Pickaform module, click Create a connection, give it a name if you want, then authorize Make on the Pickaform page or paste the key Pickaform provides, and click Save. The connection is created once and every Pickaform module reuses it. If the fields of a module stay empty afterwards, check that you authorized the right account.
03Can Pickaform start a Make scenario in real time?
No, not from Pickaform itself: the app has no trigger module in Make, neither scheduled nor instant. A scenario that uses Pickaform starts somewhere else. Either the first module belongs to another app, and if that app offers an instant trigger it calls Make through a webhook as soon as something happens. Or the scenario runs on a schedule set on its first module, every 15 minutes by default, down to 1 minute on a paid plan.
04What if the Pickaform module you need is missing?
Use Make an API Call. With it, the scenario can reach any endpoint of the Pickaform API through the connection you already have, which covers what the 12 other modules do not. Keep in mind that Make describes its Pickaform documentation as limited for lack of public information, so the Pickaform API reference will be your guide for paths and parameters. When a run fails, the bundles shown after Run once are the first place to look.
05Is Pickaform better on Make or on n8n?
It depends on where the rest of your automations already live. On Make, Pickaform comes with 13 modules, including a search and a generic API call, but no trigger. An app available in Make often has a node in n8n as well, so check whether Pickaform does before choosing. Then compare what each tool offers for this exact app rather than general impressions, and keep your scenarios in the tool your team already knows.
Same platform

Other docs you might need on this stack.

Browse all integrations