Resources · Make integration

Gravitec Make integrationAutomate Gravitec with Make.

Can a push notification go out on its own when something happens in another tool? The Gravitec Make integration gives you 2 action modules for exactly that. This guide shows marketers and site owners how to link the account and build a first working scenario.

Try the Gravitec integration on MakeSee the 2 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Gravitec Make integration automate?

The Gravitec Make integration lets a Make scenario send push notifications through your Gravitec account without anyone typing them. A scenario is the automation you build in Make: a chain of modules, and each module is one brick, such as a trigger or an action. Gravitec brings two action bricks, so another app or a schedule starts the chain.

Announce new content automatically. When your publishing tool reports a fresh article, Send a Push Notification tells your audience as soon as the scenario runs, with the article's details mapped from the previous module instead of copied by hand.

Turn a business event into an alert. A new order, a price drop or a form reply in another app becomes a push, as long as that app has a Make module that can start the scenario.

Reach the rest of the API. Make an API Call calls any endpoint of the Gravitec API with the same connection, which covers whatever the dedicated module does not.

Know the limits before you start. Make's own documentation for Gravitec is thin: it says there is not enough public information about the app for a complete guide, so field names are something you discover in the editor. The Make review helps you judge the platform as a whole, and Make pricing explains how operations are counted.

If you are also weighing n8n, the n8n vs Make comparison lays out the criteria without picking a winner for you.

Connect

How do you connect Gravitec to Make?

  1. 01

    Add a Gravitec module

    In your scenario, click the +, search for Gravitec and pick a module. Make then asks for a connection, which is your Gravitec account linked to Make once and reused by both modules. Click Create a connection.

  2. 02

    Name it and authorize

    Give the connection a name you will recognize later, such as the site it serves. Then follow what Make displays: either an authorization page on Gravitec's side, or a field where you paste the key Gravitec gives you.

  3. 03

    Save and check the fields

    Click Save. If the module now shows its fields and Make can read what it needs from your account, the connection works. If an error appears, create the connection again with fresh credentials.

First scenario

Your first scenario with Gravitec

GoalWhen another app signals new content, Make sends a Gravitec push notification about it.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + in the middle of the canvas. That first module will come from the app where your content or event lives.

  2. 02

    Pick the starting app

    Search for that app, choose the module that watches for the event you care about, and connect its account. Gravitec has no trigger of its own, so the start always comes from elsewhere.

  3. 03

    Add Send a Push Notification

    Click the + on the right of the first module, search for Gravitec and choose Send a Push Notification. Select your connection or create it as shown above.

  4. 04

    Map the message

    Fill the fields Make shows for the notification by mapping data from the first module, such as what the article is about. A bundle is one item passed along, so each new item produces its own push.

  5. 05

    Test with Run once

    Click Run once, trigger a test event in the first app, then open each module's bubble to read the bundle it received and the answer Gravitec sent back.

  6. 06

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default) and turn the scenario on. From then on, pushes go out without you.

Modules

What the Gravitec modules do

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

Gravitec1

Make an API Call

ActionIn the docs only

This module gives you access to the full Gravitec API from inside a scenario, reusing the connection you already created. You write the request yourself and get Gravitec's raw answer back as a bundle.

When to use it
when you need something Send a Push Notification does not offer and Gravitec's API documentation describes the endpoint for it.
Watch out
Make's own guide for Gravitec is limited, so rely on Gravitec's API reference for paths and parameters.
Gravitec2

Send a Push Notification

ActionIn the docs only

Most scenarios end on this module: it sends a push through your Gravitec account with content mapped from earlier steps. Each bundle that reaches it counts as one operation on your Make plan.

When to use it
right after the module that detects your event, such as a new blog post or a confirmed sale in another app.
Watch out
a start module that returns many items fires one push per item, so check in Run once how many bundles reach this step before you switch the scenario on.
Need help

Need help automating Gravitec with Make?

A person reads every message.

FAQ

Gravitec and Make: frequent questions

01Is the Gravitec Make integration free?
Yes, Gravitec is a standard app in Make, so it is available from the Free plan. That plan allows 2 active scenarios, a minimum of 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 count usage in credits each month. Your Gravitec subscription is separate and is not covered here.
02What do you need to connect Gravitec to Make?
A Gravitec account and a Make account are enough to begin, since Make's documentation lists no other prerequisite for this app. You add a Gravitec module, click Create a connection, optionally name it, then authorize Make on Gravitec's page or paste the key Gravitec provides, depending on what Make shows. Click Save to finish. The same connection then serves both Gravitec modules in every scenario, so you only go through these steps once per account.
03Does the Gravitec Make integration react in real time?
It depends on how the scenario starts, because Gravitec has no trigger in Make. Its two modules are actions, so the first module comes from another app or from Make's own scheduling. If that other app offers an instant trigger, which it calls through a webhook as soon as something happens, the push follows quickly. Otherwise the scenario runs on its schedule, every 15 minutes by default, and never faster than every 15 minutes on the Free plan.
04What if a Gravitec module is missing in Make?
Use Make an API Call. With it, any endpoint of the Gravitec API can be called from the scenario, reusing the connection you already set up, so you are not limited to Send a Push Notification. You will need Gravitec's API reference for the path and parameters, because Make states that its own documentation for Gravitec is incomplete. Test each call with Run once and read the returned bundle before switching the scenario on.
05Should you use Make or n8n for Gravitec?
It depends on your criteria rather than on a winner. In Make, Gravitec offers 2 modules: one to send a push notification and one to call any endpoint of the API. Many apps also have an n8n node, so check whether one exists for Gravitec before choosing. Then compare what matters to you, such as the editor you prefer, how usage is counted and the other apps your scenario must reach, using the comparison linked earlier on this page.
Same platform

Other docs you might need on this stack.

Browse all integrations