Resources · Make integration

Flashyapp Make integrationAutomate Flashyapp with Make.

Can Make keep your Flashyapp contacts and messages in step with the rest of your tools? Yes. The Flashyapp Make integration offers 8 action modules for contacts, emails, SMS and custom events. This guide shows how to connect your account and build a first working scenario.

Try the Flashyapp integration on MakeSee the 8 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Flashyapp Make integration do for you?

The Flashyapp Make integration lets a Make scenario, the automation you build as a chain of modules, write into Flashyapp for you: add or update a contact, block one, send an email or an SMS, or record a custom event. Every module here is an action, so the data that starts the flow comes from another app or from a schedule.

Every signup lands in your marketing list. A form tool or a store notices a new customer, then Create a Contact adds that person to Flashyapp and Send an Email Template sends the welcome message you already designed there.

Your CRM and Flashyapp tell the same story. When a deal changes stage in your sales tool, Update a Contact refreshes the matching record, and Send Custom Event logs what happened so your Flashyapp campaigns can react to it.

No opt-out slips through. When someone unsubscribes in your support desk, Block a Contact marks them in Flashyapp before the next campaign goes out.

One limit shapes everything: Flashyapp has no trigger in Make, so it cannot start a scenario by itself. Another app or the scenario clock has to kick things off. The Flashyapp documentation on Make is also flagged as AI-generated, so double-check anything important with Flashyapp directly. If you are still weighing tools, the n8n vs Make comparison lays out the differences, and the Make review covers the editor in depth. To learn the basics with guidance, see the Make training.

Connect

How do you connect Flashyapp to Make?

  1. 01

    Copy your Flashyapp API key

    Sign in to Flashyapp, click your user name in the upper right corner, then pick API from the dropdown menu. The key sits under Key: copy it, you will paste it into Make in a moment.

  2. 02

    Open the connection window in Make

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

  3. 03

    Paste the key and save

    Paste the API key you copied into the credentials field and confirm. The connection then appears in the list, ready for the other seven Flashyapp modules of your scenarios.

First scenario

Build your first scenario: welcome every new contact

GoalWhen a new lead shows up in another app, Make adds that person to Flashyapp and sends them your welcome email template.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Since Flashyapp has no trigger, this first module belongs to the app where your leads arrive.

  2. 02

    Pick the app that starts the flow

    Search for your form tool or store by name and choose the module that watches new entries. Each new entry becomes a bundle, one item that flows to the next module.

  3. 03

    Add Create a Contact

    Click the + on the right, search Flashyapp, pick Create a Contact and select your connection. Map the email and name from the previous module into the matching fields.

  4. 04

    Chain Send an Email Template

    Add Send an Email Template after it, choose the welcome template and map the contact's email address. The same connection serves both Flashyapp modules.

  5. 05

    Test with Run once

    Click Run once, then submit a test lead in the first app. Open each module's bubble to read the bundles it received and check that the contact shows up in Flashyapp.

  6. 06

    Schedule and switch it on

    Set the schedule on the first module, every 15 minutes by default, and turn the scenario on. Each module run on one bundle counts as one operation on your Make plan.

Modules

What the 8 Flashyapp modules do

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

Flashyapp1

Block a Contact

ActionIn the docs only

This module marks an existing Flashyapp contact as blocked straight from your scenario, so an opt-out recorded somewhere else is reflected in your marketing tool too.

When to use it
a customer asks your support team to stop all messages and you want Flashyapp to know without a manual edit.
Watch out
make sure the contact you pass is the right one, because blocking the wrong address silences a good lead.
Flashyapp2

Create a Contact

ActionIn the docs only

With Create a Contact, a person captured in another app becomes a Flashyapp contact without anyone copying the data by hand. It is usually the first Flashyapp brick of a scenario.

When to use it
a new form submission, order or signup should join your Flashyapp audience without anyone retyping it.
Watch out
if the person may already exist, think about Update a Contact instead, so you do not rely on a creation step for known people.
Flashyapp3

Make an API call

ActionIn the docs only

Make an API call is the escape hatch: it reaches any part of the Flashyapp API while reusing the connection you already set up, so you are not stuck when no listed module fits.

When to use it
the action you need exists in Flashyapp but none of the other seven modules covers it.
Watch out
you build the request yourself from the Flashyapp API documentation, so keep that reference open while you fill it in.
Flashyapp4

Send Custom Event

ActionIn the docs only

Send Custom Event tells Flashyapp that something meaningful happened to a contact outside of it, such as a purchase or a closed deal, so your marketing can respond to real behavior.

When to use it
your shop or CRM records an action and you want Flashyapp to hear about it the moment the scenario runs.
Watch out
keep event names consistent across scenarios, otherwise the same action ends up recorded under several labels.
Flashyapp5

Send a SMS

ActionIn the docs only

Send a SMS lets a scenario send a text message through Flashyapp, which suits short, time-sensitive notices that an email might bury in an inbox.

When to use it
an appointment is booked or an order ships in another app and the customer should get a quick text about it.
Watch out
test with Run once on your own number first, since a mapping mistake would reach real customers' phones.
Flashyapp6

Send an Email HTML

ActionIn the docs only

Send an Email HTML sends a message whose body you build inside the scenario, which gives you full freedom to mix text and data mapped from earlier modules.

When to use it
the content changes each time, like an order summary assembled from your store's data.
Watch out
for a message your team already designed in Flashyapp, Send an Email Template is simpler to maintain than HTML written in Make.
Flashyapp7

Send an Email Template

ActionIn the docs only

Send an Email Template reuses an email already designed in Flashyapp and sends it to a contact, so marketers keep editing the design while the scenario only decides when it goes out.

When to use it
welcome sequences, confirmations or any message whose wording stays the same for everyone.
Watch out
if someone renames or deletes the template in Flashyapp, check the module again before the next run.
Flashyapp8

Update a Contact

ActionIn the docs only

Update a Contact refreshes the details of someone who already sits in Flashyapp, so a change made in your CRM or billing tool does not leave an outdated record behind.

When to use it
a customer changes plan, company or phone number in another app and your campaigns should follow.
Watch out
this module changes an existing record, so pair it with Create a Contact when new people can also come through.
Need help

Need help automating Flashyapp with Make?

A person reads every message.

FAQ

Flashyapp and Make: common questions

01Is the Flashyapp Make integration free?
Yes, on the Make side. Flashyapp is a standard app, so its modules work on the Free plan. That plan allows 2 active scenarios, runs them at most every 15 minutes, stops an execution after 5 minutes, handles files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) go down to a one-minute interval with unlimited active scenarios. Flashyapp itself is a separate matter: you need an active Flashyapp account, and its pricing page tells you what that costs.
02What do you need to connect Flashyapp to Make?
An active Flashyapp account and its API key. In Flashyapp, click your user name in the upper right corner, choose API in the dropdown and copy the value under Key. In Make, add any Flashyapp module, click Create a connection, optionally name it, paste the key and confirm. That single connection then serves all 8 Flashyapp modules, so you only do this once per account, not once per scenario or per module.
03Can a Flashyapp event start a Make scenario instantly?
No, not from Flashyapp itself: the app has no trigger module in Make, only actions. You still have two ways to start. Put another app's trigger first, and if that trigger is instant, its app calls Make through a webhook as soon as something happens. Or start the scenario from its schedule, set on the first module and every 15 minutes by default. Either way, the Flashyapp modules then run on each bundle that reaches them.
04What if a Flashyapp module you need is missing in Make?
Use Make an API call. It calls any endpoint of the Flashyapp API with the connection you already have, so you are not limited to the seven listed actions. You write the request from the Flashyapp API documentation. Note that the Flashyapp documentation on Make is marked as AI-generated and may contain mistakes, so confirm important details with Flashyapp before you build a scenario that depends on them. For a missing trigger, start from another app or from a schedule.
05Should you use Make or n8n for Flashyapp?
It depends on the tool your team already uses. On Make, Flashyapp comes with 7 ready-made action modules plus Make an API call, and it works from the Free plan. The same app often has an n8n node too, so check that side if n8n is already your platform. Neither tool is ranked here: compare which Flashyapp actions each one offers for your case and how your team prefers to build, then pick the editor you will actually maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations