Resources · Make integration

Automation Toolbox (ADP Workforce Tools) Make integrationAutomate Automation Toolbox (ADP Workforce Tools) with Make.

Need your employee records inside other tools without copying them by hand? The Automation Toolbox (ADP Workforce Tools) Make integration gives you 3 modules: 2 searches and 1 action. This page shows HR and ops teams how to link the account and build a first scenario step by step.

Try the Automation Toolbox (ADP Workforce Tools) integration on MakeSee the 3 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Automation Toolbox (ADP Workforce Tools) Make integration do?

Make reads your employee data from Automation Toolbox (ADP Workforce Tools) and hand it to the rest of your tools. In Make, you build a scenario, which is the automation itself: a chain of modules, where each module is one brick, such as a search or an action. This app brings two searches and one open API action.

Check a person before anything else happens. A request arrives in another app, for example a form or a sheet, and Find an employee looks up the matching record. The scenario only goes further when a result comes back, so later modules work with a real person, not a typo.

Pull the whole staff list into another tool. List Employees sends each person as a separate bundle, which is one item passing from one module to the next. Map those bundles into a spreadsheet or a directory and the copy-paste job disappears.

Reach what the listed modules skip. Make an API Call calls any endpoint of the app's API with the same connection. It suits a builder who already knows which endpoint holds the data.

A limit to know up front: Make's own documentation for this app is marked as limited, because little public information exists about it. Test each module with Run once before relying on it. If the setup gets stuck, the Make troubleshooting guide helps, and the Make review covers the platform as a whole. Weighing another tool? The n8n vs Make comparison lays out the criteria.

Connect

How do you connect Automation Toolbox (ADP Workforce Tools) to Make?

  1. 01

    Add a module and create the connection

    In your scenario, add any Automation Toolbox (ADP Workforce Tools) module, then click Create a connection. A connection is your account linked to Make once and reused by every module of this app.

  2. 02

    Name it so you recognize it later

    Giving the connection a name is optional, but it pays off when several people or several accounts share the same Make organization. A clear label saves a guess when you pick it in another module.

  3. 03

    Authorize Make, then save

    Depending on what the app asks, approve Make on the app's own page or paste the key the app gives you. Then click Save. The module now shows the connection and its fields become available.

First scenario

Your first scenario with Automation Toolbox (ADP Workforce Tools)

GoalWhen a request lands in another app, Make looks up the employee in Automation Toolbox (ADP Workforce Tools) and passes the record along.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. This app has no trigger, so the first module comes from the tool where requests start.

  2. 02

    Set the starting module

    Search that other app by name, pick the module that picks up new requests, and connect its account. Each request it finds becomes one bundle for the next module.

  3. 03

    Add Find an employee

    Click the + on the right, search Automation Toolbox (ADP Workforce Tools) and choose Find an employee. Map the value that identifies the person from the previous module into its fields.

  4. 04

    Test with Run once

    Click Run once. Make executes the scenario one time, and you can open each module to read the bundles it received. Check that the right person came back.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. Each module run on one bundle counts as one operation on your plan.

Modules

What the 3 modules do

Automation Toolbox (ADP Workforce Tools) gives you 3 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Automation Toolbox (ADP Workforce Tools)1

Find an employee

SearchIn the docs only

Looks up one person in Automation Toolbox (ADP Workforce Tools) and returns what it finds, so the next modules can use that record instead of a name typed by hand.

When to use it
a request mentions a colleague and you want to confirm the person exists before the scenario creates or sends anything.
Watch out
a search can return zero, one or several bundles, so plan what happens when nobody matches.
Automation Toolbox (ADP Workforce Tools)2

List Employees

SearchIn the docs only

Brings back your employees as a series of bundles, one per person. That gives you a whole list to push somewhere else, rather than one targeted record.

When to use it
you want every person copied into a sheet or a directory, not a single lookup on demand.
Watch out
each bundle then runs through the following modules, and every run of a module counts as one operation, so a long list uses more of your plan.
Automation Toolbox (ADP Workforce Tools)3

Make an API Call

ActionIn the docs only

Opens the rest of the app's API from your scenario, with the connection you already set up. It is the fallback when the two searches do not return what you need.

When to use it
you know which endpoint of the app holds the data and no listed module reaches it.
Watch out
the documentation for this app is limited, so read the answer in Run once before building anything on it.
Need help

Need help automating Automation Toolbox (ADP Workforce Tools) with Make?

A person reads every message.

FAQ

Questions about the Automation Toolbox (ADP Workforce Tools) Make integration

01Is the Automation Toolbox (ADP Workforce Tools) Make integration free?
Yes, on Make's side. It is a standard app, available from the Free plan. That plan allows 2 active scenarios, runs no more often than every 15 minutes, stops a run after 5 minutes, handles files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lower the interval to 1 minute and remove the cap on active scenarios. Usage is counted in operations per month. This page does not cover what the app itself costs.
02What do you need to connect Automation Toolbox (ADP Workforce Tools) to Make?
An account on the app and a Make account. Make's documentation lists no specific prerequisite and gives no dedicated connection steps, so the generic flow applies: add a module, click Create a connection, optionally name it, authorize Make on the app's page or paste the key the app provides, then click Save. The connection is reused by all 3 modules, so you only do this once per account. Keep the connection in the account that owns the data, so teammates reuse it without new credentials.
03Can Automation Toolbox (ADP Workforce Tools) start a Make scenario in real time?
No, because the app has no trigger module in Make. A scenario still starts in two ways. It can run on a schedule set on its first module, every 15 minutes by default, or every minute on a paid plan. It can also open on a trigger from another app, such as a form or a sheet, and then call Find an employee or List Employees for the data it needs. Start with the schedule if you only need fresh data at regular points.
04What if the module you need is missing?
Use Make an API Call. It calls any endpoint of the app's API with the same connection, which covers what Find an employee and List Employees do not. Make's documentation for this app is marked as limited, since little public information exists, so you will need to know the endpoint yourself. Run once shows the raw answer before you map it anywhere. Keep the call scoped to one endpoint at a time, so each result stays easy to read and map.
05Should you use Make or n8n with Automation Toolbox (ADP Workforce Tools)?
It depends on what each tool offers for this app. In Make you get 3 modules: two searches and Make an API Call, which reaches the rest of the API. Many apps also have an n8n node, so check whether one exists for this app before deciding. Neither tool is ranked above the other here. Compare the modules available against the job you need done, then pick. The n8n vs Make comparison linked above goes through the criteria in more detail.
Same platform

Other docs you might need on this stack.

Browse all integrations