Resources · Make integration

Elements.cloud Make integrationAutomate Elements.cloud with Make.

Stories that fill themselves in when something happens elsewhere in your stack. The Elements.cloud Make integration gives you 8 modules: 5 actions and 3 searches built around stories. This page shows how to link your account with an API token, then walks you through a first scenario, step by step.

Try the Elements.cloud integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Elements.cloud Make integration do for you?

The Elements.cloud Make integration lets Make create, read, update and delete stories in your Elements.cloud space, with no code. You build a scenario (the automation itself, a chain of modules) and each module (one brick of that chain) does one job on your stories, such as creating one or listing them.

Turn incoming requests into stories. A form, a ticket or a chat message lands in another app, and Create a Story writes the matching story in Elements.cloud. Nobody retypes the request, and the story exists the moment the scenario runs.

Keep a story in step with its source. When the source item changes, Get a Story reads the current version and Update a Story writes the change back. List Story Statuses helps you pick a valid status instead of guessing one.

Pull stories out for a report. List Stories hands every matching story to the next module, so you can send them to a spreadsheet or a message. List Story Custom Fields tells you which extra fields your space uses before you map them.

Two limits to know. The app has no trigger, so it cannot start a scenario by itself: another app's trigger or Make's schedule does that. And Make flags its own documentation for this app as AI-generated, so check important details against Elements.cloud. The Make troubleshooting guide helps when a run fails, and Make pricing explains how operations are counted. If you are also weighing n8n, the n8n vs Make comparison sets the two side by side.

Connect

How do you connect Elements.cloud to Make?

  1. 01

    Create an API token in Elements.cloud

    Open Space management, then the Developer tab and the API Tokens tab. Click Create API Token, give it a name and a description, tick the scopes your scenario needs, click Create and copy the token shown in the window.

  2. 02

    Add an Elements.cloud module

    In your Make scenario, add any Elements.cloud module and click Create a connection. A connection is your Elements.cloud account linked to Make once, then reused by every module of the app. The Connection name field is optional.

  3. 03

    Paste the token and save

    Paste the token you copied into the credentials Make asks for, or follow the instructions on screen, then save. Make now reads your space, and you can pick values from lists instead of typing them.

First scenario

Your first scenario with Elements.cloud and Make

GoalWhen a new request comes in through another app, Make creates a story for it in Elements.cloud.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. Pick the trigger of the app where your requests arrive, such as your form tool.

  2. 02

    Connect the source app

    Choose that trigger, click Create a connection and link the account. Fill its fields; once connected, Make shows the forms or folders it can read.

  3. 03

    Add Create a Story

    Click the + on the right of the first module, search for Elements.cloud and pick Create a Story. Use the connection you made with your API token.

  4. 04

    Map the request into the story

    Fill the story fields by mapping data from the first module: the request title into the story name, for instance. Each bundle (one item passed along, here one request) becomes one story.

  5. 05

    Test with Run once

    Click Run once, send a test request, then open each module's bundles to see what it received. Check in Elements.cloud that the story looks the way you want.

  6. 06

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default) and switch the scenario on. From then on, each run turns new requests into stories.

Modules

What each Elements.cloud module does

Elements.cloud gives you 8 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Elements.cloud1

Create a Story

ActionIn the docs only

Adds a new story to your Elements.cloud space from data that arrives in the scenario, so requests from other tools stop being copied by hand.

When to use it
a form or ticket in another app should become a story as soon as the scenario picks it up.
Watch out
every bundle that reaches this module creates one story, so a test run with many items fills your space with many stories.
Elements.cloud2

Delete a Story

ActionIn the docs only

Removes one story from your space, which keeps it clean when the item it tracked is dropped in its source tool.

When to use it
a request is cancelled upstream and its story no longer has a reason to exist.
Watch out
treat a deletion as final, since no module brings a story back. Put a filter before this module and try it on a throwaway story first.
Elements.cloud3

Get a Story

ActionIn the docs only

Reads one story you already know and hands its current content to the next modules, so they work on fresh data rather than an old copy.

When to use it
before Update a Story, to compare what the story holds now with what the source app sends.
Watch out
it works on one precise story; if you do not know which one yet, start from List Stories.
Elements.cloud4

List Stories

SearchIn the docs only

Returns the stories of your space as separate bundles, one per story, ready to be filtered, counted or sent to another app.

When to use it
building a report of stories in a spreadsheet, or finding the story that matches a record elsewhere.
Watch out
as a search, it can return zero, one or many stories, and every following module then runs once per story, which spends operations.
Elements.cloud5

List Story Custom Fields

SearchIn the docs only

Shows the custom fields that stories use in your space, so you map real fields instead of guessing their names.

When to use it
setting up Create a Story or Update a Story for the first time in a space where the team added its own fields.
Watch out
run it with Run once and read its bundles; it tells you what exists, it does not fill anything.
Elements.cloud6

List Story Statuses

SearchIn the docs only

Gives back the statuses a story can take in your space, which lets a scenario set a status that Elements.cloud will accept.

When to use it
a scenario moves stories forward when work progresses in another tool and needs the exact status value.
Watch out
it returns several bundles, one per status, so filter to the one you need before mapping it.
Elements.cloud7

Make an API Call

ActionIn the docs only

Calls any endpoint of the Elements.cloud API with the connection you already set up, for everything the seven other modules leave out.

When to use it
a task on something other than stories, or an option that no listed module offers.
Watch out
you need to read the Elements.cloud API documentation yourself, and your token only reaches what its scopes allow.
Elements.cloud8

Update a Story

ActionIn the docs only

Changes an existing story in place, so its content follows what happens in the tool where the work is really done.

When to use it
a ticket changes state in another app and its story should show the same progress.
Watch out
you must point it at one story; pair it with List Stories or Get a Story to find the right one first.
Need help

Need help automating Elements.cloud with Make?

A person reads every message.

FAQ

Elements.cloud and Make: common questions

01Is the Elements.cloud Make integration free?
Yes, on the Make side. Elements.cloud is a standard app, so it is available from the Free plan. That plan allows 2 active scenarios, runs scheduled scenarios at most every 15 minutes, and caps each run at 5 minutes. Paid plans lower the interval to 1 minute and remove the cap on active scenarios. On the Elements.cloud side, you need an enterprise space with the API capability, which depends on your Elements.cloud subscription, not on Make.
02What does the Elements.cloud Make integration need to connect?
You need an Elements.cloud enterprise space where the API capability is active, and a user with space admin or API token manager permissions. With that, create a token under Space management, in the Developer tab then API Tokens, choose the scopes your scenario needs, and copy it. In Make, click Create a connection on any Elements.cloud module and paste the token. The same connection then serves all 8 modules. A token without the right scope is the first thing to check when a module fails.
03Does the Elements.cloud Make integration react in real time?
No, it has no trigger at all, so it cannot start a scenario on its own. The scenario starts from another app's trigger, such as a new form entry, or from Make's schedule, which runs every 15 minutes by default. In that second case, begin with List Stories and let the following modules work on each story it returns. How fast a change shows up then depends on the trigger or schedule you choose.
04What if an Elements.cloud module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Elements.cloud API with the connection you already have, so you are not limited to the seven story modules. You will need the Elements.cloud API documentation to build the request, and your token must include the matching scopes. Make also marks its own documentation for this app as AI-generated, so confirm important details with Elements.cloud before relying on them. Start with a small request and test it with Run once.
05Make or n8n for Elements.cloud: which one fits?
It depends on the tool your team already runs. On Make, the app gives you 8 modules focused on stories, plus Make an API Call for the rest, and a visual editor where you test with Run once. The same app often has an n8n node too, so check what the node covers before you choose. Compare the modules each side offers for your case rather than the tool's reputation.
Same platform

Other docs you might need on this stack.

Browse all integrations