Resources · Make integration

Pickaxe Make integrationAutomate Pickaxe with Make.

Want new Pickaxe users, documents and access groups handled without copy and paste? The Pickaxe Make integration offers 21 modules: 1 trigger, 17 actions and 3 searches. This guide shows how to link your account, build a first scenario and pick the right module.

Try the Pickaxe integration on MakeSee the 21 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Pickaxe Make integration do for you?

The Pickaxe Make integration links your Pickaxe account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, reads or changes something in an app. Pickaxe gets 21 of those bricks, covering users, documents, access groups and calls to your Pickaxe.

Every new sign-up lands in your other tools. Watch User Signed Up spots new users, Get User fetches the full record, and the next module copies it into a CRM or a sheet such as the one in the Airtable Make integration.

Buyers get access without a manual invite. When a sale or a form lands in another app, Invite Users brings the person into Pickaxe, and Update Access Group can widen what a paying customer sees.

Your knowledge base stays tidy. Create Document, Connect Document and Disconnect Document let a scenario add or retire the material a Pickaxe relies on, while List Documents gives you an inventory to check.

Be aware of the limits. Make's own documentation says it cannot describe Pickaxe in full for lack of public information, and none of the 21 modules has an official description. The notes below read each module from its name, so confirm fields with Run once before going live. There is also no Make an API Call module for Pickaxe.

Weighing another tool? The n8n vs Make comparison lays out the criteria, and the Make training covers the editor from scratch.

Connect

How do you connect Pickaxe to Make?

  1. 01

    Add a Pickaxe module

    Open a scenario, click the +, type Pickaxe and pick any of its modules. The first time, Make asks for a connection, meaning your Pickaxe account linked to Make once and reused by every Pickaxe module. Click Create a connection.

  2. 02

    Name it and authorize

    Give the connection a name if you like, handy when a client account and your own sit side by side. Then follow what the window asks: either authorize Make on the Pickaxe page, or paste the key Pickaxe gives you. Make's doc does not say which one Pickaxe uses.

  3. 03

    Save and check

    Click Save. The connection now appears in the module's dropdown, and Make can list the objects your account holds. If the list stays empty, the account behind the connection is probably not the one you meant to use.

First scenario

Your first Pickaxe scenario in Make

GoalWhen a customer pays or fills a form in another app, Make invites that person to your Pickaxe with Invite Users.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. The first module is the trigger: the app where the buyer or the form entry shows up, such as your shop, your payment tool or a form builder.

  2. 02

    Set the trigger

    Connect that app and pick the module that fires on a new order or entry. Each one comes out as a bundle, meaning one item passed to the next module: here, one buyer with a name and an email.

  3. 03

    Add Invite Users

    Click the + on the right of the trigger, search Pickaxe and choose Invite Users. Pick your Pickaxe connection, then map the buyer's email from the previous module into the invite fields Make shows.

  4. 04

    Test with Run once

    Click Run once and trigger a test order. Open the bubbles above each module to read the bundles they received, and check in Pickaxe that the invitation went out to the right address.

  5. 05

    Schedule and switch on

    Set the schedule on the first module. A new scenario checks every 15 minutes by default, which is also the shortest gap on the Free plan. Then switch the scenario on.

Triggers

What can start a Pickaxe scenario?

1 module starts a scenario when something happens in Pickaxe. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Pickaxe as soon as it happens.

Pickaxe1Watch User Signed Up

Watch User Signed Up

triggerIn the docs only

This is the only Pickaxe trigger, and going by its name it hands your scenario each person who signs up to your Pickaxe. That gives you one place to react to new users: copy them to a CRM, ping your team, or start a welcome flow in another app.

How it fires
scheduled. Make checks Pickaxe on the scenario's schedule, every 15 minutes by default and never faster than that on the Free plan.
When to use it
you run a public Pickaxe and want every newcomer logged somewhere your sales or support team already looks.
Watch out
Make has no official description of this module, so run it once to see what a sign-up bundle really contains before mapping it.
Modules

What can Make do in Pickaxe?

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

Pickaxe1

Call Pickaxe

ActionIn the docs only

Puts your Pickaxe to work from inside a scenario: as the name suggests, you send it input and get its answer back as data the next module can use. That turns your AI tool into a step of any automation, not only a chat window.

When to use it
a support ticket arrives in another app and you want a draft reply from your Pickaxe attached to it.
Watch out
every call is an operation Make counts on your plan, so place it after any filter.
Pickaxe2

Connect Document

ActionIn the docs only

Attaches a document that already exists in your account to a Pickaxe, so it can draw on that material. It is the step that makes a freshly uploaded file actually count.

When to use it
right after Create Document, or when one guide should feed several Pickaxes at once.
Watch out
the doc gives no field list, so check with Run once which identifiers Make expects for the document and the Pickaxe.
Pickaxe3

Create Access Group

ActionIn the docs only

Sets up a new access group, a way to bundle users who should see the same things. You get a clean container to drop people into later, without touching the Pickaxe settings by hand.

When to use it
a new client, cohort or offer goes live and needs its own set of members.
Watch out
running the scenario twice on the same event would create two groups, so search with List Access Groups first.
Pickaxe4

Create Document

ActionIn the docs only

Adds fresh material to your Pickaxe account from a scenario, instead of uploading it yourself. Your knowledge base can then grow each time a source file changes elsewhere.

When to use it
a new procedure is approved in your shared drive and your assistant should know about it.
Watch out
creating a document is one step and attaching it is another; add Connect Document if a Pickaxe must use it.
Pickaxe5

Create User

ActionIn the docs only

Registers a person directly in Pickaxe from a scenario. The account exists straight away, which suits people you already know rather than prospects who should accept an invitation.

When to use it
a colleague joins the team and gets added to your internal tools from your HR sheet.
Watch out
for outside customers, Invite Users is usually the gentler choice, since they decide to join.
Pickaxe6

Delete Access Group

ActionIn the docs only

Removes an access group from Pickaxe when it no longer serves any purpose. Your group list stays short, and a closed offer does not linger with its old members attached.

When to use it
a program ends and its group should disappear along with the related record in your CRM.
Watch out
a deletion cannot be undone from Make, so test on a throwaway group before activating the scenario.
Pickaxe7

Delete Document

ActionIn the docs only

Erases a document from your account, not just from one Pickaxe. Outdated material stops existing, which removes any chance of an assistant quoting it later.

When to use it
a policy is withdrawn at the source and should vanish from Pickaxe too.
Watch out
if you only want one Pickaxe to stop using the file, Disconnect Document is the safer move, since deletion is final.
Pickaxe8

Delete User

ActionIn the docs only

Takes a person out of your Pickaxe account entirely. Access ends in the same scenario that handles the rest of an offboarding, so nobody has to remember that extra step.

When to use it
a subscription is cancelled in your billing tool and the matching user should go.
Watch out
nothing brings the user back from Make; if you might restore access later, moving them to another access group may fit better.
Pickaxe9

Disconnect Document

ActionIn the docs only

Detaches a document from a Pickaxe while keeping it in your account. The assistant stops drawing on it, yet the file remains ready for another Pickaxe or a later comeback.

When to use it
seasonal content goes out of date but will return next season.
Watch out
you need both the document and the Pickaxe identified, so a List Documents step before it often helps.
Pickaxe10

Get Access Group

ActionIn the docs only

Reads one access group so later modules can use its details. It answers the question of what a given group looks like right now, without opening Pickaxe.

When to use it
before Update Access Group, to check the current state and avoid overwriting something useful.
Watch out
it most likely asks for the group's identifier; if you only know its name, start with List Access Groups.
Pickaxe11

Get Document

ActionIn the docs only

Fetches one document from your account and passes its details down the scenario. Handy when a decision depends on what a file holds or how it is set up.

When to use it
you want to archive a copy of a knowledge base file elsewhere before replacing it.
Watch out
Make lists no fields for this module, so read the output of a Run once test before mapping anything.
Pickaxe12

Get Pickaxe History

ActionIn the docs only

Pulls the history of a Pickaxe, which, going by the name, means the past conversations people had with it. That gives you material to review what users actually ask.

When to use it
you want past exchanges copied into a sheet so your team can spot missing answers and improve the documents.
Watch out
history may hold personal data, so send it only to a place with the right access rules.
Pickaxe13

Get User

ActionIn the docs only

Returns the record of one Pickaxe user, ready to map into another app. It completes the thin data a trigger or a form often provides.

When to use it
right after Watch User Signed Up, when your CRM needs the full profile rather than a bare identifier.
Watch out
the doc does not describe which details come back, so confirm them in the bundle before building on them.
Pickaxe14

Get User Memories

ActionIn the docs only

Reads what Pickaxe keeps in memory about one user, in other words the context it has built up from past exchanges, if the name holds. That lets you see the assistant's view of a person.

When to use it
a support agent opens a ticket and wants that context added to it.
Watch out
treat this data as sensitive and never push it to a public channel.
Pickaxe15

Invite Users

ActionIn the docs only

Sends people an invitation to join your Pickaxe, so they sign in on their own terms. The plural name points to several people at once, which suits a batch of buyers or a whole class.

When to use it
a payment clears in your shop and the buyer should get access without you lifting a finger.
Watch out
check with Run once how Make expects the addresses before inviting a real list.
Pickaxe16

List Access Groups

SearchIn the docs only

Returns your access groups as separate bundles, zero, one or many. You can then filter or loop over them without clicking through Pickaxe.

When to use it
to find a group by name before adding someone to it, or to check that a group does not exist before creating it.
Watch out
as a search, it may return nothing, so add a filter after it or the next module will not run.
Pickaxe17

List Documents

SearchIn the docs only

Gives you an inventory of the documents in your account, each one as its own bundle. Every module after it runs once per document, which is exactly what a cleanup needs.

When to use it
you want a sheet showing every file your Pickaxes can draw on, for an audit.
Watch out
each returned document costs operations in the following modules, so filter early.
Pickaxe18

List Users

SearchIn the docs only

Searches your Pickaxe users and returns them one bundle at a time. It is the way to act on a group of people rather than a single known account.

When to use it
you are comparing Pickaxe users with your paying customers to find who still has access after cancelling.
Watch out
on a large base the result can be long, and every user then counts as an operation downstream.
Pickaxe19

Update Access Group

ActionIn the docs only

Changes an existing access group rather than rebuilding it. Existing members keep their place while the group itself evolves with your offer.

When to use it
a plan is renamed or extended in your billing tool and the matching group should follow.
Watch out
an update can overwrite what is already there; read the group with Get Access Group first if in doubt.
Pickaxe20

Update User

ActionIn the docs only

Edits the record of a Pickaxe user from a scenario. Profile changes made in another tool then reach Pickaxe without a second round of typing.

When to use it
a customer upgrades in your billing tool and their Pickaxe account should reflect the new status.
Watch out
it most likely asks for the user's identifier; when you only have an email, find the person with List Users first.
Need help

Need help automating Pickaxe with Make?

A person reads every message.

FAQ

Pickaxe and Make: common questions

01Is the Pickaxe Make integration free?
Yes, Pickaxe is a standard app in Make, so its modules work on the Free plan. That plan has real limits though: 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 such as Core, Pro and Teams lift the gap to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, one per module per bundle. Your Pickaxe subscription is a separate matter.
02What do you need to connect Pickaxe to Make?
A Pickaxe account and a Make account are enough to start, as Make's documentation lists no other prerequisite. Add any Pickaxe module, click Create a connection, name it if you want, then either authorize Make on the Pickaxe page or paste the key Pickaxe gives you, and save. The documentation does not say which of the two methods Pickaxe uses, and it describes its coverage of Pickaxe as limited, so follow the connection window as it appears.
03Does the Pickaxe trigger in Make fire in real time?
No. Watch User Signed Up is a scheduled trigger, marked with a clock badge in the editor. Make checks Pickaxe at the interval set on the scenario, every 15 minutes by default, which is also the minimum on the Free plan. Paid plans can bring that down to 1 minute. A new sign-up therefore reaches your scenario at the next check, not the moment it happens. Pickaxe has no instant trigger in Make.
04What if a Pickaxe module is missing in Make?
It depends on the gap. Pickaxe has no Make an API Call module, so you cannot reach the rest of its API from Make with a ready-made brick. The 21 existing modules cover users, access groups, documents, history and calls to a Pickaxe. If what you need sits outside that list, look at whether another app in your stack can hold that step, or ask the team for help designing a workaround.
05Make or n8n for Pickaxe automations?
It depends on the criteria that matter to you. On Make, Pickaxe comes with 21 modules, one scheduled trigger and no generic API call module, and it runs on the Free plan within its limits. The same app often has an n8n node too, so compare the list of operations each tool offers for your use case, and how each one bills its runs. Neither is better in general; the right pick is the one whose modules match your scenario.
Same platform

Other docs you might need on this stack.

Browse all integrations