Resources · Make integration

AgilePlace Make integrationAutomate AgilePlace with Make.

Can Make keep your AgilePlace boards moving on their own? The AgilePlace Make integration offers 32 modules for cards, tasks and comments. This guide is for teams new to Make: connect the account, build a first scenario, then pick the right module.

Try the AgilePlace integration on MakeSee the 32 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the AgilePlace Make integration do?

The AgilePlace Make integration links your AgilePlace boards to Make, a tool where you build scenarios: automations made of modules, each module being one step such as a trigger, an action or a search. You get 32 modules, with 4 triggers that watch cards, 21 actions and 7 searches, so cards, tasks and comments travel between AgilePlace and your other apps without code.

Intake that sorts itself. With Watch New Card in a Board, each request card becomes a bundle, the single item Make passes from one module to the next, and Assign a User puts a name on it straight away.

Handoffs nobody forgets. Watch Existing Card Moved on a Board spots a card changing position; Create a Comment then records the handoff on the card, and Create a Task adds the next step the new owner has to tick off.

Reporting from live boards. Search Cards or Tasks and List Card Activity pull cards and their recent events into Make, so a spreadsheet or a chat app can summarize them for people who never open AgilePlace.

What Make does not do here: every trigger is scheduled, so nothing fires instantly, and Make itself flags its AgilePlace documentation as limited, which means fewer ready answers when a module surprises you. The Make troubleshooting guide helps in that case, and Make training covers the editor from the ground up. AgilePlace may also be available in n8n; the n8n vs Make comparison lays out how to choose.

Connect

How do you connect AgilePlace to Make?

  1. 01

    Add an AgilePlace module

    In a new scenario, click the big +, type AgilePlace and pick any module, for instance Search Boards. A connection is your AgilePlace account linked to Make once, then reused by every AgilePlace module. Click Create a connection.

  2. 02

    Name it and authorize Make

    Give the connection a name you will recognize later, such as the workspace it belongs to; this part is optional. Then do what the window asks: either authorize Make on the AgilePlace page that opens, or paste the key AgilePlace gives you.

  3. 03

    Save and check it works

    Click Save. Back in the module, start filling it in: once the connection works, Make lists what it can read from AgilePlace, such as your boards. An empty list means the wrong account was authorized.

First scenario

Your first scenario: a task on every new card in a lane

GoalWhen a new card lands in a chosen AgilePlace lane, Make adds a task to that card.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + in the middle of the editor. This first module is the one that starts every run.

  2. 02

    Add the trigger

    Search for AgilePlace, choose Watch New Card in a Lane and select your connection, or click Create a connection if this is your first AgilePlace module.

  3. 03

    Pick the lane to watch

    Fill in the trigger by choosing the lane that matters, for example the one where new client work arrives. Make lists what it can read, so nothing has to be typed from memory.

  4. 04

    Add Create a Task

    Click the + on the right of the trigger, add Create a Task and map the card coming from the trigger, so the task lands on the card that just arrived and not on a fixed one.

  5. 05

    Test with Run once

    Create a test card in the lane, click Run once and open the bundles: the trigger should show your card, and Create a Task the task it added.

  6. 06

    Schedule and switch on

    On the first module, keep the default schedule of every 15 minutes or change it (1 minute at the shortest on a paid plan), then switch the scenario on.

Triggers

Which AgilePlace triggers start a scenario?

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

AgilePlace1Watch Existing Card Moved on a Board

Watch Existing Card Moved on a Board

Scheduled trigger

In Make“Triggers when an existing card moved on a board.”

Starts your scenario when a card that already exists changes position on the board you pick, so a move on the board can set off follow-up work without anyone copying it by hand. Each moved card reaches the next module as one bundle.

How it fires
scheduled. Make checks AgilePlace on the scenario's schedule, every 15 minutes by default, and hands over the moves it finds.
When to use it
a card reaching the review lane of a delivery board should notify the reviewer or log the handoff in a sheet.
Watch out
it follows existing cards only; a card that is brand new belongs to Watch New Card in a Board.
AgilePlace2Watch Existing Card Updated on Board

Watch Existing Card Updated on Board

Scheduled trigger

In Make“Triggers when an existing card is updates on board.”

Reacts when someone edits an existing card on a chosen board, which lets a change made in AgilePlace spread to the tools around it instead of staying on the card.

How it fires
scheduled. Make checks AgilePlace on the scenario's schedule, so an edit is picked up at the next check rather than the second it happens.
When to use it
on a support board, where a card's details change and the matching customer record in your CRM has to stay in step.
Watch out
if your scenario itself updates cards with Update a Card, those edits can wake this trigger again; a filter stops the loop.
AgilePlace3Watch New Card in a Board

Watch New Card in a Board

Scheduled trigger

In Make“Triggers when a new card is created in a specific board.”

Hands you every card created on one specific board, which is the natural entry point for request intake: each card becomes a bundle the rest of the scenario can route, assign or copy.

How it fires
scheduled. Make checks AgilePlace on the scenario's schedule and collects the cards created since it last looked.
When to use it
an intake board where requests arrive as cards and each one needs an owner, an acknowledgment or a row in a tracking sheet.
Watch out
every new card is its own bundle, and every module after the trigger spends one operation per bundle, which adds up on a busy board.
AgilePlace4Watch New Card in a Lane

Watch New Card in a Lane

Scheduled trigger

In Make“Triggers when a new card is created in a specific lane.”

Narrows the watch to a single lane, so your scenario only wakes for cards created exactly where a specific kind of work begins, not for the whole board.

How it fires
scheduled. Make checks AgilePlace on the scenario's schedule and passes on the new cards of that lane.
When to use it
a lane reserved for urgent fixes, where each new card should alert the person on call or get its standard tasks.
Watch out
the module speaks of cards created in the lane; for a card that arrives there by being moved, check its behavior with Run once before relying on it.
Modules

What can the AgilePlace modules do?

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

AgilePlace1

Assign a User

Action

In Make“Assigns a user to specific cards.”

Puts one of your AgilePlace users on the cards you choose, so each card leaves the scenario with an owner instead of waiting for someone to claim it.

When to use it
right after Watch New Card in a Board, to hand incoming requests to whoever covers that type of work.
Watch out
map the card from the trigger rather than a fixed one, or every run will reassign the same card.
AgilePlace2

Connect a Card

Action

In Make“Connects a card to a child or parent cards.”

Links a card to parent or child cards, so a large piece of work and the smaller cards that make it up show their relationship on the board.

When to use it
when a scenario splits one request into several cards and they should stay tied to the original.
Watch out
both cards must exist before they can be linked, so place this module after the ones that create them.
AgilePlace3

Create a Card

Action

In Make“Creates a new card on the board.”

Adds a fresh card to a board, filled with data from earlier modules, so a form reply or an email turns into work the whole team can see.

When to use it
for requests that start outside AgilePlace, such as a helpdesk ticket or a signed order in a CRM.
Watch out
each run creates a new card; test with Run once on a test board before switching the scenario on.
AgilePlace4

Create a Card Type

Action

In Make“Creates a card type.”

Creates a new card type, the category that tells your team at a glance what kind of work a card holds.

When to use it
when you set up several boards and each one needs the same set of types, without clicking them in one by one.
Watch out
a scenario that runs again will create the type again; check first with List Card Types whether it already exists.
AgilePlace5

Create a Comment

Action

In Make“Creates a new comment.”

Posts a comment on a card, which keeps the story of a piece of work in one place even when part of it happens in other tools.

When to use it
to note on the card that an invoice went out, a customer replied or a deployment finished somewhere else.
Watch out
one comment is written per bundle, so a search upstream that returns ten cards means ten comments.
AgilePlace6

Create a Task

Action

In Make“Creates a new task in the specified card.”

Adds a task inside the card you point to, turning a broad card into concrete steps the assignee can tick off one after the other.

When to use it
when every new card of a given kind needs the same checks, such as a review followed by a sign-off.
Watch out
the task lives in the card you map; take that card from the trigger or a search so it lands in the right place.
AgilePlace7

Create Custom Fields

Action

In Make“Creates custom fields.”

Sets up custom fields, the extra data slots your cards carry beyond the standard details, without going through the board settings by hand.

When to use it
when several boards must share the same custom fields because reports compare them side by side.
Watch out
Make's documentation for this app is limited, so run the module once on a test board to see exactly what it creates.
AgilePlace8

Delete a Card

Action

In Make“Deletes a specific card.”

Removes one specific card from AgilePlace, which clears out duplicates or test cards that a scenario or a person created by mistake.

When to use it
after a filter confirms the card is a duplicate or was cancelled in the system it came from.
Watch out
the scenario cannot bring a deleted card back; put a filter in front of this module and test with Run once.
AgilePlace9

Delete a Card Connections

Action

In Make“Deletes one or more parent or child connection from a card.”

Cuts one or more parent or child links from a card while leaving the cards themselves exactly where they are.

When to use it
when work gets reorganized and a card should no longer count under its former parent.
Watch out
it removes links, not cards; if the goal is to remove the card itself, Delete a Card is the module to pick.
AgilePlace10

Delete a Card Type

Action

In Make“Removes a specific card type.”

Retires a card type nobody uses anymore, which keeps the type list short and clear for the people filling in cards.

When to use it
during a cleanup of boards a scenario set up, once the old type has been replaced by a new one.
Watch out
Make's documentation does not say what happens to cards still using that type; try it on a test board before a live one.
AgilePlace11

Delete Custom Fields

Action

In Make“Removes custom fields.”

Removes custom fields from a board once they no longer serve any purpose, so cards stop showing slots nobody fills.

When to use it
after a process change, when a field left over from the old way of working clutters every card.
Watch out
treat the deletion as final and keep a copy of what those fields held first, for instance with Get a Card.
AgilePlace12

Get a Card

Action

In Make“Retrieves a card details.”

Fetches the details of one card, so later modules can reuse them in an email, a spreadsheet row or a record in another app.

When to use it
when you already know which card you need, for instance from a reference stored in another tool, and the next step needs its content.
Watch out
it reads a single card; to work on several, Search Cards or Tasks returns one bundle per card.
AgilePlace13

Get a Card Type

Action

In Make“Retrieves a specific card type.”

Reads one card type and returns its details, handy when a scenario must reuse or copy a type exactly as it is set up today.

When to use it
before Update a Card Type, to see the current setup, or to copy a type to another board with Create a Card Type.
Watch out
you need to know which type to read; List Card Types finds it when all you have is the board.
AgilePlace14

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the AgilePlace API from your scenario, reusing the same connection, so a gap in the listed modules does not block the build.

When to use it
when the action you need has no dedicated module among the 21 actions and 7 searches.
Watch out
you write the request yourself, so keep the AgilePlace API documentation open and read the returned bundle after Run once.
AgilePlace15

Move a Card to Another Board

Action

In Make“Moves selected cards to the default lane of the specified board.”

Sends selected cards to another board, where they land in that board's default lane, which is how work passes from one team to the next.

When to use it
when a card finished by the design team should show up on the development board without anyone moving it.
Watch out
the card always arrives in the default lane of the target board; add Move a Card to Another Lane after it if it belongs elsewhere.
AgilePlace16

Move a Card to Another Lane

Action

In Make“Moves selected cards to the specified lane of the same board.”

Shifts selected cards to another lane of the same board, so the board reflects progress that happened in other tools.

When to use it
when a payment is received or a pull request is merged and the card should step forward on its own.
Watch out
it stays inside one board; for a jump between boards, Move a Card to Another Board is the right module.
AgilePlace17

Move a Task to a Lane

Action

In Make“Moves a task into the 'ToDo', 'Doing' or 'Done' lane.”

Changes where a task sits inside its card, choosing between the ToDo, Doing and Done lanes, so progress on small steps shows up without opening AgilePlace.

When to use it
when the step a task describes gets done in another app, like a contract signed or a quote sent.
Watch out
only those three lanes are available; to move a whole card, use Move a Card to Another Lane.
AgilePlace18

Unassign a User

Action

In Make“Unassigns a user from specific cards.”

Takes a user off specific cards, which keeps ownership accurate when someone leaves a project or hands work over.

When to use it
paired with Assign a User, to pass a card from one person to another within the same run.
Watch out
the module acts on every card it receives; after a search, filter the bundles first so only the intended cards lose their owner.
AgilePlace19

Update a Card

Action

In Make“Updates an existing card.”

Edits an existing card with fresh data, so what the board shows matches what changed in your CRM, helpdesk or spreadsheet.

When to use it
when a customer's details change in the source tool and the card tracking their project has to follow.
Watch out
if Watch Existing Card Updated on Board runs on the same board, your own update can start another run; a filter breaks the loop.
AgilePlace20

Update a Card Type

Action

In Make“Updates a specific card type.”

Adjusts a card type already in use, so a change to a category reaches the board without anyone editing it by hand.

When to use it
when the same type exists on several boards and all of them must stay identical.
Watch out
read the type first with Get a Card Type so you change only what you actually mean to change.
AgilePlace21

Update a Custom Field

Action

In Make“Updates an existing custom field.”

Changes an existing custom field, which lets the extra data your cards carry evolve along with the way your team works.

When to use it
when a process update means a custom field shared by several boards must change in one go.
Watch out
run List Custom Fields first to target the right field; a wrong pick alters a field other people rely on.
AgilePlace22

List Card Activity

Search

In Make“Retrieves a list of recent events for a card.”

Returns the recent events of a card, one bundle per event, which gives a scenario the card's history without anyone scrolling through it.

When to use it
to keep an audit trail in a sheet, or to check what happened on a card before a scenario acts on it.
Watch out
as a search, it can return zero, one or many bundles, and each module after it runs once per bundle.
AgilePlace23

List Card's Tasks

Search

In Make“Lists all tasks of the specified card.”

Lists every task inside a given card, so a scenario can tell how far a piece of work has come.

When to use it
before closing a card, to confirm its tasks are done, or to copy them into a status report.
Watch out
each task comes out as its own bundle; add an aggregator, the Make tool that groups bundles into one, if the next module expects a single list.
AgilePlace24

List Card Types

Search

In Make“Searches for a list of card types for a specific board.”

Gives back the card types set up on one board, which helps a scenario choose the right type instead of relying on a value typed by hand.

When to use it
before Create a Card when the type depends on the request, or before copying types from one board to another.
Watch out
it covers one board per search; start from Search Boards when several boards are involved.
AgilePlace25

List Custom Fields

Search

In Make“Searches custom fields.”

Surfaces the custom fields that exist, so a scenario can check the setup before writing to them or removing them.

When to use it
ahead of Update a Custom Field or Delete Custom Fields, to be sure you target the right one.
Watch out
the documentation says little about how this search filters; run it once and read the bundles before building on them.
AgilePlace26

Search Boards

Search

In Make“Searches for the boards.”

Finds the boards your connection can see, the starting point for any scenario that works across more than one board.

When to use it
to run the same report or tidy-up on every board, or to locate a board before creating cards on it.
Watch out
each board is a separate bundle, so the modules after it run once per board and spend operations each time.
AgilePlace27

Search Card Comments

Search

In Make“Searches for card comments.”

Pulls the comments left on cards, so discussions held in AgilePlace can reach a report, a chat channel or a customer update.

When to use it
when a manager wants the latest remarks gathered in one place without opening each card.
Watch out
comments your own scenario posted with Create a Comment come back too; filter them out if they would repeat.
AgilePlace28

Search Cards or Tasks

Search

In Make“Searches for the cards.”

Looks up cards and returns each match as a bundle, so the next modules can act on a whole batch instead of one card at a time.

When to use it
to find the card behind a request from another app before updating it, rather than creating a duplicate.
Watch out
a search can return zero, one or several cards; plan what happens when nothing matches, such as creating the card instead.
Need help

Need help automating AgilePlace with Make?

A person reads every message.

FAQ

Common questions about AgilePlace and Make

01Is the AgilePlace Make integration free?
Yes. AgilePlace is a standard app in Make, so its modules work on the Free plan. That plan comes with limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Each module run on one bundle counts as an operation. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution, with usage counted in credits per month. Your AgilePlace subscription is a separate matter.
02What do you need to connect AgilePlace to Make?
An AgilePlace account and a Make account; Make's documentation lists no other prerequisite. Add any AgilePlace module, click Create a connection, name it if you like, then authorize Make on the AgilePlace page that opens or paste the key AgilePlace provides, and click Save. The connection is stored once and reused by all 32 modules. Because Make flags its AgilePlace documentation as limited, the quickest check is a Run once on a small scenario right after saving, to confirm Make can read your boards.
03Do AgilePlace triggers in Make fire in real time?
No. All 4 AgilePlace triggers are scheduled and none is instant. Make asks AgilePlace for new, moved or edited cards at the rhythm set on the first module: every 15 minutes by default, 15 minutes at the shortest on the Free plan, and down to 1 minute on paid plans. A card created just after a check therefore waits for the next one. If a workflow needs a quicker reaction, a paid plan shortens the gap, but the trigger keeps its scheduled type.
04What if an AgilePlace module is missing in Make?
Use Make an API Call. It is one of the 32 AgilePlace modules and reuses the connection you already created, so any endpoint of the AgilePlace API can be called from the scenario without a new login. You write the request yourself, which means keeping the AgilePlace API documentation at hand. Since Make marks its own documentation for this app as limited, test each call with Run once and read the returned bundle before you switch the scenario on.
05Make or n8n for AgilePlace?
It depends on your criteria rather than on a winner. In Make, AgilePlace comes with 32 ready modules: 4 scheduled triggers on cards, 21 actions and 7 searches, plus Make an API Call for anything else, and a Free plan to start. n8n is another automation tool, and apps listed in Make often have a node there too, so check its catalog for AgilePlace first. Then compare what each covers for your boards, how you prefer to build, and which tool your team already uses.
Same platform

Other docs you might need on this stack.

Browse all integrations