Resources · Make integration

Cyfe Make integrationAutomate Cyfe with Make.

Tired of typing numbers into a Cyfe widget by hand? The Cyfe Make integration has 1 action module, Push Value, that sends a value from any other app straight into a Push API widget. This page shows ops and marketing people how to set it up and build a first working scenario.

Try the Cyfe integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Cyfe Make integration do for your dashboards?

The Cyfe Make integration lets a Make scenario (the automation you build in Make, a chain of modules) write values into your Cyfe dashboard. Each module is one brick of that chain. Cyfe brings a single one, Push Value, which pushes your data into a Push API widget so the chart updates without anyone copying figures across.

A sales widget that fills itself. Start the scenario with a module from your CRM or your shop, for example when a deal closes, then let Push Value send the amount to the widget that tracks revenue. The dashboard stays current and nobody has to remember to update it.

Marketing numbers in one place. A form tool, a spreadsheet such as the one described on the Airtable Make integration page, or any app Make can read can become the source. Push Value only needs the value and the widget's endpoint, so the source can change later without touching Cyfe.

A counter for operations. Support tickets, sign-ups or orders can each feed their own widget. One scenario per metric keeps things easy to test and easy to switch off.

Know the limits before you start. Cyfe has no trigger in Make, so it cannot start a scenario, and it has no search module to read data back. It only receives values. There is also no Make an API Call module for Cyfe. If you are weighing tools, the n8n vs Make comparison lays out the differences, and the Make training covers scenario building from scratch.

Connect

How do you connect Cyfe to Make?

  1. 01

    Add the Push Value module

    In your scenario, click the +, search for Cyfe by name and pick Push Value. This is the only Cyfe module, so there is nothing else to choose between at this point.

  2. 02

    Skip the usual connection

    Most apps ask you to click Create a connection, which links your account to Make once for every module. Make's documentation for Cyfe says pushing a value needs no connection at all, so you can move straight to the module settings.

  3. 03

    Paste the widget endpoint

    In Cyfe, open the Push API widget you want to feed and copy its API End Point. Paste it into the module in Make. That endpoint is what tells Make which widget receives the value, so each widget has its own.

First scenario

Build your first scenario with Cyfe and Make

GoalWhen something new happens in another app, Make pushes the matching value into a Cyfe widget.

  1. 01

    Create the scenario

    Open the Scenarios page, create a new scenario and click the + to add the first module. Cyfe cannot start a scenario, so pick the app that holds your data.

  2. 02

    Set the starting module

    Add the module of that other app that notices the event you care about, create its connection and fill its fields. Make lists the folders, sheets or objects it can read once the connection exists.

  3. 03

    Add Push Value

    Click the + on the right of the first module, search Cyfe and choose Push Value. Paste the widget's API End Point, then map the number from the previous module.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Open each module to read the bundles it received (a bundle is one item passed along), then check the widget in Cyfe.

  5. 05

    Schedule and switch it on

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

Modules

What the Cyfe module does

Cyfe gives you 1 module. For each one: what it does for you, when to reach for it, and what to watch out for.

Cyfe1

Push Value

Action

In Make“Pushes your data into a Push API widget.”

Push Value gives you a Cyfe widget that stays up to date on its own: it sends a value from your scenario into a Push API widget, and the dashboard shows it.

When to use it
whenever a metric lives in another app and you want it visible on your Cyfe dashboard, such as revenue from closed deals.
Watch out
each widget has its own API End Point, so an endpoint from the wrong widget sends your data to the wrong chart.
Need help

Need help automating Cyfe with Make?

A person reads every message.

FAQ

Cyfe and Make: common questions

01Is the Cyfe Make integration free?
Yes, Cyfe is a standard app in Make, so it is available on the Free plan. The Free 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 allow 40 minutes of execution. Usage is counted in operations each month.
02What does it take to connect Cyfe to Make?
Less than most apps. Make's documentation for Cyfe states that no connection is required to push a value from Make. You add the Push Value module and use the API End Point of the Push API widget you want to feed. The documentation lists no other prerequisite. You still need a Cyfe account with that widget on a dashboard, since the endpoint comes from the widget itself. Each widget has its own endpoint, so plan one Push Value module per widget you want to feed.
03Can a Cyfe event start a Make scenario in real time?
No, Cyfe has no trigger module in Make, scheduled or instant, so nothing in Cyfe can start a scenario. Start it from another app instead: use a trigger of the app that holds your data, then add Push Value after it. You can also start a scenario on its own schedule, set on the first module, every 15 minutes by default. When the source app offers an instant trigger through a webhook, the value reaches Cyfe as soon as that app calls Make.
04What if a needed Cyfe module is missing in Make?
It depends on what you need. Make offers a single Cyfe module, Push Value, and no Make an API Call module for Cyfe, so reading data back from Cyfe or changing widgets is not possible from Make. If the goal is to show a number, Push Value covers it. For anything beyond that, look at another app that can hold or display the data, or ask the team to review the case during the 60 minute audit.
05Should you use Make or n8n with Cyfe?
It depends on the tool you already use. The same app often has an n8n node too, so check that side if your automations run in n8n. In Make, the Cyfe integration is one action, Push Value, with no connection to manage, which keeps a first scenario short. Pick the platform where your other apps and scenarios already live, so your dashboard feeds sit next to the rest of your automations.
Same platform

Other docs you might need on this stack.

Browse all integrations