Resources · Make integration

Amwork Make integrationAutomate Amwork with Make.

Can Make keep Amwork up to date while your team works in other tools? The Amwork Make integration offers 16 modules: 13 actions and 3 searches on cards, tasks and activities. This guide links your account and walks you through a first scenario.

Try the Amwork integration on MakeSee the 16 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Amwork Make integration do for your team?

The Amwork Make integration links your Amwork account to Make, a no-code tool where you build scenarios: chains of modules that run on a schedule or when another app calls Make. Here, each module creates, reads, updates or deletes an Amwork card, task or activity, or looks several of them up at once. Amwork has no trigger in Make, so a scenario always starts somewhere else.

Every new request gets its card. A contact form or a chat tool starts the scenario, Create a Card files the request in Amwork, and Create a Task adds the first follow-up right behind it. Nobody copies a name or an email by hand.

A history that stays in one place. When a call gets booked or a message goes out from another tool, Create an Activity writes it into Amwork. Your team reads the whole story in the CRM instead of hunting through three inboxes.

A task list you can trust. List Tasks returns tasks as separate bundles (a bundle is one item passed from a module to the next), then Update a Task or Delete a Task handles them one by one. Each module run on each bundle counts as one operation on your Make plan, which Make pricing explains in detail.

What Make won't do here: notice a change inside Amwork on its own, since the app has no trigger. The scenario runs on its schedule, every 15 minutes by default, or starts from another app. The Amwork documentation on Make also says it was generated with AI, so double-check anything important with Amwork. Weighing n8n as well? Read n8n vs Make. To learn the editor step by step, Make training is the place to start.

Connect

How do you connect your Amwork account to Make?

  1. 01

    Open the connection window

    In your scenario, add any Amwork module, Create a Card for instance, then click Create a connection. A connection is your Amwork account linked to Make once, then reused by every Amwork module you add later.

  2. 02

    Copy your API key and token

    In Amwork, go to Account Settings, open the API Access section and copy both the API key and the API token shown on screen. You need an active Amwork account to see them.

  3. 03

    Paste them into Make

    Back in Make, type a label in Connection name if you want one (it's optional), paste the two values and follow the on-screen instructions. Make can now work with your cards, tasks and activities.

First scenario

Your first scenario: turn each new request into an Amwork card and task

GoalWhen a new request lands in another app, Make creates an Amwork card and a follow-up task for it.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app where requests arrive, your form or inbox tool, and choose its trigger module.

  2. 02

    Add Create a Card

    Click the + on the right of that first module, search for Amwork, pick Create a Card and click Create a connection with your API key and token.

  3. 03

    Map the request details

    Fill the card fields by mapping data from the first module. That way each request gives a card with its own details, not a fixed text you typed once.

  4. 04

    Add the follow-up task

    Click the + again and add Create a Task. Map what the team needs from the earlier modules, so the task makes sense without opening the original request.

  5. 05

    Test with Run once

    Send a test request, click Run once and open the bundles each module received. Then look at the new card and task in Amwork before going further.

  6. 06

    Schedule and switch on

    Set the schedule on the first module (a new scenario runs every 15 minutes by default) and switch the scenario on. From now on, each request follows the same path.

Modules

What each Amwork module does

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

Amwork1

Create a Card

ActionIn the docs only

You get a fresh Amwork card built from data that arrived earlier in the scenario, so a lead or a request reaches your CRM without anyone retyping it.

When to use it
a request comes in through another app and deserves its own card on the spot.
Watch out
map each value from the previous module instead of typing it, or every card comes out identical.
Amwork2

Create a Task

ActionIn the docs only

This one turns a follow-up into an Amwork task the moment the scenario reaches it, so nobody has to remember to write it down after a call or a new deal.

When to use it
right after Create a Card, when a new record needs a first action from the team.
Watch out
the task text is whatever you map, so check its wording with Run once before switching on.
Amwork3

Create an Activity

ActionIn the docs only

Your Amwork history grows by one activity each time this module runs, fed by an event that happened in another tool rather than inside Amwork.

When to use it
a meeting booked or a message sent elsewhere should also show up in Amwork for the team.
Watch out
one bundle means one activity, so a module that sends ten items upstream creates ten entries.
Amwork4

Delete a Card

ActionIn the docs only

A card you no longer want disappears from Amwork, which keeps the CRM free of duplicates and leftover tests. Make can't bring it back once the run is done.

When to use it
a search earlier in the scenario spotted a duplicate card that should go.
Watch out
try the scenario with Run once on a test card before switching it on.
Amwork5

Delete a Task

ActionIn the docs only

Tasks that lost their reason to exist leave the list, so your team only sees work that still matters. Treat the removal as final: there is no undo from Make.

When to use it
the deal or request behind the task was cancelled in another tool.
Watch out
when this module follows List Tasks, it runs once per task returned, so check that list first.
Amwork6

Delete an Activity

ActionIn the docs only

Removing an activity cleans the history of an entry that was logged by mistake, for example by an early version of your scenario during testing.

When to use it
Search Activities found entries your team agreed should not stay in Amwork.
Watch out
the history loses that entry for good, so keep this module out of scenarios you are still testing on real data.
Amwork7

Get a Card

ActionIn the docs only

Here you read one Amwork card and hand its current content to the next modules as a single bundle, ready to map.

When to use it
the scenario already knows which card it's about and needs its latest details before updating it or telling someone.
Watch out
it reads the one card you point it to; to find cards you don't know yet, start with List Cards.
Amwork8

Get a Task

ActionIn the docs only

Pulling one task gives the rest of the scenario its up-to-date content, instead of the older copy another module passed along.

When to use it
before a reminder goes out by email or chat, to make sure the task still says what the reminder claims.
Watch out
point it at the task with data mapped from an earlier module, not a value typed by hand.
Amwork9

Get an Activity

ActionIn the docs only

With this module, a single Amwork activity comes back with its details, so later modules can copy it, quote it or decide what to do next.

When to use it
a report or a message to a colleague needs the exact content of one logged activity.
Watch out
it fetches one activity only; Search Activities is the module for looking through several.
Amwork10

List Cards

SearchIn the docs only

List Cards returns Amwork cards as separate bundles, zero, one or many, and every module after it runs once per card.

When to use it
a cleanup or an export has to go through a batch of cards in one pass.
Watch out
each card counts again in the modules that follow, so operations add up fast on a large CRM.
Amwork11

List Tasks

SearchIn the docs only

All the tasks this search brings back travel down the scenario one by one, which lets you review, update or remove them without opening Amwork.

When to use it
a scheduled scenario should go over open work and push each task to the next step.
Watch out
run it once and read the bundles to see what it returned before chaining Update a Task or Delete a Task.
Amwork12

Make an API Call

ActionIn the docs only

When none of the listed modules covers what you need, this one calls any endpoint of the Amwork API, with the connection you already set up.

When to use it
a feature exists in Amwork but has no ready module in Make.
Watch out
you describe the request yourself, so keep the Amwork API documentation open and test with Run once.
Amwork13

Search Activities

SearchIn the docs only

Looking back through logged activities becomes a module step: it returns the matching ones as bundles, possibly none, possibly several.

When to use it
before logging a new activity, to check whether the same event was already recorded.
Watch out
an empty result is a normal answer, not an error, so plan what the scenario does when nothing matches.
Amwork14

Update a Card

ActionIn the docs only

An existing card picks up new information from another tool, so what your team reads in Amwork matches what just happened elsewhere.

When to use it
a client changes details in a form or a billing app, and the card must follow.
Watch out
it edits a card that already exists; map which one from Get a Card or List Cards instead of guessing.
Amwork15

Update a Task

ActionIn the docs only

Progress made outside Amwork shows up on the task itself, without anyone going back to edit it by hand.

When to use it
the work behind a task got done in another tool, such as a signed document or a sent quote.
Watch out
after List Tasks, this module touches every task returned, so check that list with Run once before switching the scenario on.
Amwork16

Update an Activity

ActionIn the docs only

Correcting or completing a logged activity keeps the history accurate when the first version was written before all the facts were in.

When to use it
a meeting logged earlier now has an outcome that belongs with it.
Watch out
find the right activity first with Search Activities or Get an Activity, then map it into this module.
Need help

Need help automating Amwork with Make?

A person reads every message.

FAQ

Amwork and Make: frequent questions

01Is the Amwork Make integration free?
Yes. Amwork is a standard Make app, so it works from the Free plan. That plan gives you 2 active scenarios, at least 15 minutes between two scheduled runs, an execution time of 5 minutes at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute, allow unlimited active scenarios and 40 minutes of execution, with usage counted in credits each month. On the Amwork side, you need an active account with API access; its subscription is set by Amwork.
02What does it take to connect Amwork to Make?
An active Amwork account and its API credentials. In Amwork, open Account Settings, then the API Access section, and copy the API key and the API token shown there. In Make, add any Amwork module to a scenario, click Create a connection, optionally give it a name, paste the two values and follow the on-screen steps. The connection is then reused by all 16 Amwork modules, so you only do this once per account.
03Can an Amwork scenario start as soon as something changes in Amwork?
No, not from Amwork itself: the app has no trigger module in Make. You have two ways to start anyway. Open the scenario with another app's trigger, the form or tool where the event happens, and let the Amwork modules follow. Or start it on a Make schedule, every 15 minutes by default, with List Cards, List Tasks or Search Activities as the first Amwork step to pick up what needs attention. On the Free plan, 15 minutes is also the shortest interval between two runs.
04What if the Amwork module you need is missing in Make?
Use Make an API Call. It reaches any endpoint of the Amwork API with the same connection as the other modules, so you are not limited to the 16 listed ones. You write the request yourself, which means reading the Amwork API documentation first and testing with Run once. Keep in mind that the Amwork page in the Make documentation states it was generated with AI and may contain mistakes, so confirm important details directly with Amwork before relying on them.
05Make or n8n for Amwork?
It depends on what your team needs to automate. In Make, Amwork comes with 16 ready modules on cards, tasks and activities, plus Make an API Call for anything else, and you build a scenario by clicking modules together in the editor. On the n8n side, check whether an Amwork node exists and what it covers before planning around it, since this page does not describe it. List the cards, tasks and activities you want to automate, then pick the tool that covers them with the least custom work.
Same platform

Other docs you might need on this stack.

Browse all integrations