Resources · Make integration

atSpoke Make integrationAutomate atSpoke with Make.

What if every new atSpoke request reached the right place without anyone copying it? The atSpoke Make integration gives you 17 modules, 3 of them instant triggers. This page shows support and IT teams how to connect the account and build a first working scenario.

Try the atSpoke integration on MakeSee the 17 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the atSpoke Make integration let you automate?

The atSpoke Make integration links your atSpoke account to Make, a visual tool where you build a scenario (the automation itself, a chain of modules). atSpoke then reacts to other apps, and other apps react to atSpoke, without a line of code. It covers requests, resources and users.

Requests that travel on their own. Watch New Requests starts a scenario the moment someone opens a request, so the details can land in the tool your team already reads. When a form in another app collects a problem, Create a Request turns it into an atSpoke request instead of an email nobody follows up.

Status changes that others hear about. Watch Requests Updated fires when a request changes. Pair it with a module of another app to warn a manager, or with Get a Request to read the full record before deciding what happens next.

A cleaner user base. Get a User finds a person by email address or ID, and Update a User corrects the record. Useful when an HR tool holds the reference data and atSpoke should follow it.

The documentation lists no numeric limit for atSpoke, and the modules cover requests, resources and users only. For anything else in the atSpoke API, Make an API Call reuses the same connection. If you are still weighing tools, read the n8n vs Make comparison and the Make pricing guide; to learn the editor properly, the Make training starts from zero.

Connect

How do you connect atSpoke to Make?

  1. 01

    Add an atSpoke module

    In a new scenario, click the + and search for atSpoke, then pick any module, for example Watch New Requests. In the module window, click Create a connection. A connection is your atSpoke account linked to Make once, then reused by every atSpoke module.

  2. 02

    Name the connection

    Make offers a default name, and you can change it. Pick something that tells you which account it is, such as the workspace of your support team, so you can spot it later when several connections sit in the same list.

  3. 03

    Authorize, then save

    Authorize Make on the atSpoke page that opens, or paste the key atSpoke gives you, depending on what the window asks for. Click Save. The documentation lists no prerequisite, so a working atSpoke account is the starting point.

First scenario

Your first scenario with atSpoke

GoalWhen another app collects a support issue, for example through a form, Make opens it as a request in atSpoke.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the canvas. That first spot holds the module that starts everything, here the app where people report problems.

  2. 02

    Pick the starting app

    Choose the module of the tool that collects issues, a form app for instance, and connect it. Its bundles, one submitted item each, are what the scenario passes along to atSpoke.

  3. 03

    Add Create a Request

    Click the + on the right, search for atSpoke and pick Create a Request. Link your account with Create a connection, then map the answers from the first module into the request fields.

  4. 04

    Test with Run once

    Click Run once and send a test submission. Each module shows the bundle it received, so you can open atSpoke and check that the request looks the way your team expects.

  5. 05

    Schedule and switch on

    Set the schedule on the first module, every 15 minutes by default, then switch the scenario on. Each module run counts as one operation, the unit Make counts on your plan.

Triggers

What starts an atSpoke scenario

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

atSpoke1Watch New Requests

Watch New Requests

Instant trigger

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

Starts your scenario each time a request is created in atSpoke, so a new ticket can be copied, announced or routed without anyone watching the queue. Each request reaches the next modules as a bundle.

How it fires
instant, atSpoke calls Make through a webhook as soon as it happens, no polling schedule involved.
When to use it
when the team handling requests lives in another tool and needs to hear about each new one.
Watch out
it only sees creations. To catch a change on a request that already exists, switch to Watch Requests Updated instead.
atSpoke2Watch New Resources

Watch New Resources

Instant trigger

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

Reacts to every new resource added in atSpoke and hands it to the rest of the scenario. That way the content your team publishes there can be echoed elsewhere with no manual copy.

How it fires
instant, atSpoke notifies Make through a webhook as soon as the resource exists.
When to use it
when colleagues outside atSpoke should learn that a new resource is available, in a channel or a log they already follow.
Watch out
an edit to an existing resource does not start it, since this trigger listens for new ones only.
atSpoke3Watch Requests Updated

Watch Requests Updated

Instant trigger

In Make“Triggers when a request is updated.”

Follows the life of a request after its creation: each time a request is updated in atSpoke, your scenario runs with the updated record. This is how other tools stay in step with what happens to a ticket.

How it fires
instant, atSpoke sends a webhook to Make as soon as the update happens.
When to use it
to tell a requester's manager, or a tracking sheet, that a request moved.
Watch out
do not end this scenario with Update a Request on the same request, or each update can start the scenario again.
Modules

What atSpoke can do in a scenario

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

atSpoke1

Create a Request

Action

In Make“Creates a new atSpoke request.”

Opens a new request in atSpoke from data that comes from somewhere else, so issues reported outside atSpoke still end up in the queue your team works from.

When to use it
after a form submission or an email in another app, when the problem deserves a proper request rather than a forwarded message.
Watch out
map the fields from the previous module carefully, because each run creates one more request.
atSpoke2

Create a Resource

Action

In Make“Creates a new atSpoke resource.”

Adds a fresh resource to your atSpoke account from content produced in another app. Your reference material stays in one place even when it is written elsewhere.

When to use it
when a document validated in another tool should also exist as an atSpoke resource people can find.
Watch out
if the source can send the same item twice, check with List Resources first to avoid duplicates.
atSpoke3

Delete a Request

Action

In Make“Deletes a request.”

Removes a request from atSpoke. It keeps the queue free of test tickets or entries created by mistake, which otherwise clutter every report.

When to use it
at the end of a cleanup flow, after List Requests or Get a Request has confirmed which request goes.
Watch out
treat every deletion as final: run the scenario with Run once and read the bundle before switching it on.
atSpoke4

Delete a Resource

Action

In Make“Deletes a resource.”

Takes a resource out of atSpoke for good. Handy when outdated content would otherwise keep showing up for the people searching for answers.

When to use it
when the source of a resource is retired in another tool and the atSpoke copy should disappear with it.
Watch out
count on no way back; filter on the exact item instead of deleting whatever a search returns.
atSpoke5

Get a Request

Action

In Make“Gets a request.”

Reads one request in full, so later modules can decide based on its current state instead of guessing. It returns a single bundle for the request you point to.

When to use it
right after a trigger or a step that only gave you a reference to the request, and you need the whole record.
Watch out
you need to know which request you want; to browse several, List Requests is the better fit.
atSpoke6

Get a Resource

Action

In Make“Gets a resourse.”

Fetches one atSpoke resource and makes its content available to the next modules. Useful to reuse what is already written instead of retyping it in another app.

When to use it
after Watch New Resources, or whenever a scenario holds a resource reference and needs the details behind it.
Watch out
it works on one resource at a time; List Resources covers the cases where you do not know which one yet.
atSpoke7

Get a User

Action

In Make“Looks up a user by email address or ID.”

Looks up a single atSpoke user by email address or by ID. You get the person's record, ready to be mapped into a message, a sheet or another module.

When to use it
when another app only knows someone's email and the scenario needs the matching atSpoke user.
Watch out
check the case where nobody matches, for example with a filter, so the next modules do not run on empty data.
atSpoke8

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Calls any endpoint of the atSpoke API with the connection you already set up. It is the way out when the listed modules do not cover what you need.

When to use it
for an atSpoke action or object that no other atSpoke module handles.
Watch out
you write the request yourself from the atSpoke API documentation, so this module asks for more care than the others.
atSpoke9

Update a Request

Action

In Make“Updates a request.”

Changes an existing request in atSpoke, so progress made in another tool shows up where requesters look for news.

When to use it
when work tracked in a separate system moves forward and the matching atSpoke request should reflect it.
Watch out
placed after Watch Requests Updated on the same request, it can restart the scenario at each change; add a filter or use another trigger.
atSpoke10

Update a Resource

Action

In Make“Updates a resource.”

Edits a resource already stored in atSpoke. The version your colleagues read stays aligned with the source it comes from.

When to use it
when the original content is revised in another app and atSpoke should carry the new version instead of a second copy.
Watch out
identify the resource first, with Get a Resource or List Resources, so the change lands on the right one.
atSpoke11

Update a User

Action

In Make“Updates a user.”

Corrects or completes a user record in atSpoke using data held somewhere else, which spares someone from fixing profiles by hand.

When to use it
when an HR or directory tool is the reference and a change there should reach atSpoke too.
Watch out
find the user with Get a User before updating, otherwise the scenario has no reliable ID to work on.
atSpoke12

List Requests

Search

In Make“Returns a list of requests.”

Returns requests from atSpoke as a series of bundles, one per request. A good base for reports, exports or checks across the whole queue.

When to use it
when a scenario needs several requests at once, for example to copy them into a spreadsheet.
Watch out
a search can return zero, one or many items, and every following module runs once per bundle, which adds operations.
atSpoke13

List Resources

Search

In Make“Returns a list of resources.”

Brings back the resources of your atSpoke account, each one as its own bundle. It lets you review or copy the content without opening atSpoke.

When to use it
to check whether a resource already exists before Create a Resource, or to build an inventory in another tool.
Watch out
plan for an empty result, and remember each returned bundle triggers its own run of the modules that follow.
atSpoke14

List Users

Search

In Make“Returns a list of users.”

Pulls the users of your atSpoke account into the scenario, one bundle per person. You can then compare them with another directory or feed a sheet.

When to use it
when you need the whole user base rather than one person, for an audit or a sync.
Watch out
for a single person Get a User is lighter, since List Users makes every next module run once per user.
Need help

Need help automating atSpoke with Make?

A person reads every message.

FAQ

Questions about atSpoke and Make

01Is the atSpoke Make integration free?
Yes, atSpoke is a standard app in Make, so it works from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, 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 allow 40 minutes of execution. Usage is counted in operations each month. This page gives no price for atSpoke itself.
02What do you need to connect atSpoke to Make?
An atSpoke account you can sign in to is the starting point, since the documentation lists no other prerequisite. You add an atSpoke module, click Create a connection, give it a name if you want, authorize Make on the atSpoke page or paste the key atSpoke provides, then click Save. The connection is then reused by all 17 atSpoke modules. The documentation offers no official steps for this app, so these are the generic Make steps.
03Do atSpoke triggers in Make react in real time?
Yes. The 3 atSpoke triggers, Watch New Requests, Watch New Resources and Watch Requests Updated, are all instant: atSpoke calls Make through a webhook as soon as the event happens, instead of Make checking on a schedule. That means no polling interval to set for them. The Free plan limit of 15 minutes between scheduled runs concerns scheduled triggers, not these ones. In practice, the scenario starts the moment the request or resource changes in atSpoke.
04What if an atSpoke module is missing in Make?
It depends on what is missing. The 17 modules cover requests, resources and users, and the Make an API Call module reaches any endpoint of the atSpoke API with the same connection, so an action without its own module is usually still possible that way. The documentation lists no numeric limit for atSpoke. If the need concerns another tool entirely, add that app's module to the same scenario. Test such a call with Run once before switching the scenario on.
05Should you use Make or n8n with atSpoke?
It depends on the tool your team already works in. With Make, atSpoke offers 17 ready modules, 3 instant triggers and Make an API Call for the rest, on every plan from Free. The same app often has an n8n node too, so check that side before choosing. The comparison of the two tools, linked higher on this page, lays out the criteria without ranking one above the other. Pick the one where your team will maintain the scenario.
Same platform

Other docs you might need on this stack.

Browse all integrations