Basic Concepts

To get the most out of Flowmage, it’s important to understand how everything fits together.

This article explains the core building blocks in a simple way, so you can confidently create and manage your flows.

What is a Flow?

A flow is the heart of Flowmage.

It is a sequence of steps that define what should happen when something occurs.

You can think of a flow like a pipeline:

• It starts with a trigger

• Processes data step-by-step

• Executes actions based on logic

Each flow is fully customizable and can be as simple or advanced as you need.

What is a Trigger?

A trigger is what starts a flow.

Without a trigger, nothing happens.

Flowmage supports three main types of triggers:

Webhook

A webhook allows external systems to send data into Flowmage.

Example:

• A form submission sends data to your flow

• An external system notifies Flowmage of an event

Scheduler

A scheduler runs your flow at a specific time or interval.

Example:

• Every day at 09:00

• Every hour

• Every Monday

Manual Trigger

A manual trigger allows you to start a flow yourself.

This is useful for:

• Testing flows

• Running one-time processes

What is an Action?

An action is a step where something actually happens.

This is where Flowmage does the work.

Examples of actions:

• Sending data to an API

• Updating or inserting data

• Sending notifications

• Transforming or formatting data

A flow can contain multiple actions, executed in sequence.

What are Conditions & Logic?

Conditions allow your flow to make decisions.

Instead of always doing the same thing, your flow can adapt based on data.

You can:

• Check if a value matches a condition

• Split flows into different paths

• Skip or execute steps based on logic

Example:

• If status = approved → send to CRM

• If not → send rejection notification

This makes your flows flexible and intelligent.

How Data Moves Through a Flow

Data is what flows through your flow.

When a trigger starts a flow, it usually provides input data.
This data is then passed from step to step.

Variables (Explained Simply)

In Flowmage, data is stored in variables.

A variable is just a piece of information you can reuse later.

Example:

• email = john@example.com

• name = John

• status = approved

You can:

• Use variables in actions

• Modify them

• Pass them to the next step

Flow Example

Here’s how data moves:

1. Webhook receives:

   {
     "name": "John",
     "email": "john@example.com"
   }
   

2. Flowmage stores this as variables

3. A condition checks the data

4. An action uses the variables (e.g. send to API)

Each step builds on the previous one.

Important to Understand

• Data always comes from the trigger

• Each step can use or modify data

• Later steps depend on earlier steps

If something goes wrong, it’s often because:

• A variable is missing

• Data is not in the expected format

Summary

Flowmage is built around a simple idea:

• A trigger starts a flow

• The flow processes data (variables)

• Conditions decide what happens

• Actions perform the work

Once you understand this structure, building flows becomes much easier.