Resources · Make integration

Atwork Make integrationAutomate Atwork with Make.

Can Make read and write your Atwork data without a developer? Yes. The Atwork Make integration gives you 11 modules: 1 trigger, 6 actions and 4 searches. This page shows HR and ops teams how to connect the account and build a first working scenario.

Try the Atwork integration on MakeSee the 11 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Atwork Make integration do for you?

The Atwork Make integration links your Atwork account, an HR management app, to Make so that other tools can create, read, update and delete Atwork items without code. You build a scenario, which is the automation itself: a chain of modules, each one a single brick such as a trigger, an action or a search.

Feed Atwork from the tools people already use. An intake form, a signed document or a new row in a spreadsheet can end in a new Atwork record through Create an Item, and a later change can be pushed with Update an Item. Nobody retypes the same details twice.

React when something new lands in Atwork. Watch Items starts a scenario each time Make finds a new item, so a welcome message, a task in a project tool or a line in a report can follow on its own.

Get a clear picture before you change anything. List Sheets, List fields of a sheet and List Users show how the account is organized, which is the safest first step on an account you did not set up yourself.

A word of honesty: Make's own documentation for Atwork is marked as limited, because there is little public information about the app. The module names are known, their inner fields are not described, so test every module with Run once before you trust it. If you are new to the editor, the Make training covers the basics, and the Make review gives an outside view of the tool. Still choosing a platform? The n8n vs Make comparison lays out the criteria.

Connect

How do you connect Atwork to Make?

  1. 01

    Add an Atwork module

    Open a scenario, click the + and search for Atwork. Pick any module, for example List Sheets, then click Create a connection. A connection is your Atwork account linked to Make once, then reused by every Atwork module.

  2. 02

    Name the connection

    Make offers a name field for the connection. It is optional, but a clear label such as the team or the account owner helps a lot once several people share the same Make organization.

  3. 03

    Authorize and save

    Depending on what Atwork asks for, either approve access on the Atwork page that opens, or paste the key Atwork gives you. Then click Save. Make can now list the sheets and items your account can reach.

First scenario

Your first scenario with Atwork

GoalWhen a new hire fills in an onboarding form, Make creates the matching item in Atwork.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to place the first module. Here it comes from your form tool, the app where the new hire answers.

  2. 02

    Set the starting module

    Search your form app, pick the module that watches new answers and click Create a connection to link that account. Each answer then travels as a bundle, one item passed from module to module.

  3. 03

    Add Create an Item

    Click the + on the right of the first module, search Atwork and choose Create an Item. Once the connection exists, Make lists the sheets it can read, so you pick the right one from a menu.

  4. 04

    Map the answers

    Fill each Atwork field by clicking the matching answer from the form module. Make shows the fields the chosen sheet offers, and any field you do not need yet can stay empty.

  5. 05

    Test with Run once

    Submit a test answer, then click Run once. Open the bubbles above each module to read the bundles it received, and check in Atwork that the new item looks right.

  6. 06

    Schedule and switch on

    Click the clock on the first module to set the schedule, every 15 minutes by default, then switch the scenario on. On the Free plan, 15 minutes is also the shortest gap between two scheduled runs.

Triggers

What can start a scenario from Atwork?

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

Atwork1Watch Items

Watch Items

triggerIn the docs only

Watch Items hands your scenario every new Atwork item Make finds, so the next modules can act on it without anyone checking the app by hand.

How it fires
scheduled, Make checks the app on the scenario's schedule. The clock badge on the module shows it, and the default schedule is every 15 minutes.
When to use it
when a new record in Atwork should trigger follow-up work elsewhere, such as a message to a manager or a task in a project board.
Watch out
Make's documentation does not describe this module in detail, so run it once on a test item and read the bundle before you connect anything downstream.
Modules

What else can Make do in Atwork?

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

Atwork1

Create an Item

ActionIn the docs only

Create an Item adds a fresh record to Atwork from data another module passed along, which saves the copy and paste between your tools.

When to use it
a form answer, a signed contract or a new row elsewhere should become an Atwork entry.
Watch out
run it on test data first, since each run leaves a real item behind.
Atwork2

Delete an Item

ActionIn the docs only

Delete an Item removes one Atwork record for you, so duplicates or test entries disappear without a manual cleanup session.

When to use it
after a search has found the exact item that must go, never on a guess.
Watch out
Make cannot bring a deleted item back, so add a filter before this module and test it on a dummy record.
Atwork3

Get a Sheet

ActionIn the docs only

Get a Sheet returns the details of one Atwork sheet, which gives later modules the context they need about where the data lives.

When to use it
you already know which sheet matters and want its information inside the scenario, rather than a full list.
Watch out
the documentation does not say which details come back, so check the output bundle with Run once.
Atwork4

Get an Item

ActionIn the docs only

Get an Item fetches one specific Atwork record so you can reuse its values further down the scenario, for a message, a document or a comparison.

When to use it
you already reached the item through an earlier module, for example Watch Items or List Items, and need its current content, not a search across the sheet.
Watch out
the module has to be told which item to fetch, so map it from a previous step instead of typing it by hand.
Atwork5

List Items

SearchIn the docs only

List Items pulls several Atwork records into the scenario at once, which is the base for exports, reports and bulk corrections.

When to use it
you want every item of a sheet in a spreadsheet, or you need to loop over them to update each one.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per bundle, which counts operations on your plan.
Atwork6

List Sheets

SearchIn the docs only

List Sheets shows which sheets your connected Atwork account holds, a quick map of the account before you build anything on top of it.

When to use it
on the first test of a new connection, or when a scenario must pick a sheet on its own instead of a fixed one.
Watch out
it only returns what the authorized account can see, so a missing sheet usually points to access rights.
Atwork7

List Users

SearchIn the docs only

List Users brings the people of your Atwork account into Make, handy when an automation has to know who is who before it assigns or notifies anyone.

When to use it
matching a record to its owner, or keeping a directory in another tool aligned with Atwork.
Watch out
the returned details are not documented, so read one bundle with Run once before you map fields.
Atwork8

List fields of a sheet

SearchIn the docs only

List fields of a sheet reveals the columns a sheet expects, so you know exactly what to fill before you map data into Create an Item or Update an Item.

When to use it
preparing a new scenario on a sheet you did not design, or checking a sheet after someone changed its layout.
Watch out
it describes structure, not records, so pair it with List Items to see actual values.
Atwork9

Make an API Call

ActionIn the docs only

Make an API Call lets you reach any endpoint of the Atwork API with the same connection, which covers whatever the ready-made modules leave out.

When to use it
the action you need has no module of its own in the list above.
Watch out
you write the request yourself, so test it with Run once and read the answer before you switch the scenario on.
Atwork10

Update an Item

ActionIn the docs only

Update an Item changes an existing Atwork record in place, so the app stays current when the source of truth lives in another tool.

When to use it
a manager edits a detail in a form or spreadsheet and Atwork should reflect it without a second entry.
Watch out
if the same scenario starts with Watch Items, make sure your changes do not feed it back into itself.
Need help

Need help automating Atwork with Make?

A person reads every message.

FAQ

Atwork and Make: common questions

01Is the Atwork Make integration free?
Yes, Atwork is a standard app in Make, so it works on the Free plan. That plan has limits worth knowing: 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 (Core, Pro, Teams and Enterprise) lower the gap to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in operations, each one being one module processing one bundle.
02What do you need to connect Atwork to Make?
An Atwork account and a Make account. Make's documentation lists no special prerequisite for Atwork and gives no dedicated connection steps, so the generic flow applies: add any Atwork module, click Create a connection, optionally name it, then either approve access on the Atwork page or paste the key Atwork provides, and click Save. The connection is created once and every Atwork module in your scenarios reuses it, so you never sign in twice.
03Does the Atwork trigger in Make fire instantly?
No. Make's documentation only lists Watch Items by name, and its type points to a scheduled trigger: Make checks Atwork on the scenario's schedule rather than being called by Atwork the moment something changes. A new scenario runs every 15 minutes by default, which is also the shortest gap on the Free plan; paid plans go down to 1 minute. If a process truly cannot wait, start the scenario from the tool where the event happens and use Create an Item or Update an Item on the Atwork side.
04What if an Atwork module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Atwork API with your existing connection, so an action with no ready-made module is still possible. Keep in mind that Make marks its Atwork documentation as limited, since little public information exists about the app. That means fewer explanations inside Make, so read the bundles returned by Run once to learn what each module sends back, and test every custom call on sample data first.
05Should you use Make or n8n for Atwork?
It depends on the tool you already run, not on Atwork itself. On Make, Atwork comes with 11 ready-made modules, including a scheduled trigger and a Make an API Call module for anything else, and it is available from the Free plan. Many apps also have an n8n node, so check whether Atwork does, compare the modules each platform offers for the exact actions you need, then pick the editor your team is comfortable maintaining. The two tools are not ranked here.
Same platform

Other docs you might need on this stack.

Browse all integrations