Resources · Zapier integration

Cyfe Zapier integrationAutomate Cyfe with Zapier.

The Cyfe Zapier integration does one job: it pushes a number into a dashboard widget. It offers 0 triggers, 1 action and 0 searches, so another app always starts the flow. Here is what that single action needs, what it costs, and where it trips people up.

See the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Cyfe Zapier integration actually does

Connecting Cyfe to Zapier lets another app write a value into one of your dashboard widgets each time something happens there. Cyfe is a business dashboard. Zapier is the go-between: it watches your other tools and, when an event shows up, sends a metric name and a value to a Push API widget you set up beforehand.

Three results come up again and again, and all of them rest on the same action, Push Value.

A running count. Put the value 1 in the action and every event in the source app adds one to the widget. New form entries, new sign-ups, new support tickets: the widget becomes a tally you never update by hand.

A running total. Instead of a fixed 1, map a money field coming from the trigger. Each sale then adds its own amount, and the widget turns into a revenue line fed by the tool that records the sale.

Several metrics side by side. The metric name is free text (Leads, Emails, Sales). Build one Zap per source, give each its own name and its own widget endpoint, and the dashboard groups numbers that used to live in four tabs.

Now the limits, because they shape everything. Zapier can only write to Cyfe, never read from it. There is no trigger, so a change inside Cyfe never starts a Zap. There is no search either, so a Zap cannot fetch a value already sitting in a widget and reuse it. Cyfe is always the last step of the flow, never the first.

If you are weighing tools, the Cyfe Make integration page covers the same app on the other platform, and the Make vs Zapier comparison sets out the general differences.

Vocabulary

Zapier vocabulary in one minute

Seven words come back on every Zapier screen. Here they are in plain English.

Zap
The automation you build: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Cyfe has none, so the trigger always comes from another tool.
Action
What the Zap does once started, the step that writes or sends something. For Cyfe, that is pushing a value.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan allowance counts these, nothing else.
Polling vs instant
A polling trigger is checked on a timer for new items. An instant trigger is reported by the app the moment it happens.
Filter
A step that lets the Zap continue only when what arrived meets your condition, and stops it quietly otherwise.
Connection
Your account of an app, linked to Zapier once, then reused by every step of every Zap that uses that app.
Cost

What a Cyfe Zap really costs

Cyfe is not a premium app, so it runs on the free plan. The bill comes down to one action per event.

  • Free plan100 tasks a month, unlimited Zaps
  • Free plan Zap size2 steps: one trigger, one action
  • One Push Value1 task when it succeeds
  • Premium appNo, Cyfe works on the free plan

The trigger never costs a task, and checking the source app for new items costs nothing however often it runs. Each successful Push Value counts as one task; a push that fails is not counted. The free plan gives you 100 tasks a month and Zaps of two steps only: one trigger, one action. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. A lead counter therefore costs exactly one task per lead that reaches the widget.

Connect

Connect Cyfe to Zapier in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. Before that, make sure you have a Cyfe account and access to the dashboard that will hold the widget, since the Zap writes there.

  2. 02

    Find Cyfe

    Type Cyfe in the search box of the dialog, select it, then click Add connection. Zapier creates the link once, and every Cyfe step you add later reuses it without asking again.

  3. 03

    Sign in and grant access

    Log in to Cyfe in the tab that opens and allow Zapier to reach the account. Back in Zapier, the connection appears in your list and can be picked from any Zap.

First Zap

Your first Zap: count marketing leads in Cyfe

GoalEach new Typeform entry adds one to a Leads widget, but only for the form you choose.

  1. 01

    Create the Zap and set the trigger

    Start a new Zap, pick Typeform as the app and New Entry as the event, then select your connected account and the form that collects leads.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent entries of the account, so you map the next steps on a real submission rather than a guess.

  3. 03

    Add the filter

    Click the plus icon, choose Filter, and set the field, the rule and the value using something you saw in the test. This step makes the Zap multi-step, so it needs a paid plan.

  4. 04

    Add Push Value

    Pick Cyfe and Push Value. Paste the widget endpoint, write Leads as the metric name and type 1 as the value, so each entry adds exactly one.

  5. 05

    Test, then publish

    Test the Cyfe step and check the widget moved by one. Then click Publish to switch the Zap on. Only entries created after this moment will count.

Actions

The Cyfe action, in detail

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

1

Push Value

Action

In Zapier“Pushes new value to Cyfe Push API widget.”

Sends a number, under a metric name you choose, to one Push API widget on your Cyfe dashboard. Each run hands that widget one fresh value: a fixed number or a trigger field.

When to use it
you want a widget to grow on its own, with 1 per event for a count or a mapped amount for a total.
Watch out
all three fields are required, and the endpoint you paste points at one widget only, so feeding another widget means another endpoint.
When it breaks

When a Cyfe Zap breaks

Zapier attaches no help article to Cyfe, so the failures you will meet are mostly general ones.

Most of these cases look like Cyfe is broken while the cause sits upstream, in the trigger or in the widget setup. Go through them before rebuilding anything, and keep the Zapier troubleshooting guide nearby for the rest.

  • The widget stays flat

    The Push API widget was created but never saved in Cyfe. Until you click Save Widget, it is not active and the values have nowhere to go.

  • Old data never shows up

    A Zap only reacts to events that happen after you publish it. Past sales or past entries are not picked up, and moving that history is a separate job.

  • A bulk import stalls

    When the source app suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold those items back.

  • The task count looks low

    A push that fails is not billed. If tasks used are fewer than events seen, look at the Zap history for steps that did not go through.
Need help

Need help automating Cyfe with Zapier?

A person reads every message.

FAQ

Cyfe Zapier integration: frequent questions

01Is the Cyfe Zapier integration free?
Yes, on the free plan, because Cyfe is not a premium app. The free plan includes 100 tasks a month and unlimited Zaps, but each Zap is capped at two steps: one trigger from another app and the Push Value action. That covers the simplest setup, such as counting new form entries. As soon as you add a filter to keep only some events, or a second action, the Zap becomes multi-step and requires a paid plan. No price is quoted here, since plan grids change often; check Zapier's pricing page before deciding.
02How many tasks does pushing a value to Cyfe use?
One task per successful push. The trigger in the source app costs nothing, and neither do the checks Zapier runs to look for new items. So a Zap that pushes a value for every new entry uses as many tasks as there are entries that went through. A push that fails is not counted against your plan. If one Zap feeds two widgets with two Push Value steps, each successful step counts separately, which doubles the consumption for the same event.
03Does Cyfe update in real time with Zapier?
It depends on the trigger of the other app, because Cyfe has no trigger of its own. If that trigger is instant, the source app reports the event straight away and the push follows at once, whatever your plan. If it is a polling trigger, Zapier checks for new items on a timer: every 15 minutes on Free, every 2 minutes on Professional, every minute on Team and Enterprise. The editor shows a lightning bolt on Zaps built on an instant trigger, which is the quickest way to tell.
04What does it take to connect Cyfe to Zapier?
A Cyfe account, access to the dashboard, and a Push API widget ready to receive data. The connection itself goes through the Apps page of Zapier, with + Add connection, then a sign-in to Cyfe. The widget is the part people forget: create it on the dashboard, copy the endpoint shown on its configuration screen and click Save Widget. The action asks for that endpoint, a metric name and a value, and all three are mandatory.
05Can one Zap feed several Cyfe widgets?
Yes, but each widget needs its own Push Value step, because the endpoint the action asks for belongs to one particular widget. Two steps in the same Zap make it multi-step, so that route needs a paid plan, and each successful push is billed as its own task. On the free plan, the workaround is one two-step Zap per widget, each pasted with its own endpoint and saved in Cyfe first.
06What if the Cyfe operation you need is not in Zapier?
Then it does not exist on Zapier today: the only Cyfe operation offered is Push Value. Reading a value back, reacting to a change inside Cyfe or editing a widget are not possible from the editor. Two workarounds stay within reach. Do the extra logic upstream, in the app that holds the data, before the push. Or check whether the other platforms covering Cyfe offer the operation, and compare what each one lists before you build anything.
07Zapier, Make or n8n for Cyfe?
Decide on criteria, not on reputation. First, where does your data come from: the source app has to be available on the platform you pick, since Cyfe never starts a flow. Second, the operation: on Zapier the Cyfe side is one action, Push Value, so check whether another platform lists what you need beyond it. Third, budget logic: on Zapier only successful actions are billed, and a filter pushes you onto a paid plan. Compare those points against your volume.
Same platform

Other docs you might need on this stack.

Browse all integrations