Resources · Zapier integration

Pickaxe Zapier integrationAutomate Pickaxe with Zapier.

The Pickaxe Zapier integration gives you 1 instant trigger, 16 actions and 7 searches to run a Pickaxe studio from Zapier: react to signups, payments and finished conversations, manage users and access groups, and attach documents without opening the studio.

See the 24 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Pickaxe Zapier integration actually does

Pickaxe is a no-code platform where you build AI tools, publish them and sell access to them from a studio. The Zapier integration links that studio to Zapier, the service that chains apps together. Something happens in your studio, Zapier hears about it at once, and it runs the steps you picked, in Pickaxe or in any other connected app.

Three results people usually build first. A welcomed member: Studio Event on a signup, then Connect Document so the new user gets the right reference file in front of their Pickaxe. A paid customer moved to the right tier: the same trigger on a payment, then Assign Access Group Links to open the matching access group. A conversation archive: a finished conversation fires the Zap and Find Pickaxe History pulls the chat so the next step can store it wherever your team reads.

Where Zapier stops. There is a single trigger, so everything that starts a Zap goes through the four studio events: signup, payment, membership and a conversation that ended. Nothing fires when you edit a document or an access group yourself. Nothing reaches back into the past either: a Zap only sees events that happen after you switch it on. And most of the useful scenarios chain a search or a second action, which a free plan does not allow.

If you are weighing tools, the same app has a page on the other side: Pickaxe Make integration. For the broader choice, see Make vs Zapier.

Vocabulary

Zapier vocabulary, in plain words

Seven words come back on every line of this page. Here is what each one means before you open the editor.

Zap
The automation you build: one event that starts it, then one or more steps that run every time that event happens again.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier sits and waits for it to happen.
Action
What the Zap does after it starts: the step that creates, updates, sends or deletes something on your behalf.
Task
The unit Zapier bills you for. One task is one action that finished without an error; your plan counts those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself the moment the event occurs.
Filter
A step that lets the Zap carry on only when the incoming data meets a condition you set, and stops it quietly otherwise.
Search step
A step that looks up something that already exists in an app, so the steps after it can reuse what it found.
Cost

What a Pickaxe Zap costs you

Pickaxe is not a premium app on Zapier, so it works on the free plan. The bill depends on how many actions finish, not on how often the studio fires.

  • Free plan100 tasks per month, unlimited Zaps
  • Free plan Zap shapeTwo steps: one trigger, one action
  • TriggerNever costs a task
  • Failed actionNot counted

The trigger never costs a task, and an action that fails is not counted. Each successful action is counted separately: a Zap that finds a user, then updates them, then attaches a document uses three tasks per run. The catch is the free plan: it only builds two-step Zaps, one trigger and one action. Add a search or a filter, the Zap becomes multi-step, meaning anything beyond trigger plus one action, and that needs a paid plan. The interval grid below applies to polling triggers only; Studio Event is instant, so it ignores it.

Connect

Connect your Pickaxe account in 3 steps

  1. 01

    Open your connections

    In Zapier, go to the Apps page of your account and click + Add connection. A connection is your Pickaxe account linked once, then reused by every step that touches Pickaxe.

  2. 02

    Pick Pickaxe

    Type Pickaxe in the search box of the dialog, select it, then confirm with Add connection. You need a Pickaxe account first, plus access to anything you do not own and want the Zap to touch.

  3. 03

    Sign in and allow access

    A new tab opens on Pickaxe. Sign in with the account that owns the studio, then grant Zapier access. The connection now shows up in your list and in every Pickaxe step of the editor.

First Zap

Your first Zap: a starter document for every new member

GoalWhen someone signs up to your studio, find them in Pickaxe and attach a starter document to them.

  1. 01

    Pick the trigger

    Create a Zap and choose Pickaxe as the app that starts it, with Studio Event as the event. Select your connection, then the studio and the signup event.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items of the account, so map the next steps on a real signup rather than a made-up one.

  3. 03

    Find the user

    Add Find User by Email under the trigger. Pick the same studio and map the new user from the signup. This search is what turns the Zap multi-step, so it needs a paid plan.

  4. 04

    Attach the document

    Add Connect Document. Choose the studio, the starter document and the Pickaxe it belongs to, and map the user found by the search step.

  5. 05

    Test, then publish

    Test each step once and read what came back. When the document lands on the right user, click Publish to switch the Zap on.

Triggers

The Pickaxe trigger

1 event starts a Zap when something happens in Pickaxe, and one of them is instant: the app calls Zapier straight away, whatever your plan.

1

Studio Event

Instant trigger

In Zapier“Triggers when a studio event happens.”

This is the only door into a Pickaxe Zap: it starts every time one of four things happens in a studio you pick. A user signs up, pays inside the studio, someone becomes a member of your studio workspace, or a conversation ends. You choose the studio and one of those events when you set the step up, so one Zap listens to one event.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
any time the useful work starts with a person joining, paying or finishing a chat with one of your tools.
Watch out
both Studio and Studio Event are required, so covering signups and payments takes two Zaps, one per event.
Actions

The 16 Pickaxe actions

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

2

Call Pickaxe

Action

In Zapier“Call pickaxe with provided data.”

Sends data to one of your Pickaxes and gets its answer back, so the AI tool works inside the Zap like any other step.

When to use it
a new ticket lands in your helpdesk and a Pickaxe should draft the first reply.
Watch out
only the Pickaxe field is required; test with a real input, since the answer shapes every step after it.
3

Connect Document

Action

In Zapier“Connect a document to a Pickaxe or User.”

Hooks one or more documents onto a Pickaxe or onto a user, so that tool or that person works with that knowledge.

When to use it
a new member signs up and should find their own onboarding file waiting in the assistant.
Watch out
Studio, Documents and Pickaxe are all required, even when the target is a user.
4

Create Access Group

Action

In Zapier“Create a new access group.”

Opens a new access group in a studio, the container that decides who can use which of your tools.

When to use it
you launch a new offer in your sales tool and want its matching group built at the same time.
Watch out
Studio and Access Group Type are required; display image, button style and upgrade path are optional and can wait.
5

Create Document

Action

In Zapier“Create a new document with the provided details.”

Creates a new document in a studio, ready to be attached later to a Pickaxe or a user as knowledge.

When to use it
a brief, a policy or a product sheet is finished elsewhere and your AI tool should be able to read it.
Watch out
Studio and Document name are required, so map a clear name or the library fills with untitled entries.
6

Create Pickaxe Deployment

Action

In Zapier“Create a new Pickaxe deployment.”

Publishes one of your Pickaxes as a new deployment, without going through the studio by hand.

When to use it
every new client project gets its own deployed copy of the same assistant.
Watch out
three fields are required (Studio, Pickaxe and Deployment Type), so the Pickaxe must already exist before the Zap runs.
7

Create User

Action

In Zapier“Create a new document with the provided details.”

Adds a person to a studio from another app, so a buyer or a lead gets an account without anyone typing it in.

When to use it
a sale closes in your checkout tool and the buyer should land in Pickaxe straight away.
Watch out
Studio and User Email are required; there is an optional box to mark the email as already verified.
8

Delete Access Group

Action

In Zapier“Delete an access group, or reassign links and users before deleting it.”

Deletes an access group, or first moves its links and users elsewhere and then deletes it.

When to use it
an offer is closed for good and its members should be moved onto the current tier rather than left out.
Watch out
decide where the users go before the run; the reassignment option is what keeps them from losing access.
9

Delete Document

Action

In Zapier“Delete a specific document by its ID.”

Erases a specific document from a studio, picked by its identifier.

When to use it
a file is retired in your shared drive and the outdated copy should not stay behind in Pickaxe.
Watch out
unlike Disconnect Document, this removes it for every Pickaxe and user that relied on it.
10

Delete User

Action

In Zapier“Delete a specific user by their email.”

Removes a user from a studio, matched by email address.

When to use it
a deletion request arrives through your support form and the account should go everywhere at once.
Watch out
Studio and User Email are required, and there is no undo step in the Zap; put a filter in front if the source can send mistakes.
11

Disconnect Document

Action

In Zapier“Detach a document from a Pickaxe or User.”

Detaches a document from a Pickaxe or a user without deleting it, so it stays in the studio for later use.

When to use it
a contract ends and the client's private file should stop feeding the assistant.
Watch out
Studio, Document and Pickaxe are required, so keep the document identity at hand from an earlier step.
12

Invite Users

Action

In Zapier“Invite a new user by sending an invitation email.”

Sends an invitation email to new users of a studio, so they create their own access instead of receiving a ready-made account.

When to use it
a form or a CRM stage marks someone as approved, and the invitation should leave without a manual step.
Watch out
only Studio is required; check in a test that the email really goes out before publishing.
13

Update User

Action

In Zapier“Update a specific user by their email.”

Edits an existing user of a studio, found by their email address.

When to use it
your onboarding tool confirms an address and Pickaxe should show the user as verified too.
Watch out
Studio and User Email are required; the email is how the user is matched, so it must be the one Pickaxe already holds.
14

Preview Delete Access Group

Action

In Zapier“Preview the impact of deleting an access group.”

Shows what deleting an access group would affect, without deleting anything.

When to use it
before a cleanup Zap removes groups, send that preview to a teammate for a quick check.
Watch out
it still counts as an action, so each successful preview uses one task.
16

Update Access Group

Action

In Zapier“Update an existing access group.”

Changes the settings of an access group that already exists, such as its image, its archived state or where it sends people to upgrade.

When to use it
an offer ends in your shop and the group should be archived the same day.
Watch out
Studio and Access Group are both required; pair it with Find Access Group when the group is not fixed.
Searches

The 7 Pickaxe searches

7 search steps look for data that already exists in Pickaxe, so a later step can use it.

Searches sit at the bottom of the action event list, under the SEARCH heading. Some action fields also offer + Add search step, which inserts the right search just before the current step. Three settings decide what happens next.

1

Find Access Group

Search

In Zapier“Retrieve a specific access group by its ID.”

Fetches one access group of a studio, so a later step can update it, link it or delete it.

When to use it
the group to change depends on what was bought, not on a fixed choice.
Watch out
Studio and Access Group are required, and the group is looked up by its identifier.
2

Find Document by ID

Search

In Zapier“Retrieve a specific document by its ID.”

Retrieves one document of a studio from its identifier, so its details can travel to the next step.

When to use it
another app stored the document identity and the Zap needs the document itself before detaching or deleting it.
Watch out
it matches on the identifier only, never on the document name.
3

Find Pickaxe History

Search

In Zapier“Fetch specific Pickaxe chat history.”

Pulls the chat history of a given Pickaxe, so the conversation can be stored, summarised or shared by the steps that follow.

When to use it
a conversation just ended and the transcript belongs in your CRM or your notes.
Watch out
only the Pickaxe field is required; test it on a Pickaxe that already has conversations.
4

Find User by Email

Search

In Zapier“Retrieve a specific user by their email.”

Looks up a single user of a studio from an email address, the usual first move before updating or deleting someone.

When to use it
your form only gives you an address and a later step needs the matching Pickaxe user.
Watch out
a typo in the address means no result; decide with the first setting above what the Zap does then.
5

Find Access Groups

Search

In Zapier“List all access groups for a studio workspace.”

Lists every access group of a studio workspace in one go, instead of looking up a single one.

When to use it
a reporting Zap needs the full set of tiers to write them somewhere else.
Watch out
several results come back; the third setting decides whether you keep one or all of them.
6

Find Documents

Search

In Zapier“List all documents with optional pagination.”

Returns the documents of a studio, with optional paging when the library is large.

When to use it
an audit Zap should compare what sits in Pickaxe with what your drive still holds.
Watch out
only Studio is required; with several documents back, the third setting decides whether you keep the first or all of them.
7

Find Users

Search

In Zapier“List all users with optional pagination.”

Brings back the users of a studio, page by page if you set paging, for a step that needs the list rather than one person.

When to use it
an export of members to a spreadsheet you share with sales.
Watch out
the default keeps only the first match, so switch the third setting if the goal is the whole list.

The three settings every search exposes

  1. Successful if no search results are found?
    Left as it is, a search that finds nothing stops the Zap and the steps that depended on it are skipped. Switched on, the Zap carries on without the value.
  2. Create X if it doesn't exist yet?
    Turns a search into find-or-create. Pickaxe offers no such variant on Zapier, so you will not see this box on its searches.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one (the default), stop the Zap, or pass all of them on together.
When it breaks

When a Pickaxe Zap breaks

Zapier publishes no help article and no limit specific to Pickaxe. What goes wrong comes from how Zapier itself behaves, and four cases cover most of it.

Each one is a habit of Zapier, not a Pickaxe bug, so knowing them saves a lot of guessing. When a run fails for another reason, the steps in Zapier troubleshooting are a good place to start.

  • Old signups never arrive

    A Zap only reacts to events that happen after you switch it on. Members who joined before stay out; moving them over is a separate job.

  • The Zap keeps setting itself off

    A Zap that writes into the place its own trigger watches starts again on its own output, and the task count drains fast.

  • A bulk import is held back

    When a trigger suddenly returns a very large batch, after an import or a migration, Zapier's flood protection can hold the runs back.

  • The test shows old data

    A trigger test brings back the three most recent items of the account. If they are not the event you chose, trigger a real one and test again.
Need help

Need help automating Pickaxe with Zapier?

A person reads every message.

FAQ

Pickaxe Zapier integration: questions people ask

01Is the Pickaxe Zapier integration free?
Yes, on the free plan, within its limits. Pickaxe is not a premium app, so the free plan can use it, with 100 tasks per month and unlimited Zaps. The catch is the shape of the Zap: free plans only build two-step Zaps, one trigger and one action. Once you add a search, a filter or a second action, for example finding a user before updating them, the Zap becomes multi-step and needs a paid plan. Most Pickaxe scenarios that go beyond a single reaction fall into that second case.
02How many tasks does a Pickaxe Zap use?
One per successful action, per run. The Studio Event trigger costs nothing, however many events your studio sends. An action that fails is not counted either. A Zap that only attaches a document to new members spends one task per signup; one that finds the user, updates them and attaches a document spends three. Previews count too: Preview Delete Access Group is an action, so a successful preview is a task. Plan your monthly volume from the number of events times the number of actions.
03Is the Pickaxe trigger real time?
Yes. Studio Event is an instant trigger: Pickaxe tells Zapier itself when a signup, a payment, a membership or a finished conversation happens, and the Zap starts right away. The plan interval grid, from 15 minutes on Free down to 1 minute on Team and Enterprise, applies only to polling triggers, which Zapier checks on a timer. It does not apply here, so a free plan reacts as fast as a paid one on this trigger. The editor shows a lightning bolt on Zaps built this way.
04What does it take to connect Pickaxe to Zapier?
A Pickaxe account, a Zapier account, and access to the studio the Zap will work on. You add the connection from the Apps page with + Add connection, pick Pickaxe, sign in in the tab that opens and grant access. Most steps then require a Studio, so the account must own or reach at least one studio workspace. If you plan to touch items someone else owns, the account also needs read or write rights on them, or the steps will not find them.
05Why does a Studio Event Zap miss some events?
Usually because one Zap listens to one event. Studio Event asks for a studio and for one event among signup, payment, membership and conversation ended, and both are required. A Zap set on signups ignores payments in the same studio. To react to two events, build two Zaps. Also check the studio: a Zap set on one studio does not hear what happens in another. And remember that nothing from before the Zap was published is ever picked up.
06What if the Pickaxe operation you need is missing?
Then the integration does not expose it, and the editor offers no way around that. Check first whether two existing steps cover it: a search followed by an action often does what one missing action would, such as Find User by Email followed by Update User. If the trigger is the missing piece, there is only Studio Event, so a change that is not one of its four events cannot start a Zap. In that case another tool, or a request to Pickaxe, is the realistic route.
07Zapier, Make or n8n for Pickaxe?
It depends on what matters most to you, not on a ranking. Judge on three criteria. Does the tool offer the events you need to start from? On Zapier, that is only the four studio events. Does it cover the actions you need? Here there are 16 actions and 7 searches. And does the plan allow the shape of your workflow? On Zapier, any Zap with a search or a second action needs a paid plan. Compare each tool on those same three questions before picking one.
Same platform

Other docs you might need on this stack.

Browse all integrations