Resources · Make integration

Process Street Make integrationAutomate Process Street with Make.

What if your checklists could start and update themselves? The Process Street Make integration gives you 16 modules: 2 instant triggers, 8 actions and 6 searches. This page shows ops teams how to link the account, build a first scenario and pick the right module.

Try the Process Street integration on MakeSee the 16 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Process Street Make integration automate?

The Process Street Make integration links your Process Street account to Make, a visual tool where you build a scenario: an automation made of modules, each one a single step such as a trigger, an action or a search. Once linked, your workflow runs and tasks can react to other apps, and other apps can react to them, without code.

Hand out work the moment a checklist starts. When someone launches a new onboarding run, Watch Workflow Runs fires and Assign to a Task puts the right teammate on the first step. Nobody has to open the run and pick names by hand.

Launch a run from another tool. A signed contract in your CRM or a new row in a sheet can feed Create a Workflow Run, so the checklist exists before anyone remembers to start it. Update Form Fields in a Workflow Run then drops the known details into the run.

Send finished answers elsewhere. Watch Checked Tasks tells Make when a step is ticked off. Get Workflow Run Form Field Values reads what people typed, and the next module passes it to your billing or reporting app.

Make only covers what these 16 modules and the Make an API Call module reach. The official documentation for this app is marked as AI-generated from the vendor docs, so double-check anything critical with Process Street. If you are still weighing tools, our Make review and the n8n vs Make comparison help, and Make training gets you building faster.

Connect

How do you connect Process Street to Make?

  1. 01

    Generate an API key in Process Street

    Make signs in with an API key, so you need an active Process Street account first. From the main menu, open the organization integrations page, click the button that generates a new key, give it a name if asked, and copy the key shown on screen.

  2. 02

    Add a Process Street module

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

  3. 03

    Paste the key and save

    You can type a label in Connection name, which helps when you manage several accounts. Paste the API key you copied, confirm, and Make now lists the workflows and runs it is allowed to read.

First scenario

Your first scenario with Process Street

GoalWhen a new workflow run starts in Process Street, Make assigns a teammate to one of its tasks.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the big + to add your first module. Search for Process Street and choose Watch Workflow Runs.

  2. 02

    Set up the trigger

    Click Create a webhook, then Create a connection and paste your API key. The trigger is instant: Process Street will call Make each time a new run is created.

  3. 03

    Add the assignment

    Click the + on the right of the trigger and pick Assign to a Task. Map the run coming from the trigger, then choose the task and the member who should own it.

  4. 04

    Test with Run once

    Click Run once, then start a test run in Process Street. Each module shows the bundle it received, one item of data, so you can check the right person landed on the task.

  5. 05

    Switch it on

    Save the scenario and turn it on. From then on, every new run gets its owner without anyone opening the checklist, and each module execution counts as one operation on your Make plan.

Triggers

What starts a Process Street scenario

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

Process Street1Watch Checked Tasks

Watch Checked Tasks

Instant trigger

In Make“Triggers when a task is checked.”

This trigger starts your scenario the moment someone ticks a task in a Process Street run, so the next step outside Process Street follows right behind the person who finished the work.

How it fires
it is an instant trigger, meaning Process Street calls Make through a webhook as soon as the task is checked, instead of Make polling on a schedule.
When to use it
when ticking an approval or a review step should notify a channel, update a record or kick off another tool.
Watch out
click Create a webhook before Create a connection, or the trigger never hears anything.
Process Street2Watch Workflow Runs

Watch Workflow Runs

Instant trigger

In Make“Triggers when a new workflow run is created.”

Every freshly launched checklist becomes a starting signal: this trigger hands Make each new workflow run as it is created, ready for the next modules to read and act on.

How it fires
instant. Process Street warns Make through a webhook right when the run appears, with no schedule to set.
When to use it
when a new client onboarding or hiring run should get owners, a CRM record or a message before anyone opens it.
Watch out
it watches for new runs only, so a run that already exists will not start the scenario again.
Modules

Everything the Process Street modules can do

Process Street gives you 14 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Process Street1

Assign to a Task

Action

In Make“Assigns a member to a certain task of a workflow run.”

Puts a member on a specific task inside a workflow run, so the person responsible sees the step as theirs without a manager handing it out.

When to use it
right after a run is created, to route the legal review to legal and the invoice step to finance.
Watch out
it targets one task of one run, so map the run coming from the earlier module rather than picking a fixed one.
Process Street2

Create a Workflow Run

Action

In Make“Creates a new workflow run.”

Starts a brand new run of one of your workflows from Make, which means another app can launch the checklist instead of a person starting it by hand.

When to use it
when a deal closes in your CRM or a form is submitted, and the onboarding checklist should exist immediately.
Watch out
if Watch Workflow Runs sits in another scenario, the run you create here will fire it too.
Process Street3

Get a Task

Action

In Make“Retrieves an existing task.”

Fetches one existing task with its details, giving the following modules something precise to work with instead of a vague reference.

When to use it
after Watch Checked Tasks, when you need more about the ticked step than the trigger delivered before posting it to your team chat.
Watch out
it reads a single task; to go through every task of a run, use List Tasks instead.
Process Street4

Get a Workflow Run

Action

In Make“Retrieves an existing workflow run.”

Reads one workflow run you already know about and returns it whole, so later modules can reuse its details in their own fields.

When to use it
when a checked task arrives and you want context about the run it belongs to, such as which client checklist it is.
Watch out
you need the run to already be identified; if you only have a name, search first with Search Workflow Runs.
Process Street5

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Sends your own request to the Process Street API using the connection you already set up, which covers anything the 15 other modules do not.

When to use it
when you need an endpoint of the Process Street API that no ready module reaches.
Watch out
you write the request yourself, so keep the Process Street API documentation open to get the path and body right.
Process Street6

Unassign from a Task

Action

In Make“Unassigns a member from a certain task of a workflow run.”

Removes a member from a given task in a workflow run, which keeps task lists clean when people change roles or leave a project.

When to use it
when your HR tool marks someone as off the project and their open steps must go back to the team.
Watch out
removing the only assignee leaves the task without an owner, so pair it with Assign to a Task when needed.
Process Street7

Update a Workflow Run

Action

In Make“Updates an existing workflow run.”

Changes an existing workflow run from Make, so the run in Process Street reflects what happened in your other tools without anyone editing it by hand.

When to use it
when a deal moves forward in the CRM and the matching run should follow.
Watch out
it edits the run itself, not the answers in its forms; for those, pick Update Form Fields in a Workflow Run.
Process Street8

Update Form Fields in a Workflow Run

Action

In Make“Updates form fields of a workflow run.”

Fills or changes the form fields of a run with data from other apps, sparing your team from retyping client names, amounts or addresses.

When to use it
just after Create a Workflow Run, to prefill the checklist with what the CRM or signup form already knows.
Watch out
it writes into the run you point it at, so map the run from the earlier module before filling any value.
Process Street9

Get Workflow Run Form Field Values

Search

In Make“Retrieves form field values of a workflow run as a collection.”

Collects everything people entered in the forms of a run in a single collection, ready to send to a spreadsheet, invoice tool or report.

When to use it
when an audit or intake run is done and its answers belong in your tracking sheet.
Watch out
the values come grouped together, so map the ones you need individually in the next module.
Process Street10

List Data Set Records

Search

In Make“Lists records contained within a data set.”

Reads the records stored in one of your Process Street data sets, turning that reference table into bundles other apps can use.

When to use it
when a list of clients, sites or suppliers kept in Process Street should feed a sync with another tool.
Watch out
each record becomes its own bundle, and every following module then runs once per record, which adds operations.
Process Street11

List Task Form Fields

Search

In Make“Retrieves a list of all form fields of a task.”

Returns every form field attached to one task, showing exactly what that step asks the person to fill in.

When to use it
when a checked task should pass only its own answers on, not the whole run, for example a quality check result.
Watch out
the result can hold several fields, each a separate bundle, so a later module may run more than once.
Process Street12

List Tasks

Search

In Make“Retrieves a list of all tasks.”

Brings back all tasks you can reach, useful to spot which steps are still open or to hand work around in bulk.

When to use it
when a manager wants a digest of pending steps across runs pushed to a sheet or a chat channel.
Watch out
it can return many tasks at once, and each one then costs an operation in every module that follows.
Process Street13

List Workflow Run Form Fields

Search

In Make“Retrieves a list of all form fields of a workflow run.”

Shows the full set of form fields defined in a run, across all its tasks, one bundle per field.

When to use it
before an update, when you want to see which fields a run contains so you can map the right ones later.
Watch out
this lists the fields themselves; if you mostly want what people typed, Get Workflow Run Form Field Values is the quicker route.
Process Street14

Search Workflow Runs

Search

In Make“Searches for workflow runs or lists them all.”

Finds the workflow runs that match what you look for, or lists them all, so a scenario can locate the right checklist before acting on it.

When to use it
when an email or CRM update names a client and you need their run to update or assign.
Watch out
a search can return zero, one or several runs; plan for the empty case so the next module does not fail.
Need help

Need help automating Process Street with Make?

A person reads every message.

FAQ

Process Street and Make: common questions

01Is the Process Street Make integration free?
Yes, Process Street is a standard app in Make, so its modules are available on the Free plan. That plan limits you to 2 active scenarios, 15 minutes minimum between scheduled runs, 5 minutes of execution per run, 5 MB files and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) drop the interval to 1 minute, remove the cap on active scenarios and count usage in credits, one per operation. You also need your own active Process Street account.
02What is needed to connect Process Street to Make?
You need an active Process Street account and an API key. Generate the key from the organization integrations page in Process Street, name it if asked, then copy it. In Make, add a Process Street module, click Create a connection, optionally set a connection name, and paste the key. For the two instant triggers, click Create a webhook first. The connection is saved once and reused by every Process Street module in your scenarios.
03Does the Process Street trigger fire in real time?
Yes. Both Process Street triggers, Watch Checked Tasks and Watch Workflow Runs, are instant: Process Street calls Make through a webhook as soon as a task is checked or a run is created. There is no polling interval to wait for, unlike scheduled triggers that Make checks every 15 minutes by default. The scenario still needs to be switched on to receive these calls, and each module that runs uses one operation.
04What if a Process Street module is missing in Make?
Use Make an API Call. It sends any request to the Process Street API with the connection you already created, so an endpoint that none of the 15 other modules covers is still reachable. You write the request yourself from the Process Street API documentation. Also note that the Make documentation for this app is flagged as AI-generated from the vendor docs, so check important details directly with Process Street.
05Is Make or n8n better for Process Street?
It depends on the tool your team already runs. On Make, Process Street comes with 16 ready modules, including 2 instant triggers and a Make an API Call module for anything else, all usable without code on the Free plan. Many apps also have an n8n node, so check whether one exists for Process Street before choosing. Compare the modules each side offers against the steps your checklists actually need, then pick the one that covers them.
Same platform

Other docs you might need on this stack.

Browse all integrations