Resources · Make integration

Pivotal Tracker Make integrationAutomate Pivotal Tracker with Make.

What if new stories and projects in Pivotal Tracker set off the rest of your work on their own? The Pivotal Tracker Make integration gives you 14 modules: 3 triggers, 9 actions and 2 searches. This guide shows product teams how to connect the account and build a first scenario.

Try the Pivotal Tracker integration on MakeSee the 14 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Pivotal Tracker Make integration automate?

The Pivotal Tracker Make integration links your Tracker account to Make, a no-code tool where you build a scenario: an automation made of modules, each module being one brick such as a trigger, an action or a search. Tracker can start a scenario when a story, a project or an activity appears, and Make can then create, update, read or delete projects and stories for you.

Every new project starts with its setup story. Watch Projects spots the project, then Create a Story drops a first story into it, so nobody forgets the kickoff checklist.

A team channel that follows the project. Watch Activities is an instant trigger: Tracker calls Make as soon as something happens in a project, and the next module can post that change wherever your team reads it.

Stories that stay in sync with another tool. Watch Stories picks up each new story; Update a Story or Get a Story then keep a spreadsheet or a support tool aligned. To see how other teams wire their tools, the Airtable Make integration is a good companion read.

What the listed modules do not cover, such as a Tracker feature without its own module, goes through Make an API Call, which reuses the same connection. The documentation gives no numbered limit for this app. If you also look at n8n, the n8n vs Make page lays out the differences, and the Make review covers the tool itself.

Connect

How do you connect Pivotal Tracker to Make?

  1. 01

    Add a Pivotal Tracker module

    In a scenario, add any Pivotal Tracker module, then click Create a connection. A connection is your Tracker account linked to Make once; every other Tracker module of your scenarios reuses it.

  2. 02

    Name the connection if you like

    Naming is optional, but a clear label such as the team or workspace helps later, when several people or several accounts share the same Make organization and you need to pick the right one.

  3. 03

    Authorize Make and save

    Follow what Tracker shows you: either approve Make on the Tracker page, or paste the key that Tracker gives you. Then click Save, and the module fields open, ready to fill.

First scenario

Your first scenario with Pivotal Tracker

GoalWhen a new project is created in Pivotal Tracker, Make adds a starter story to it.

  1. 01

    Create the scenario

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

  2. 02

    Place Watch Projects

    Search for Pivotal Tracker, pick Watch Projects and link your account with Create a connection. This trigger will look for projects created since the last check.

  3. 03

    Add Create a Story

    Click the + on the right of the trigger, choose Create a Story, then map the project coming from Watch Projects so the story lands in the right place.

  4. 04

    Test with Run once

    Create a test project in Tracker, then click Run once. Open each module to read the bundle it received: one bundle is one item, here one project.

  5. 05

    Schedule and switch it on

    On the first module, set the schedule (every 15 minutes by default, 15 minutes at the shortest on the Free plan), then turn the scenario on.

Triggers

Pivotal Tracker triggers in Make

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

Pivotal Tracker1Watch Activities

Watch Activities

Instant trigger

In Make“Triggers when any new activity happens within a project.”

Hears about any new activity inside a project, so your scenario reacts to what the team does in Tracker instead of waiting for someone to report it. It is the broadest of the three triggers.

How it fires
instant, Tracker calls Make through a webhook as soon as the activity happens. No schedule to set.
When to use it
you want a change in a project to show up in another tool right away, for example a message to the team.
Watch out
every activity starts a run, and each module that runs counts as an operation on your plan, so add a filter if you only care about some changes.
Pivotal Tracker2Watch Projects

Watch Projects

Scheduled trigger

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

Spots each project newly created in your account and hands it to the next module as a bundle. It is the natural starting point when a new project should set off setup work elsewhere.

How it fires
scheduled, Make checks Tracker on the scenario's schedule, every 15 minutes by default and 1 minute at best on paid plans.
When to use it
a fresh project needs its starter story, a shared folder or a line in a portfolio sheet.
Watch out
it only reports new projects; changes to an existing one will not start the scenario.
Pivotal Tracker3Watch Stories

Watch Stories

Scheduled trigger

In Make“Triggers when a new story is added in a project.”

Picks up each story added to a project, which lets another tool learn about new work without anyone copying it by hand. You choose the project it looks at when you fill the module.

How it fires
scheduled, Make asks Tracker for new stories on the scenario's schedule, so a story appears in the next run, not the instant it is written.
When to use it
new stories should reach a spreadsheet, a support desk or a team channel.
Watch out
edits to older stories are not caught here; Watch Activities hears those.
Modules

What Make can do in Pivotal Tracker

Pivotal Tracker gives you 11 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Pivotal Tracker1

Create a Project

Action

In Make“Creates a new project.”

Opens a brand new project in Tracker from your scenario, so a signed deal or a new client in another app gets its workspace without anyone setting it up by hand.

When to use it
a won opportunity in your CRM should turn into a Tracker project for the delivery team.
Watch out
every bundle the trigger sends creates one project, so test with Run once and add a filter before it.
Pivotal Tracker2

Create a Story

Action

In Make“Creates a new story in a project.”

Adds a story to the project you pick, turning a request that arrives somewhere else into planned work in the backlog. It is the module most scenarios end on.

When to use it
a bug report from a form, a support ticket or a new project should become a story the team can estimate.
Watch out
map the project from an earlier module or choose it in the list, or the story lands in the wrong backlog.
Pivotal Tracker3

Delete a Project

Action

In Make“Deletes a project.”

Removes a whole project from Tracker when your scenario decides it is no longer needed, which keeps the account tidy after an engagement closes.

When to use it
a test or temporary project was created by another scenario and must go away once the job is done.
Watch out
treat this as final and point it at a throwaway project during tests, never at a live one.
Pivotal Tracker4

Delete a Story

Action

In Make“Deletes a story.”

Takes one story out of a project, useful when a request is cancelled at the source and the backlog should reflect it without a manual cleanup.

When to use it
a ticket closed as a duplicate in your support tool should also disappear from Tracker.
Watch out
feed it the exact story from an earlier module, and add a filter before it so only the stories you mean are removed.
Pivotal Tracker5

Get a Project

Action

In Make“Gets the information of a project.”

Reads the details of one project so later modules can use them, for instance to add the project's information to a message or a report.

When to use it
a trigger gives you a project reference and you need the full record before writing it anywhere else.
Watch out
it returns a single project; to go through all of them, List Projects is the right module.
Pivotal Tracker6

Get a Story

Action

In Make“Gets the information of a story.”

Fetches the full information of one story, so the next step works with the whole story, not just the reference you started from.

When to use it
before copying a story into a support tool or a sheet, you want everything Tracker knows about it.
Watch out
it needs to know which story to read, so map it from a trigger or from List Stories.
Pivotal Tracker7

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Sends your own request to the Pivotal Tracker API with the connection you already set up, which lets you reach any endpoint the ready-made modules leave out.

When to use it
you need a Tracker feature that has no module of its own on this page.
Watch out
you write the request yourself, so keep the Tracker API reference open and test it with Run once before switching the scenario on.
Pivotal Tracker8

Update a Project

Action

In Make“Updates the settings of a project.”

Changes the settings of an existing project from your scenario, so a decision recorded in another tool is reflected in Tracker without someone editing it by hand.

When to use it
a project's status or details change in your CRM or planning sheet and Tracker should follow.
Watch out
only fill the settings you want to change and check the result on a test project first.
Pivotal Tracker9

Update a Story

Action

In Make“Updates the parameters of a story.”

Edits an existing story, which keeps Tracker aligned when the same piece of work moves forward in another app such as a help desk.

When to use it
a customer ticket changes state and the linked story should show it too.
Watch out
if Watch Activities starts this scenario, the update itself creates a new activity, so filter out your own changes to avoid a scenario that restarts itself.
Pivotal Tracker10

List Projects

Search

In Make“Retrieves a list of all your active projects.”

Returns all your active projects, one bundle per project, which is handy for building an overview or looping through every project in one run.

When to use it
you want a portfolio sheet that lists each active project with its details.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per project, which multiplies operations.
Pivotal Tracker11

List Stories

Search

In Make“Retrieves a list of the stories of a project.”

Brings back the stories of one project as separate bundles, so you can copy, count or review them in the modules that follow.

When to use it
a backlog export to a spreadsheet, or a check that finds stories needing attention in a given project.
Watch out
the project comes first; if it has many stories, add a filter so the next modules only handle the ones you need.
Need help

Need help automating Pivotal Tracker with Make?

A person reads every message.

FAQ

Pivotal Tracker and Make: common questions

01Is the Pivotal Tracker Make integration free?
Yes, Pivotal Tracker is a standard app in Make, so it works from the Free plan. That plan gives you 2 active scenarios, runs at most every 15 minutes, stops a run after 5 minutes and handles files up to 5 MB, with 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 allow 40 minutes per run. Usage is counted in operations each month, one per module run on one bundle. Any Tracker subscription is separate and not covered here.
02What do you need to connect Pivotal Tracker to Make?
A Pivotal Tracker account and a Make account are enough. The Make documentation for this app names no prerequisite and gives no specific connection steps, so the generic flow applies: add a Tracker module, click Create a connection, optionally name it, authorize Make on the Tracker page or paste the key Tracker provides, then click Save. The connection is created once and every Tracker module in your scenarios reuses it, so you will not repeat these steps for each new scenario you build.
03Does the Pivotal Tracker trigger in Make fire in real time?
It depends on the trigger. Watch Activities is instant: Tracker calls Make through a webhook as soon as an activity happens in a project, so the scenario starts right away. Watch Projects and Watch Stories are scheduled: Make asks Tracker for new items on the scenario's schedule, every 15 minutes by default, and never more often than every 15 minutes on the Free plan or every minute on paid plans. Pick Watch Activities when speed matters, and the other two when a short delay is fine.
04What if a Pivotal Tracker module is missing in Make?
Use Make an API Call. It sends any request to the Pivotal Tracker API with the connection you already created, so a feature without its own module is still within reach. You write the request yourself, which asks for a look at the Tracker API reference. The Make documentation lists no numbered limit for this app, so none applies from that side. Test the call with Run once and read the bundle it returns before you switch the scenario on.
05Make or n8n for Pivotal Tracker?
It depends on the tool your team already uses and on what you need to automate. On the Make side, Pivotal Tracker comes with 14 modules: 3 triggers, 9 actions and 2 searches, plus Make an API Call for anything else. Many apps also have an n8n node, so check that the features you need exist there before deciding. Neither tool is ranked here; the n8n vs Make comparison on this site lays out the differences in detail if you want to weigh them side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations