Resources · Make integration

Virtual Buttons Make integrationAutomate Virtual Buttons with Make.

Can another app press your virtual button for you? The Virtual Buttons Make integration gives you 1 action module, Push a Virtual Button. This page shows how to link your account, where the module fits in a scenario, and how to test it before switching it on.

Try the Virtual Buttons integration on MakeSee the 1 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Virtual Buttons Make integration do?

The Virtual Buttons Make integration lets a Make scenario (the automation you build, a chain of steps) push one of your virtual buttons for you. It has a single module (one brick of a scenario), an action called Push a Virtual Button. Nothing in Virtual Buttons starts a scenario on its own: another app or Make's clock does that.

Because the app offers no trigger, the useful pattern is simple: something happens elsewhere, and Make pushes the button in response. A new form entry, a paid order or a row added to a sheet can all open the scenario, with Push a Virtual Button right after. You could also skip the outside event and let Make run the scenario on a schedule, every 15 minutes by default.

Make only presses the button; since the module has no description, what the press sets off most likely depends on how the button is configured in your Virtual Buttons account. The official documentation lists no fields and no description for the module, so check its settings in the editor before you build anything around it. That same documentation carries a warning of its own: it is AI generated from vendor material and may contain mistakes, so confirm anything important with Virtual Buttons directly.

Access has a condition worth knowing before you start: you need an active Patreon account, a Creator or Developer API client, and an account on Virtual Buttons. If you are new to the editor, the Make training walks through modules and mapping, and Make troubleshooting helps when a test run fails. Weighing tools first? Read n8n vs Make.

Connect

How do you connect Virtual Buttons to Make?

  1. 01

    Find your API key

    Open the inbox tied to your Patreon account and look for the email that arrived after you linked the Virtual Buttons skill to Patreon. It holds your access code. Copy the API key it contains and keep it at hand.

  2. 02

    Add the module and open the connection

    In your scenario, add the Virtual Buttons module and click Create a connection. A connection is your Virtual Buttons account linked to Make once, then reused by every module of the app.

  3. 03

    Name it and paste your credentials

    The Connection name field is optional, but a clear name helps once you have several accounts. Paste the credentials you copied from Virtual Buttons, or follow the instructions shown on screen, then save.

First scenario

Your first scenario with Virtual Buttons

GoalWhen something happens in another app, Make pushes your virtual button.

  1. 01

    Create the scenario

    Go to the Scenarios page, create a new scenario and click the + in the middle of the canvas. That first spot is for the event that starts everything, from any app you already use.

  2. 02

    Pick the starting event

    Search the other app by name, choose its trigger, connect the account and fill its fields. Make shows what it can read once the connection exists, so you pick from a list instead of typing.

  3. 03

    Add Push a Virtual Button

    Click the + to the right of the first module, search for Virtual Buttons and choose Push a Virtual Button. Link your connection and fill the fields Make shows, mapping data from the first module where needed.

  4. 04

    Test it with Run once

    Click Run once and cause the event in the first app. Each module shows the bundles it received, a bundle being one item passed along. Check on the Virtual Buttons side that the button actually fired.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set how often Make checks, every 15 minutes by default. Then switch the scenario on. Each module run on a bundle counts as one operation on your plan.

Modules

What the Virtual Buttons module does

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

Virtual Buttons1

Push a Virtual Button

ActionIn the docs only

Your scenario presses one of your virtual buttons for you, right after the earlier steps finish, so you no longer tap it by hand. As the only module the app offers, it usually closes the flow.

When to use it
place it after a trigger from another app whenever an outside event, a new signup or a closed deal, should set off whatever your button does.
Watch out
the documentation gives no field list or description, so open the module and read what it asks for before mapping data.
Need help

Need help automating Virtual Buttons with Make?

A person reads every message.

FAQ

Virtual Buttons and Make: common questions

01Is the Virtual Buttons Make integration free?
Yes, on the Make side. Virtual Buttons is a standard app, so it works from the Free plan, which allows 2 active scenarios, a minimum of 15 minutes between scheduled runs, 5 minutes of execution per run and files up to 5 MB. Paid plans drop the interval to 1 minute and remove the cap on active scenarios. The Virtual Buttons service has its own subscription, described on its pricing page, and you also need an active Patreon account.
02What does the Virtual Buttons Make integration need to connect?
You need three things: an active Patreon account, a Creator or Developer API client, and an account created on Virtual Buttons. The key Make asks for arrives by email to the inbox tied to Patreon, sent after you link the Virtual Buttons skill to your Patreon account. With that key copied, click Create a connection on the module, give it a name if you like, paste the credentials and save.
03Can Virtual Buttons start a Make scenario in real time?
No. The app has no trigger, so nothing in Virtual Buttons can start a scenario. You have two ways around it. Open the scenario with a trigger from another app, such as a form, a store or a spreadsheet, and put Push a Virtual Button right after it. Or let Make run the scenario on its own clock, set on the first module, every 15 minutes by default and down to 1 minute on paid plans.
04What if the Virtual Buttons module in Make is not enough?
It depends on what is missing. The app has a single action and no Make an API Call module, so Make cannot do anything else in Virtual Buttons beyond pushing a button. The usual answer is to let another app handle the rest of the flow around the button. If the need is specific, the team at Hack'celeration can review your case and suggest a setup. Remember that the official documentation is AI generated and may contain mistakes.
05Make or n8n: which fits Virtual Buttons better?
It depends on the tool you already run. Many apps have both a Make module and an n8n node, so check which one covers Virtual Buttons before choosing. In Make, the whole integration is one action, Push a Virtual Button, set up through a connection that takes your emailed key. Base the choice on which editor your team knows and where your other automations already live, then build the same small flow to compare.
Same platform

Other docs you might need on this stack.

Browse all integrations