Resources · Make integration

Traction Tools Make integrationAutomate Traction Tools with Make.

Can Make keep your rocks, issues and to-dos moving without copy and paste? The Traction Tools Make integration gives you 29 modules: 3 triggers, 21 actions and 5 searches. This page shows leadership teams how to link the account and build a first scenario that works.

Try the Traction Tools integration on MakeSee the 29 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Traction Tools Make integration do?

The Traction Tools Make integration links your Traction Tools account to Make, a no-code tool where you build a scenario: an automation made of modules, each one a brick that watches, reads or changes data. Make can spot new headlines, issues and to-dos, then create or update rocks, measurables and scores for you.

An issue never stays ownerless. Watch Issues picks up each new issue, and Create a Personal To-Do hands a follow-up task to the person who raised it, so the topic reaches the next meeting with someone already on it.

The scorecard fills itself. When a number lands in another tool, such as a sales total in your CRM, Get a Current Week finds the right week and Update a Score writes the value, so nobody retypes figures before the meeting.

Headlines reach the whole team. Watch Headlines catches each good news item posted in Traction Tools, and the next module can forward it to your chat or email app.

Make does not replace Traction Tools: the modules read and write the objects the app already has, and anything outside the list goes through Make an API Call. The same app may also exist as an n8n node; the n8n vs Make page helps you pick. To learn the editor step by step, see our Make training, and check Make pricing before you scale.

Connect

How do you connect Traction Tools to Make?

  1. 01

    Add a Traction Tools module

    Log in to Make, open your scenario and add any Traction Tools module. Click Create a connection. A connection is your account linked to Make once, then reused by every Traction Tools module you add later.

  2. 02

    Name the connection

    The Connection name field is optional, but a clear name helps when several people or accounts share the same Make organization. Pick something like the team or workspace it belongs to.

  3. 03

    Paste your API key

    Enter the credentials you copied from your Traction Tools account, or follow the instructions shown on screen. The doc asks for an active Bloom Growth account and an API key, so have both ready before you start.

First scenario

Build your first scenario with Traction Tools

GoalWhen a new issue is created in Traction Tools, Make adds a personal to-do so someone owns the follow-up.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to place the first module on the canvas.

  2. 02

    Add Watch Issues

    Search for Traction Tools, pick Watch Issues and click Create a connection to link your account with the API key.

  3. 03

    Add Create a Personal To-Do

    Click the + on the right of the trigger and choose Create a Personal To-Do. Map the issue details from the previous module into the to-do so the task reads clearly.

  4. 04

    Test with Run once

    Create a test issue in Traction Tools, then click Run once. Open each module's bubble to read the bundle it received: a bundle is one item, here one issue.

  5. 05

    Schedule and switch it on

    Open the clock on the first module. A new scenario checks every 15 minutes by default, and the Free plan cannot go lower. Save, then switch the scenario on.

Triggers

What can start a Traction Tools scenario?

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

Traction Tools1Watch Headlines

Watch Headlines

Scheduled trigger

In Make“Triggers when a new headline is created.”

Every new headline posted in Traction Tools becomes a bundle your scenario can pass along, so good news and customer feedback travel beyond the app without anyone reposting them.

How it fires
scheduled. Make checks the app on the scenario's schedule and collects the headlines created since the last check.
When to use it
forward each headline to the channel where the wider company reads announcements.
Watch out
headlines arrive in batches at each check, not one by one as they are typed.
Traction Tools2Watch Issues

Watch Issues

Scheduled trigger

In Make“Triggers when a new issue is created.”

You get a signal each time someone adds an issue, which lets you assign, log or announce it before the next meeting instead of discovering it on the day.

How it fires
scheduled. Make checks the app on the scenario's schedule, so a new issue shows up at the next check.
When to use it
create a follow-up to-do or post a note to the team's chat whenever an issue lands on the list.
Watch out
it reacts to new issues only; edits to an existing issue do not start the scenario.
Traction Tools3Watch To-Dos

Watch To-Dos

Scheduled trigger

In Make“Triggers when a new To-Do is created.”

New to-dos flow out of Traction Tools and into the tools where people actually work, such as a task board or a shared calendar, so commitments stay visible.

How it fires
scheduled. Make checks the app on the scenario's schedule and returns the to-dos created since the previous check.
When to use it
mirror each new to-do into the project tool the owner already works in.
Watch out
if another scenario creates to-dos, this trigger will see them too, so avoid feeding its output back into Traction Tools.
Modules

What else can Make do in Traction Tools?

Traction Tools gives you 26 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Traction Tools1

Create a Measurable

Action

In Make“Creates a new measurable.”

A new line appears on your scorecard without anyone opening the settings, which helps when a metric starts life in another system first.

When to use it
a new KPI is approved in your planning sheet and should show up in Traction Tools right away.
Watch out
run a List Measurables first if the metric might already exist, or you will end up with twins.
Traction Tools2

Create a Meeting To-Do

Action

In Make“Creates a To-Do for a meeting.”

This adds a to-do tied to a meeting, so the action item is visible to the whole team during the review rather than hidden in one person's list.

When to use it
a form or a ticket closes with a decision the team must follow up on together.
Watch out
for a task only one person needs to see, Create a Personal To-Do is the better fit.
Traction Tools3

Create an Issue

Action

In Make“Creates an issue.”

Problems raised elsewhere land on the issues list automatically, so they get discussed instead of lost in an inbox or a support queue.

When to use it
a customer complaint or a failed check in another app should become a topic for the team.
Watch out
if Watch Issues runs in another scenario, each issue you create here will trigger it too.
Traction Tools4

Create a Personal To-Do

Action

In Make“Creates a personal To-Do.”

One person gets a private task in their own list, which keeps small follow-ups off the shared meeting view.

When to use it
a new issue, a signed deal or a form reply calls for a specific owner to act.
Watch out
map details from the previous module into the to-do; a bare task is hard to understand later.
Traction Tools5

Create a Rock

Action

In Make“Creates a rock.”

Priorities set in a planning document become rocks in Traction Tools without retyping, so the team starts from a list already in place.

When to use it
goals are approved in a sheet or a form, and each row should turn into a rock.
Watch out
Make creates one rock per bundle, so a sheet with duplicate rows gives duplicate rocks.
Traction Tools6

Delete a Rock

Action

In Make“Delete a rock.”

Removing a rock from a scenario keeps the list clean when a goal is cancelled in the tool where decisions are recorded.

When to use it
a priority is dropped in your planning tool and should disappear from Traction Tools as well.
Watch out
a deletion cannot be undone from Make; test it on a dummy rock with Run once before you switch the scenario on.
Traction Tools7

Get a Current Week

Action

In Make“Gets a current week.”

Make fetches the week Traction Tools considers current, giving later modules the reference they need to write numbers into the right column.

When to use it
place it right before Update a Score so the value lands in this week, not a past one.
Watch out
it returns a reference, not scores; pair it with Get a Score or Update a Score to do something useful.
Traction Tools8

Get a Headline

Action

In Make“Gets a headline.”

You pull the full detail of one headline when you already know which one you want, for example to quote it in a summary.

When to use it
after Watch Headlines or List Headlines, to read the complete record before sending it elsewhere.
Watch out
it needs the headline's ID; without it, start with List Headlines to find the right one.
Traction Tools9

Get a Measurable

Action

In Make“Gets a measurable.”

Reading a single measurable tells your scenario what the metric is and how it is set up before you change anything on it.

When to use it
check a metric's details ahead of Update a Measurable or before posting it in a report.
Watch out
one ID gives one measurable; to scan the whole scorecard, List Measurables is the right module.
Traction Tools10

Get an Issue

Action

In Make“Gets an issue.”

The complete record of one issue comes back to Make, handy when the trigger only gave you part of the story.

When to use it
before updating an issue, to confirm what it currently says and who owns it.
Watch out
it reads one issue by ID; to browse several, List Issues is the module to pick.
Traction Tools11

Get a Personal To-Do

Action

In Make“Gets a personal To-Do.”

Pull one personal to-do to see its current state, which lets a scenario decide whether a reminder is still needed.

When to use it
a reminder flow checks the task before nudging the owner by email or chat.
Watch out
it reads a single to-do by ID; List To-Dos is the one that returns several at once.
Traction Tools12

Get a Rock

Action

In Make“Gets a rock.”

This returns the details of one rock so you can show its progress outside Traction Tools or feed it into a status report.

When to use it
a dashboard or a board update needs the current state of a named priority.
Watch out
you need the rock's ID; without it, start with List Rocks.
Traction Tools13

Get a Score

Action

In Make“Gets a score.”

Make reads one scorecard value, which is how you compare a number in Traction Tools with the one in your source system.

When to use it
before Update a Score, to skip the write when the value is already correct.
Watch out
place Get a Current Week before it so you read this week's value, not an old one.
Traction Tools14

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

This module reaches any endpoint of the Traction Tools API with the connection you already have, which covers what the listed modules leave out.

When to use it
you need an object or an option that no ready-made module offers.
Watch out
you write the request yourself, so keep the Traction Tools API documentation open while you build it.
Traction Tools15

Update a Headline

Action

In Make“Updates a headline.”

Fixing a headline from a scenario keeps the text in line with its source, such as a corrected figure or a renamed customer.

When to use it
the original news changes in the tool where it was first recorded.
Watch out
test the change on a sample headline with Run once before the scenario touches real ones.
Traction Tools16

Update a Measurable

Action

In Make“Updates a measurable.”

You adjust how a metric is defined without opening the scorecard in Traction Tools, keeping it aligned with the tool where KPIs are decided.

When to use it
a KPI is redefined in your planning tool and the scorecard should follow.
Watch out
this changes the metric itself, not a value; numbers go through Update a Score.
Traction Tools17

Update an Issue

Action

In Make“Updates an issue.”

Keep an issue current from the outside: new details, another owner or a status that changed in the tool where the work happens.

When to use it
a support ticket linked to the issue is resolved and the issue should reflect it.
Watch out
find the right issue first with List Issues or Get an Issue, since a wrong ID updates the wrong topic.
Traction Tools18

Update a Personal To-Do

Action

In Make“Updates a personal To-Do.”

Changing a personal to-do from Make keeps its wording in sync with the project tool where the task really lives.

When to use it
the linked task is edited elsewhere and the Traction Tools copy should follow.
Watch out
to mark it done, Update a Personal To-Do Completion is the dedicated module.
Traction Tools19

Update a Personal To-Do Completion

Action

In Make“Updates personal To-Dos completion.”

Ticking a to-do as done happens on its own when the matching work is finished somewhere else, so the meeting list stays honest.

When to use it
a task is closed in your project board and its twin in Traction Tools should close too.
Watch out
it only changes completion; use Update a Personal To-Do for the text.
Traction Tools20

Update a Rock

Action

In Make“Updates a rock.”

Rock details and status can follow what happens in the project tool, sparing the owner a second update before the meeting.

When to use it
a project milestone moves, and the related rock should show the new state.
Watch out
map the rock ID from a previous module; List Rocks helps you find it first.
Traction Tools21

Update a Score

Action

In Make“Updates a score.”

Scorecard numbers reach the scorecard straight from the system that produces them, which removes the manual entry before each meeting.

When to use it
revenue, leads or tickets are counted in another app and should land on the matching measurable.
Watch out
the value must target the right week, so place Get a Current Week before this module.
Traction Tools22

List Headlines

Search

In Make“Gets all headlines owned by a user.”

You get the headlines owned by a user in one go, which is the base for a digest or an archive in another tool.

When to use it
build a recap of every headline a person has shared, before a review.
Watch out
a search returns zero, one or many bundles; the next module runs once per headline and each run costs an operation.
Traction Tools23

List Issues

Search

In Make“Gets a list issues.”

Pull the list of issues into Make to report on them, clean them up or copy them to a spreadsheet for analysis.

When to use it
an export of open topics is needed for a board pack or a retrospective.
Watch out
every issue becomes its own bundle, so a long list multiplies the operations the next modules consume.
Traction Tools24

List Measurables

Search

In Make“Gets a list of measurables.”

The full set of measurables comes back as separate bundles, letting a scenario loop over the scorecard metric by metric.

When to use it
sync every metric with a BI tool, or check which ones still miss a value.
Watch out
add a filter after it when you only need part of the scorecard, to save operations.
Traction Tools25

List Rocks

Search

In Make“Gets a list of rocks.”

Gather every rock in one search, the starting point for a progress report or a sync with your project tool.

When to use it
a leadership summary should show all priorities and their owners side by side.
Watch out
an empty result is valid: the scenario simply stops, which can look like a failure on the first test.
Traction Tools26

List To-Dos

Search

In Make“Gets a list of To-Dos.”

Collect to-dos in bulk to chase overdue items, build a reminder email or measure how much gets done.

When to use it
a follow-up flow needs every open to-do before it sends nudges to owners.
Watch out
combine it with Make's aggregator if you want one message instead of one per to-do.
Need help

Need help automating Traction Tools with Make?

A person reads every message.

FAQ

Questions about Traction Tools and Make

01Is the Traction Tools Make integration free?
Yes, Traction Tools is a standard app, so it works on the Make Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, runs of up to 5 minutes, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and count usage in operations per month. Your Traction Tools subscription is separate and is covered on the vendor's own pricing page.
02What do you need to connect Traction Tools to Make?
You need an active Bloom Growth account and an API key from your Traction Tools account, according to the Make documentation. In Make, add any Traction Tools module, click Create a connection, give the connection a name if you like, then paste the credentials or follow the on-screen instructions. The connection is made once and every Traction Tools module in your scenarios reuses it, so you do not repeat the step for each module.
03Do Traction Tools triggers in Make fire instantly?
No. Watch Headlines, Watch Issues and Watch To-Dos are all scheduled triggers: Make checks Traction Tools on the scenario's schedule and picks up what was created since the last check. A new scenario checks every 15 minutes by default, which is also the shortest interval on the Free plan; paid plans can go down to 1 minute. You change the rhythm with the clock icon on the first module of the scenario.
04What if a Traction Tools module is missing in Make?
Use Make an API Call. It calls any endpoint of the Traction Tools API with the connection you already set up, so you can reach objects or options that the 29 listed modules do not cover. You write the request yourself, which means reading the vendor's API documentation. The Make doc also warns that its Traction Tools page is AI-generated from the vendor's documentation, so verify important details with Traction Tools directly.
05Should you use Make or n8n for Traction Tools?
It depends on how you like to build. In Make, Traction Tools comes with 29 ready-made modules, three scheduled triggers and Make an API Call for the rest, all inside a visual editor with a Free plan to start. The same app often exists as an n8n node too. Compare the modules each tool offers for the objects you care about, such as rocks, scores or to-dos, and pick the one your team will keep maintaining.
Same platform

Other docs you might need on this stack.

Browse all integrations