Resources · Make integration

Atarim Make integrationAutomate Atarim with Make.

Website feedback piles up fast, and the Atarim Make integration lets it move on its own. Make offers 17 Atarim modules: 8 triggers that spot new tasks, comments or time entries, and 9 actions that create, assign or update them. This guide walks you from connection to a first working scenario.

Try the Atarim integration on MakeSee the 17 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Atarim Make integration do for your team?

The Atarim Make integration links your Atarim account to Make, a visual tool where you build a scenario (the automation itself: a chain of modules, run on a schedule or when an app calls Make). Each module is one brick of that chain. With Atarim, those bricks watch your projects for new activity and write tasks, comments, notes or time entries back, without any code.

Route new feedback to the right person. Watch New Task spots a fresh task on a client site, and Assign User To Task hands it to the developer or designer who owns that part of the project. Nobody has to triage the inbox by hand.

Keep the client thread alive. When a task moves forward in another tool, Create New Task Comment posts an update on the Atarim task, so the client sees progress where they left their feedback. Change Task Status can close the loop at the same moment.

Feed time tracking into reporting. Watch New Time Entry picks up logged hours, and the next module can copy them into a spreadsheet or an invoicing app. The reverse also works: Create Time Entry records hours that were tracked elsewhere.

Two things to know before you start. Make's documentation lists the Atarim triggers without saying how they fire; as Watch modules they work as scheduled triggers, so Make checks Atarim on the scenario's schedule instead of hearing from it instantly (look for the clock badge). And the connection needs an Atarim Pro Business or Enterprise plan. If a module is missing, Make an API Call reaches the rest of the Atarim API. Many apps also have an n8n node; the n8n vs Make comparison lays out the differences, and the Make training covers the editor from the ground up. If you want a team to build it, see the Make agency.

Connect

How do you connect Atarim to Make?

  1. 01

    Copy your Atarim API key

    In your Atarim dashboard, open Settings, then Integration Settings. Toggle the Make integration on and copy the API key that appears on screen. Keep it handy for the next step.

  2. 02

    Add an Atarim module in Make

    Open a scenario, add any Atarim module and click Create a connection. A connection is your Atarim account linked to Make once, then reused by every Atarim module. The Connection name field is optional; a client or workspace name helps later.

  3. 03

    Paste the key and save

    Paste the API key you copied from Atarim, or follow the instructions Make shows on screen, and save. Make then fills the module fields with what it can read from your account, so you pick options from a list.

First scenario

Your first scenario: assign every new Atarim task

GoalWhen a new task appears in Atarim, Make assigns it to the teammate you choose.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to add the first module. Type Atarim in the search box.

  2. 02

    Set Watch New Task as the trigger

    Pick Watch New Task, then click Create a connection or choose the one you already made. Fill the module fields; Make lists what it can read from your Atarim account.

  3. 03

    Add Assign User To Task

    Click the + on the right of the trigger, search Atarim again and pick Assign User To Task. Map the task from the previous module so Make knows which task to hand over.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario one time and shows the bundles each module received. A bundle is one item passing between modules, here one task. Check that the right person was assigned.

  5. 05

    Schedule it and switch it on

    Click the clock on the first module to set the schedule. A new scenario runs every 15 minutes by default. Then flip the scenario on, and new tasks start finding their owner without you.

Triggers

Atarim triggers: what starts your scenario

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

Atarim1Watch New Priority

Watch New Priority

triggerIn the docs only

Starts a scenario whenever Make finds a new priority in Atarim, so urgent feedback does not sit unnoticed among the rest. The priority reaches the next module as a bundle you can route anywhere.

How it fires
scheduled: Make checks the app on the scenario's schedule, every 15 minutes by default on a new scenario.
When to use it
an agency wants the account manager to hear about a task flagged high at the next check, through a message or an email sent by the following module.
Watch out
Make lists this module without an official description, so run it once and read the bundle to see exactly what Atarim returns.
Atarim2Watch New Status

Watch New Status

triggerIn the docs only

Gives you a hook on status activity in Atarim: when Make spots a new status, your scenario runs and the following modules can react to it. Handy for keeping a project board in another tool aligned.

How it fires
scheduled: Make checks the app on the scenario's schedule, so the reaction comes at the next check rather than the second it happens.
When to use it
a developer marks work as done in Atarim and the project manager wants the matching card in their own tracker to follow.
Watch out
run it once before switching the scenario on, and read the bundle to confirm what a new status means in your account.
Atarim3Watch New Tag

Watch New Tag

triggerIn the docs only

Lets tags drive your automation. Each new tag Make finds in Atarim starts the scenario, so a label your team already uses becomes a signal that sets off work elsewhere without anyone copying it over.

How it fires
scheduled: Make checks the app on the scenario's schedule, which you set with the clock on this first module.
When to use it
your team tags feedback by topic, such as copy or design, and each topic should land with a different person or channel.
Watch out
add a filter after the trigger if only some tags matter, otherwise every tag uses an operation on each run of the modules that follow.
Atarim4Watch New Task

Watch New Task

triggerIn the docs only

The trigger most teams start with: every new task Make finds in Atarim, often a piece of client feedback, launches the scenario and passes the task on as a bundle ready to be assigned, copied or announced.

How it fires
scheduled: Make checks the app on the scenario's schedule, every 15 minutes by default, down to 1 minute on paid plans.
When to use it
a client leaves feedback on a staging site and the task should reach your ticketing tool or the right developer with no manual triage.
Watch out
on the Free plan the shortest gap between two scheduled runs is 15 minutes, so plan your expectations around that.
Atarim5Watch New Task Comment

Watch New Task Comment

triggerIn the docs only

Brings every new comment on an Atarim task into Make, so replies from a client or a teammate can travel beyond Atarim and reach people who never open it. Each comment becomes one bundle for the next module.

How it fires
scheduled: Make checks the app on the scenario's schedule, not the instant the comment is posted.
When to use it
the project lead lives in a chat app and wants client replies on tasks forwarded there, instead of checking each site.
Watch out
if the same scenario also posts comments with Create New Task Comment, it may pick up its own messages; filter them out after the trigger.
Atarim6Watch New Task Note

Watch New Task Note

triggerIn the docs only

Tracks the notes added to tasks, which teams often use for internal context the client does not need to see. Each new note found by Make runs the scenario and can be stored or shared with the people who need it.

How it fires
scheduled: Make checks the app on the scenario's schedule, set with the clock on this module.
When to use it
a developer writes a technical note on a task and the lead wants a copy in the project documentation kept in another tool.
Watch out
notes can be internal, so think about where the next module sends them before switching the scenario on.
Atarim7Watch New Time Entry

Watch New Time Entry

triggerIn the docs only

Turns hours logged in Atarim into data you can reuse. Every new time entry Make finds starts the scenario, and the following module can add it to a spreadsheet, a report or an invoicing tool.

How it fires
scheduled: Make checks the app on the scenario's schedule, every 15 minutes by default.
When to use it
a freelancer or agency bills by the hour and wants logged time on client tasks gathered in one place without retyping.
Watch out
each entry is one bundle, so a busy period means more operations, the unit Make counts on your plan, for every module after the trigger.
Atarim8Watch New Website

Watch New Website

triggerIn the docs only

Kicks off onboarding work each time a website is added to Atarim. Make passes the new site on as a bundle, so the rest of the scenario can prepare everything that usually follows a new project.

How it fires
scheduled: Make checks the app on the scenario's schedule, so the new site is picked up at the next check.
When to use it
an agency adds a client site for review and wants a project record created in its CRM or a welcome message sent to the team.
Watch out
Make lists it without an official description, so test it with Run once to see which site details come through.
Modules

Atarim actions: what Make can do in your account

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

Atarim1

Assign User To Task

ActionIn the docs only

Puts a named person in charge of an Atarim task, so the work has an owner the moment it arrives. It pairs naturally with Watch New Task at the start of the scenario.

When to use it
feedback on a given site or topic should always go to the same developer or designer.
Watch out
map the task from the previous module rather than typing it, or every run will target the same task.
Atarim2

Change Task Status

ActionIn the docs only

Moves an Atarim task to a different status from outside Atarim, which keeps the client view honest when the real work is tracked in another tool.

When to use it
a ticket is closed in your development tracker and the matching Atarim task should show it too, without someone updating both.
Watch out
a scenario that watches statuses and changes them can trigger itself; keep those two jobs in separate scenarios or filter.
Atarim3

Change Task Urgency

ActionIn the docs only

Raises or lowers how urgent a task is in Atarim, so priorities follow rules instead of someone's memory. Choose it over Change Task Status when the task stays where it is but deserves more attention.

When to use it
a feedback task from a client on a tight launch should jump ahead of the rest of the queue.
Watch out
run once on a test task first, to check how the urgency values look in your account.
Atarim4

Create New Task

ActionIn the docs only

Adds a task to Atarim from data that started somewhere else, such as a form, an email or a support ticket. Your team then handles every request in the same place it already reviews feedback.

When to use it
a client sends a change request by email and it should become an Atarim task on the right site without copy and paste.
Watch out
one task is created per bundle, so a trigger that returns several items creates several tasks.
Atarim5

Create New Task Comment

ActionIn the docs only

Posts a comment on an existing Atarim task, where the client can read it. It is the way to report progress back into the conversation the client started, rather than in a separate email.

When to use it
a fix goes live and the scenario tells the client on the original task that it is ready to check.
Watch out
comments are visible to the people on the task, so keep internal remarks for Create New Task Note.
Atarim6

Create New Task Note

ActionIn the docs only

Attaches a note to an Atarim task, a good home for context your team needs next to the feedback, like a link to a commit or a summary from another tool.

When to use it
a developer tool records what was changed, and the scenario leaves that detail on the task for whoever reviews it next.
Watch out
pick this module over a comment when the text is for your team; check in a test run where the note appears.
Atarim7

Create New Task Tag

ActionIn the docs only

Adds a tag to an Atarim task so it can be sorted, filtered or picked up by another scenario. Tags written by Make work like the ones your team adds by hand.

When to use it
tasks coming from a specific form or client should carry a label that makes them easy to find in Atarim.
Watch out
if another scenario runs Watch New Tag, a tag added here can set it off; that chain can be useful or a loop.
Atarim8

Create Time Entry

ActionIn the docs only

Records time in Atarim from outside it, so hours tracked in another app still end up next to the tasks they belong to. The mirror of Watch New Time Entry.

When to use it
your team logs hours in a dedicated time tracker and the project manager wants Atarim to show the full picture per task.
Watch out
if a scenario also watches time entries, avoid sending the same hours back and forth between the two tools.
Atarim9

Make an API Call

ActionIn the docs only

Reaches any endpoint of the Atarim API from your scenario, using the same connection as the other modules. It covers whatever the ready-made Atarim modules leave out.

When to use it
you need an Atarim operation that has no dedicated module above, and the API documentation from Atarim describes it.
Watch out
you build the request yourself here, so keep Atarim's own API documentation open and test with Run once.
Need help

Need help automating Atarim with Make?

A person reads every message.

FAQ

Atarim and Make: common questions

01Is the Atarim Make integration free?
Yes, on the Make side. Atarim is a standard app, available from the Free plan, which allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes per run and files up to 5 MB. Paid plans such as Core, Pro, Teams and Enterprise lower the interval to 1 minute and remove the cap on active scenarios. On the Atarim side, the connection requires a Pro Business or Enterprise plan, so check your Atarim subscription before you start building.
02What do you need to connect Atarim to Make?
An active Atarim account on a Pro Business or Enterprise plan and its API key. To get the key, go to Settings in your Atarim dashboard, open Integration Settings, turn the Make integration on and copy the key shown. In Make, add an Atarim module, click Create a connection, give it a name if you like and paste the key. The same connection then serves all 17 Atarim modules in every scenario you build.
03Do Atarim triggers in Make fire instantly?
No. Make's documentation does not give their type, but all 8 Atarim triggers are Watch modules and work as scheduled triggers: Make checks Atarim on the scenario's schedule instead of being called by Atarim. The clock badge on the module confirms it. A new scenario checks every 15 minutes by default. You can shorten that down to 1 minute on a paid plan, while the Free plan keeps a minimum of 15 minutes. For most feedback routing, that delay is fine; if you need faster reactions, a paid plan is the lever.
04What if the Atarim module you need is missing in Make?
Use Make an API Call. It is part of the Atarim app in Make and lets a scenario call any endpoint of the Atarim API with the same connection, so you are not limited to the ready-made modules. You write the request yourself, so keep the Atarim API documentation at hand and test with Run once. Note that the Make documentation for Atarim is AI-generated from the Atarim docs and suggests contacting Atarim for anything important.
05Should you use Make or n8n for Atarim?
It depends on how you like to work. Make gives you 17 Atarim modules in a visual editor, with a guided connection and a Free plan to try things. Many apps also have an n8n node, so check whether Atarim does. Compare the two on what matters for your case: which Atarim actions each one offers and which editor your team finds easier to read and maintain. The n8n vs Make comparison on this site goes through those criteria. Test your first scenario before committing.
Same platform

Other docs you might need on this stack.

Browse all integrations