# FlowMattic

> WordPress workflow automation

The full text of every published help article for FlowMattic.

---

# A booking has no Zoom or Google Meet link

Source: https://support.flowmattic.com/kb/article/194/a-booking-has-no-zoom-or-google-meet-link

## Symptom

A calendar's location is Zoom or Google Meet, but the booking confirmation and calendar invite contain no join link.

## Cause

A real Zoom or Meet link is created from a **connected host account**. If no account for that provider is connected under **FlowMattic → Connects**, the booking still completes — the invitee is booked — but there is no account to create the meeting in, so no link is added.

## Fix

**1. Connect the host account.**
Go to **FlowMattic → Connects** and connect the host's account: for Zoom, install the Zoom integration under **FlowMattic → Integrations** first, then connect it; for Google Meet, connect a **Google Calendar** account (Meet links are created through a Google Calendar event).

![FlowMattic → Connects with a Google Calendar account connected](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-bookings-connects-google.png)

**2. Assign that account to the calendar.**
Open the calendar under **FlowMattic → Bookings**, confirm the **Location** is set to Zoom or Google Meet, and use the account picker (**Zoom account** or **Google account**) to select the connected host account. Save. Until an account is picked, the confirmation links to the booking page instead of a meeting link.

![The calendar's Location section set to Zoom with the Zoom account picker](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-bookings-location-zoom.png)

**3. Make a fresh test booking.**
Existing bookings made before the account was connected will not gain a link retroactively. Make a new test booking and confirm the join link now appears in the confirmation email.

## Note

Connect the correct account — the meeting is created in whichever account you connect, and that account's owner is treated as the host. If several people take bookings, each host connects their own account and assigns it to their calendar.

---

# Add conditional logic to a form

Source: https://support.flowmattic.com/kb/article/168/add-conditional-logic-to-a-form

Conditional logic shows or hides fields based on what the visitor has already answered, so the form only asks what is relevant. This guide covers adding logic rules.

## Step 1 — Open the Logic tab

1. Open your form in **FlowMattic → Forms**.
2. Go to the **Logic** tab. Its **Conditional rules** group is where you add show/hide rules.

![The Logic tab open, showing the Conditional rules group](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-form-builder-form-logic-tab.png)

## Step 2 — Add a rule

A rule takes the shape **If** <field> <operator> [value] **Then** <action> <field>. For example, to reveal an email field only when a visitor chooses to be contacted by email:

1. Click **Add rule**.
2. Set the condition — *If `followup` is "Yes, via email"*.
3. Set the action — *Then Show `email`*.

Available actions are **Show**, **Hide**, **Require**, and **Jump to**. Fields are referenced by their **Field key**, so make sure the controlling field's key is set before writing the rule. You can also add a rule from a single field's **Conditional Logic** group in the **Field** tab.

## Step 3 — Add more rules as needed

You can add several rules to build multi-step branching — for example show a "company size" dropdown only for business leads, or hide a shipping address for digital-only orders. Each rule targets one field.

![A logic rule configured as If Your role is Founder Then Show Team size](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-form-builder-form-logic-rule.png)

## Step 4 — Test the form

Click **Preview** and step through the answers that should trigger each rule, confirming the target fields appear and disappear as expected. Save when the logic behaves correctly.

## Note on display mode

Conditional logic works in both display modes. In conversational (one-question-per-page) mode, a hidden field is simply skipped in the sequence; in single-page mode it appears or disappears in place.

---

# Add Multiple Triggers to a Workflow

Source: https://support.flowmattic.com/kb/article/241/add-multiple-triggers-to-workflow

A workflow usually starts from one trigger. With multi-trigger workflows, the same workflow can start from **several** triggers — a webhook from one store, a schedule, a form submission — and every one of them runs the same action steps. No more duplicating a workflow just to start it a second way.

This guide walks you through adding a second trigger, capturing its response, and mapping it so your existing steps keep working no matter which trigger fires.

## Step 1 — Click Add New Trigger

Open your workflow in the builder. Below the primary trigger you'll see a dashed **Add New Trigger** box.

![The Add New Trigger box below the primary trigger](https://assets.infidesk.support/products/flowmattic/kb-images/multi-trigger-workflows/mt-01-add-trigger-box-3.png)

Click it to add another trigger to this workflow.

## Step 2 — Choose the trigger app

The app picker opens. Choose any trigger app — Webhooks, Schedule, a form plugin, or any other integration that can start a workflow. You can also search for it by name.

![Choosing an app for the new trigger](https://assets.infidesk.support/products/flowmattic/kb-images/multi-trigger-workflows/mt-02-trigger-picker-2.png)

## Step 3 — Pick the trigger event

The new trigger appears on the canvas as **trigger 1.2** (your original trigger becomes **1.1** — both connect into the same first action step). Its settings open automatically: select the **Trigger Event**, exactly like setting up a normal trigger.

![Both triggers connected to the same first step, with trigger 1.2 settings open](https://assets.infidesk.support/products/flowmattic/kb-images/multi-trigger-workflows/mt-04-two-triggers-4.png)

You'll notice a **Multi-trigger workflow** notice in the settings. It explains the one rule that makes multi-trigger workflows work:

![The multi-trigger notice on the Setup tab](https://assets.infidesk.support/products/flowmattic/kb-images/multi-trigger-workflows/mt-03-trigger-setup.png)

Your action steps keep using the **first** trigger's data tags (like `{webhook1.customer_email}`). So each additional trigger's response needs to be mapped to the first trigger's keys — you'll do that once, in the next step.

> **Tip:** Each additional webhook trigger gets its **own unique webhook URL**. You'll find it on the trigger's Configure tab — send data there, not to the primary trigger's URL.

## Step 4 — Capture a response and map it

Open the new trigger's **Capture** tab and capture a sample response, just like you would for any trigger.

Once a response is captured, the **Multi-trigger workflow** section on the same tab lists every key from your *first* trigger. For each one, tell FlowMattic which key of *this* trigger's response should fill it — the tokens use the `{trigger.key}` format. If both triggers use the same key names, click **Auto-map matching keys** and you're done in one click.

![Mapping the new trigger's response to the first trigger's keys](https://assets.infidesk.support/products/flowmattic/kb-images/multi-trigger-workflows/mt-05-capture-map.png)

Each row's **+** button opens a searchable picker with this trigger's captured keys — search, click a key, and its `{trigger.key}` token is inserted for you. You can also mix tokens with static text in the same field.

![The + button opens a searchable picker with this trigger's response keys](https://assets.infidesk.support/products/flowmattic/kb-images/multi-trigger-workflows/mt-06-map-picker.png)

Save the workflow.

## How it runs

- Whichever trigger fires starts the workflow — all triggers stay active at the same time.
- When an additional trigger starts a run, FlowMattic converts its payload through your mapping, so every action step receives the data under the first trigger's keys and works unchanged.
- Task History shows which trigger started each run, so you can always tell your entries apart.

## Good to know

- All triggers share the same action steps, filters, and settings — edit them once.
- You can add more than two triggers; they're numbered 1.1, 1.2, 1.3, and so on.
- Deleting an additional trigger only removes that trigger — the rest of the workflow is untouched.
- Conditional execution set on an additional trigger applies to runs started by that trigger.

---

# Add OpenAI API Key to FlowMattic Using Connects

Source: https://support.flowmattic.com/kb/article/67/add-openai-api-key-to-flowmattic-using-connects

### Step-by-Step Guide to Adding OpenAI API Key to FlowMattic

#### 1. Install the OpenAI Integration
- Navigate to the **FlowMattic -> Integrations** page.
- Use the search box to locate the **OpenAI integration**.
- Hover over the OpenAI integration box and click the **Install** button to install the integration.

#### 2. Set Up a Connect
- Go to **FlowMattic -> Connects** and click the **Connect Integration** button.
- Search for **OpenAI** in the list and select it by clicking on the OpenAI box.
- Enter your OpenAI **API Key** in the provided field and click **Save Connect**.
- Note down the **Connect ID** displayed in the connects table for the newly added OpenAI connection. This ID will be useful for referencing the connection in future workflows.

![OpenAI Connect Settings](/storage/kb-images/7a7b9d3d0d-inline.png)

### Additional Tips
- Ensure your OpenAI API Key is valid and has the necessary permissions for your intended use cases.
- The Connect ID can be used in OpenAI action steps or AI Assistants within FlowMattic to streamline automation processes.

By following these steps, you can seamlessly integrate OpenAI with FlowMattic and unlock powerful AI-driven functionalities.

---

# Add spam protection and submission limits to a form

Source: https://support.flowmattic.com/kb/article/169/add-spam-protection-and-submission-limits-to-a-form

FlowMattic forms include several controls to reduce spam and limit who can submit. This guide covers enabling reCAPTCHA and the submission-limit options.

## Enable reCAPTCHA

reCAPTCHA v3 scores submissions automatically, so most visitors never see a challenge.

1. First, add your reCAPTCHA keys once for the whole site. In FlowMattic's global settings, paste the **site key** and **secret key** for a reCAPTCHA v3 site (create keys at `google.com/recaptcha/admin/create`).
2. Open your form and go to **Settings → Access & spam**.
3. Turn on **Enable reCAPTCHA**.

![FlowMattic's global settings showing the reCAPTCHA site key and secret key fields](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-form-builder-settings-recaptcha.png)

The **Enable reCAPTCHA** toggle only takes effect once the global keys are set — without them, enabling it on a form has no effect. Add the keys to make the protection active.

## Limit who can submit

The **Access & spam** group also has:

- **Close form after date** — set **Closes on** and the form stops accepting submissions after that date and time.
- **Limit submissions** — set **Max submissions** (default 100) and the form closes once that total is reached.

In the **Submission** group you can further restrict who submits:

- **Require authentication** — only logged-in WordPress users can submit.
- **Allow multiple submissions** — turn this off to accept only a single submission.

![The form's Access & spam settings with Enable reCAPTCHA, Close form after date, and Limit submissions](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-form-builder-form-access-spam.png)

## Test the settings

Preview the form and try to submit under the conditions you set — for example while logged out if you required authentication, or a second time if you turned off multiple submissions — to confirm the limit behaves as expected before publishing.

---

# Add tokens and sample data to an image template

Source: https://support.flowmattic.com/kb/article/170/add-tokens-and-sample-data-to-an-image-template

Tokens are what make an image template dynamic. A token is a placeholder such as `{{post_title}}` that a workflow fills with live data at render time. This guide covers defining tokens, binding them to elements, and setting their sample values.

## Step 1 — Open the Data tab

1. Open your template in **FlowMattic → Image Templates**.
2. In the right-hand panel, switch to the **Data** tab. This lists every token the template uses.

![The image editor's right panel on the Data tab, showing the token list](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-image-template-04-data-tab-tokens.png)

## Step 2 — Define your tokens

1. Click **New Token**.
2. In the **New Token** form, type the token key in the field (placeholder `Token key, e.g. post_title`) — such as `post_title`, `author_name`, or `coupon_code` — then click **Add token**.

The new token appears in the list. Set its sample value in Step 4. Keep token keys simple and flat, such as `{{full_name}}`.

## Step 3 — Bind a token to an element

1. Drag a token from the **Data** tab onto a text element on the canvas to bind it. You can also insert one into a text element with its **Insert placeholder** button.
2. For an **Image**, **Avatar**, or **Logo**, set the element's **Source** field to a token like `{{hero_image}}`.
3. For a **QR Code** element, set its **URL / Value** field to a token like `{{ticket_url}}`.

The canvas preview resolves tokens to their sample values, so you can confirm the layout looks right with realistic content.

![A text element bound to {{post_title}} with the resolved sample value rendered on the canvas](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-image-template-img-token-binding.png)

## Step 4 — Edit sample values quickly

Click **Edit Sample Values** to open a table of every token and its current sample value. Change any value to preview the template with different data. Edits here update the canvas immediately, because the preview, the Data tab, and this modal all read from the same set of sample values.

![The Edit Sample Values modal — a two-column table of tokens and their sample values](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-image-template-05-edit-sample-values.png)

## Step 5 — Save

Click **Save**. The tokens and their sample values are stored with the template. When you add the **Image Builder → Generate Image from Template** action to a workflow, it reads the template's saved sample data and gives you one field per token to map your live data into.

## How sample values are used

The sample value drives what the canvas shows while designing and what the **Download Image** and **Preview** test renders use by default. Your saved sample values also define the parameter fields the workflow action generates for the template. Keep them realistic so the design always previews correctly.

---

# A form or its embed is not showing on the page

Source: https://support.flowmattic.com/kb/article/186/a-form-or-its-embed-is-not-showing-on-the-page

## Symptom

A form does not appear where you expect — its public page is missing, or a shortcode, block, or embed snippet shows nothing.

## Cause and fix

### The form is archived

A form only renders while its **Status** is active. A form archived from **Settings → Danger zone → Archive form** will not display anywhere.

**Fix:** on the **Forms** list, check the form's **Status**. If it shows Archived, restore it so the status is active, then confirm you can reach its public page at `/flowmattic-form/{slug}/`.

![The Forms list with the Status column showing active and archived forms](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-form-builder-forms-list-status.png)

### The shortcode id is wrong

The `[flowmattic_form id="..."]` shortcode must reference the correct form id.

**Fix:** copy the shortcode straight from the form's row (**Copy Shortcode** in the ⋮ menu) or the **Settings → Embed** group rather than typing the id by hand, then paste it into the post or page.

### The wrong embed snippet was used

The **Embed** tab of the **Share** modal offers **Inline embed**, **Popup**, **Slide-in**, and **Bubble**. A popup or bubble embed does not show the form inline; it shows a launcher that opens the form.

**Fix:** if you want the form visible in the page body, copy the **Inline embed** snippet (or use the shortcode/block), and make sure its `data-fm-form`/`data-fm-embed` attributes are intact and `flowmattic-embed.js` loads on the page. Use popup, slide-in, or bubble only when you intend a launcher.

### A stale public URL was shared

Setting a custom **Public URL slug** changes the form's public URL.

**Fix:** share the current **Public URL** shown in the **Settings → Embed** group (or the **Link** tab of the **Share** modal).

## How to confirm

Open the form's public URL directly in a private browser window. If it loads there but not where you embedded it, the issue is the shortcode, block, or embed snippet on that page — re-copy it from the **Embed** tab of the **Share** modal.

---

# AI Agents Integration in FlowMattic

Source: https://support.flowmattic.com/kb/article/127/ai-agents-integration-in-flowmattic

FlowMattic's AI Agent is a powerful automation component that integrates multiple AI providers with your workflows. It allows AI models to make decisions, execute actions through tool calling, maintain conversation memory, and return structured responses — all within your automated workflows.

---

## How AI Agents Work

The AI Agent operates in an iterative loop:

1. You provide a **system prompt** (instructions) and a **user message** (the task or question).
2. The AI processes the input along with any available **tools** (FlowMattic actions the AI can execute).
3. If the AI decides to use a tool, it calls it with the required parameters.
4. The tool executes and the result is sent back to the AI.
5. The AI can call more tools or provide a **final response**.
6. This loop repeats for up to **10 iterations** until the AI produces a final answer.

![Ai agents workflow builder screen.png](/storage/kb-images/24e4e80475-inline.png)

---

## Supported AI Providers

FlowMattic supports **10 AI providers** out of the box:

| Provider | Models | Tool Calling | Notes |
|----------|--------|--------------|-------|
| **OpenAI** | GPT-4o, GPT-4 Turbo, o3-pro, GPT-3.5 Turbo | Native | Supports Responses API for reasoning models |
| **Anthropic** | Claude Opus 4, Claude Sonnet 4, Claude Haiku | Native | Full tool calling support |
| **Google Gemini** | Gemini 2.5 Pro, Gemini 2.5 Flash, Gemini 2.0 Flash | Native | Uses Google AI Studio API keys |
| **Groq** | Llama 4 Maverick, Llama 4 Scout, Qwen, DeepSeek | Native | Ultra-fast inference |
| **Mistral AI** | Mistral Large, Medium, Small | Native | European AI provider |
| **xAI (Grok)** | Grok 3, Grok 3 Fast, Grok 3 Mini | Native | By xAI |
| **DeepSeek** | DeepSeek-V3, DeepSeek-R1 | Native | Reasoning model support |
| **OpenRouter** | 100+ models from multiple providers | Native | Unified API gateway |
| **Straico** | Multi-provider aggregator | Native | Access OpenAI, Anthropic, Google models |
| **Perplexity** | Sonar, Sonar Pro, Sonar Reasoning Pro | Prompt-based | Web-grounded responses with citations |

---

## Setting Up a Connection

Each AI provider requires an API key configured in FlowMattic's connection system.

### Getting API Keys

| Provider | Where to Get API Key |
|----------|---------------------|
| OpenAI | [platform.openai.com/api-keys](https://platform.openai.com/api-keys) |
| Anthropic | [console.anthropic.com](https://console.anthropic.com/) |
| Google Gemini | [aistudio.google.com/app/apikey](https://aistudio.google.com/app/apikey) |
| Groq | [console.groq.com](https://console.groq.com/) |
| Mistral AI | [console.mistral.ai](https://console.mistral.ai/) |
| xAI (Grok) | [x.ai](https://x.ai/) |
| DeepSeek | [platform.deepseek.com](https://platform.deepseek.com/) |
| OpenRouter | [openrouter.ai](https://openrouter.ai/) |
| Straico | [straico.com](https://straico.com/) |
| Perplexity | [perplexity.ai](https://www.perplexity.ai/) |

### Creating a Connection

1. Go to **FlowMattic > Connects** in your WordPress dashboard.
2. Click **Add New Connection**.
3. Search for the AI provider name (e.g., "OpenAI").
4. Enter your **API Key** (or Bearer Token, depending on the provider).
5. Click **Save** to store the connection.

> **Tip:** You can create multiple connections for the same provider — useful if you have separate API keys for different projects or billing accounts.

---

## Configuring an AI Agent

The AI Agent component has three main configuration sections: **Chat Model**, **Memory**, and **Tools**.

### Chat Model Configuration

This is the core section where you define the AI model and its behavior.

![ai-chat-odel-provider.png](/storage/kb-images/90a3385050-inline.png)

#### Required Settings

| Setting | Description |
|---------|-------------|
| **AI Provider** | Select from the 10 available providers. |
| **Connection** | Choose the API key connection for the selected provider. |
| **AI Model** | Select the specific model to use (models are fetched from the provider's API). |
| **System Prompt** | Instructions that define the agent's behavior, role, and constraints. |
| **User Input** | The actual message or task for the AI. Supports dynamic variables from triggers and previous steps. |

#### Model Parameters (Optional)

Fine-tune the AI's response behavior with these parameters:

| Parameter | Default | Range | Description |
|-----------|---------|-------|-------------|
| **Max Tokens** | 4096 | 1–unlimited | Maximum length of the AI's response. |
| **Temperature** | 0.7 | 0–2 | Controls randomness. Lower values (0.1) = focused and consistent. Higher values (1.5) = creative and varied. |
| **Top P** | 1 | 0–1 | Nucleus sampling. Controls the diversity of vocabulary selection. |
| **Top K** | 0 (disabled) | 0–100 | Limits token selection to the top K candidates. Only supported by some providers. |
| **Frequency Penalty** | 0 | -2 to 2 | Penalizes tokens that appear frequently, reducing repetition. |
| **Presence Penalty** | 0 | -2 to 2 | Encourages the model to explore new topics. |

> **Tip:** For most use cases, the default parameters work well. Adjust **Temperature** first — use `0.1–0.3` for factual tasks and `0.7–1.0` for creative tasks.

#### Output Format

Choose how the AI should format its response:

- **Text** (default) — The AI returns a plain text response.
- **JSON** — The AI returns structured JSON matching a schema you define.

When using JSON output format, provide a **JSON Schema** that describes the expected structure:

```json
{
  "type": "object",
  "properties": {
    "title": { "type": "string" },
    "summary": { "type": "string" },
    "sentiment": { "enum": ["positive", "negative", "neutral"] },
    "tags": {
      "type": "array",
      "items": { "type": "string" }
    }
  },
  "required": ["title", "summary", "sentiment"]
}
```



#### OpenAI Responses API

For OpenAI reasoning models like `o3-pro`, `codex-mini`, or `gpt-5.1-codex-mini`, FlowMattic supports the Responses API:

| Setting | Options | Description |
|---------|---------|-------------|
| **Use Responses API** | No (Auto-detect) | FlowMattic automatically detects if the model requires the Responses API. |
| | Yes | Force using the Responses API endpoint. |

> **Note:** In most cases, leave this set to "No (Auto-detect)". FlowMattic will automatically switch to the Responses API when needed.

---

### Memory Configuration

Memory allows the AI Agent to remember previous conversations and maintain context across multiple workflow executions.

![ai-agents-memory.png](/storage/kb-images/7f9de1a9d7-inline.png)

#### Memory Types

| Type | Storage | Persistence | Best For |
|------|---------|-------------|----------|
| **No Memory** | None | Stateless | One-off queries where no context is needed. |
| **Window Buffer Memory** | WordPress transients | 24 hours | Short-term conversations, testing, and demos. |
| **FlowMattic Tables** | Custom database table | Permanent | Production use, multi-user support, audit trails. |
| **WordPress Options** | wp_options table | Permanent | Simple single-site setups. |

#### Memory Settings

**Window Buffer Memory:**

| Setting | Default | Description |
|---------|---------|-------------|
| Window Size | 10 | Number of message pairs (user + assistant) to keep in memory. |

**FlowMattic Tables:**

| Setting | Default | Description |
|---------|---------|-------------|
| Database | Local | Select local WordPress database or an external database connection. |
| Table Name | — | Name of the table to store conversation history. |
| Session ID Column | session_id | Column name used for session tracking. |
| Max History Length | 20 | Maximum number of messages to retrieve per execution. |

**WordPress Options:**

| Setting | Default | Description |
|---------|---------|-------------|
| Option Prefix | fm_agent_memory_ | Prefix for option names in wp_options table. |
| Max History Length | 20 | Maximum number of messages to keep. |

#### Session Identifier

The **Session ID** determines which conversation thread the AI continues. It works the same across all memory types:

- **Leave empty** — Auto-generates a unique session ID per execution.
- **Pass a specific ID** — Continue an existing conversation. Use dynamic variables like `{Webhook1.session_id}` or `{Trigger1.user_id}` to group conversations by user or thread.

> **Example:** A chatbot workflow using a webhook trigger can pass `{Webhook1.session_id}` to maintain separate conversations for each user.

---

### Tools Configuration

Tools allow the AI to execute FlowMattic actions during its reasoning process. This is what makes the AI Agent truly powerful — it can take actions, not just generate text.

#### Tool Source: FlowMattic Actions

Use any action from any installed FlowMattic app as a tool:

1. Click **Add Tool**.
2. Select the **Application** (e.g., HTTP, Email, Slack, WooCommerce).
3. Select the **Action** (e.g., "Send Email", "Make HTTP Request", "Create Post").
4. Write a clear **Tool Description** — this tells the AI when and how to use the tool.
5. Configure the action's parameters (some can be left for the AI to fill dynamically).

![Workflow Builder ‹ FlowMattic — WordPress 2026-03-01 at 12.52.16 AM.png](/storage/kb-images/9559a47456-inline.png)

> **Important:** Tool descriptions are critical. A well-written description helps the AI understand when to use each tool. For example: *"Use this tool to send an email notification to the customer. Requires: recipient email address, subject line, and message body."*

#### Tool Source: Custom Tools (JSON Schema)

Define custom tools with JSON schemas for integrations not available as FlowMattic apps:

| Setting | Description |
|---------|-------------|
| **Tool Name** | Unique identifier (use snake_case, e.g., `check_inventory`). |
| **Tool Description** | Explains to the AI when to use this tool. |
| **Parameters Schema** | JSON schema defining the tool's input parameters. |
| **Webhook URL** | Optional external endpoint to call when the tool is invoked. |

#### Apps Excluded from Tool Use

The following apps cannot be used as tools (to prevent recursion and control flow issues):

- Control flow: Branch, Router, Filter, Iterator
- Workflow control: Delay, Sub-Workflow
- Triggers: Schedule, Webhook, Webhook Response, MCP Trigger
- Special: Human-in-the-Loop, AI Agent

---

## How Tool Calling Works

When the AI Agent has tools available, it follows this process:

```
Iteration 1:
  AI receives → System prompt + User message + Available tools
  AI decides  → Call a tool OR respond directly
  If tool called → Execute tool, send result back to AI

Iteration 2-10:
  AI receives → Previous context + Tool results
  AI decides  → Call another tool OR provide final response
  Loop continues until done or max iterations (10) reached
```

### Example: Multi-Step Automation

**Scenario:** "Research a topic and send a summary email"

1. **Iteration 1:** AI calls the "HTTP Request" tool to fetch data from an API.
2. **Iteration 2:** AI receives the API response, processes it, and calls the "Send Email" tool with a formatted summary.
3. **Iteration 3:** AI receives confirmation that the email was sent and provides a final response: "I've researched the topic and sent a summary to john@example.com."

### Perplexity — Prompt-Based Tool Calling

Perplexity's sonar models do not support native function calling. Instead, FlowMattic uses **prompt-based tool calling**:

- Tool definitions are embedded in the system prompt.
- When the AI wants to call a tool, it outputs: `TOOL_CALL: {"name": "tool_name", "arguments": {...}}`.
- FlowMattic parses this output, executes the tool, and sends the result back to the AI.

This happens transparently — you configure tools the same way as with other providers.

---

## Using AI Agent in a Workflow

### Step 1: Add the AI Agent Step

In your workflow editor, add a new step and select **AI Agent** as the application.

![ai-agents.png](/storage/kb-images/f49ce15bd0-inline.png)

### Step 2: Configure the Agent

Set up the Chat Model, Memory, and Tools sections as described above.

### Step 3: Use Dynamic Values

Reference data from triggers and previous steps using FlowMattic's variable syntax:

**System Prompt:**
```
You are a customer support agent for {{company_name}}.
The customer's name is {Trigger1.customer_name} and their email is {Trigger1.customer_email}.
Help them resolve their issue professionally.
```

**User Input:**
```
{Trigger1.support_question}
```

### Step 4: Access Results in Subsequent Steps

After the AI Agent step executes, you can use its output in later steps:

| Variable | Description |
|----------|-------------|
| `{AIAgent1.message}` | The AI's final text response. |
| `{AIAgent1.status}` | `success` or `error`. |
| `{AIAgent1.provider}` | The AI provider used (e.g., "openai"). |
| `{AIAgent1.model_id}` | The specific model used (e.g., "gpt-4o"). |
| `{AIAgent1.session_id}` | The memory session ID. |
| `{AIAgent1.memory.message_count}` | Number of messages in conversation history. |
| `{AIAgent1.memory.memory_type}` | The memory type configured. |

---

## Real-World Examples

### Customer Support Chatbot

- **Provider:** OpenAI (gpt-4o)
- **Memory:** FlowMattic Tables (persistent, multi-user)
- **Tools:** Send Email, Create Support Ticket, Look Up Order
- **System Prompt:** "You are a helpful customer support agent. Always be polite and try to resolve issues. If you can't resolve it, create a support ticket."
- **Flow:** Webhook Trigger → AI Agent → Response sent back via webhook

### Content Generation with Structured Output

- **Provider:** Anthropic (Claude Sonnet)
- **Memory:** None (one-shot generation)
- **Tools:** Save to Database, Send Slack Notification
- **Output Format:** JSON with schema for title, body, tags, and SEO metadata
- **Flow:** Manual Trigger → AI Agent generates content as JSON → Save to WordPress → Notify team on Slack

### Data Processing Pipeline

- **Provider:** Groq (Llama 4 Maverick) — for speed
- **Memory:** Window Buffer (short-term)
- **Tools:** HTTP Request, FlowMattic Tables Insert
- **System Prompt:** "You are a data analyst. Fetch data from the provided API, analyze it, and store the results."
- **Flow:** Schedule Trigger → AI Agent fetches and processes data → Results stored in database

---

## Troubleshooting

### Common Issues

**"Failed to get API key from connection"**
- Verify the connection is active in **FlowMattic > Connects**.
- Check that the API key is valid and has sufficient credits/quota.

**AI not calling tools**
- Ensure tool descriptions are clear and specific.
- Check that the system prompt instructs the AI to use tools when appropriate.
- Some models are better at tool calling than others — GPT-4o and Claude Sonnet are recommended.

**JSON output is invalid or wrapped in markdown**
- FlowMattic automatically strips markdown fences (` ```json ... ``` `) from responses.
- If you still get invalid JSON, try a more capable model or simplify your JSON schema.

**Tool execution fails**
- The AI receives the error and can attempt a different approach.
- Check that the tool's action is configured correctly (correct connection, required fields).
- Review the workflow execution log for details.

**Memory not working**
- Verify the Session ID is consistent across executions. If auto-generated, each execution creates a new session.
- For FlowMattic Tables memory, ensure the table exists with the required columns.

**Model not found or "not a chat model" error**
- For OpenAI reasoning models (o3-pro, codex-mini), enable the **Responses API** toggle.
- Click the refresh button to re-fetch the latest models from the provider.

### Debug Options

Enable these options for troubleshooting:

- **Include Execution Log** — Logs each iteration step, showing what the AI decided and which tools were called.
- **Include Request Body** — Records the full API requests sent to the provider.

These are saved in the workflow execution history and can be reviewed from the **FlowMattic > Task History** page.

---

## Summary

| Feature | Details |
|---------|---------|
| **Supported Providers** | 10 (OpenAI, Anthropic, Google, Groq, Mistral, xAI, DeepSeek, OpenRouter, Straico, Perplexity) |
| **Tool Calling** | Native (9 providers) + Prompt-based (Perplexity) |
| **Memory Options** | Window Buffer, FlowMattic Tables, WordPress Options |
| **Output Formats** | Text, JSON (with schema validation) |
| **Max Iterations** | 10 per execution |
| **Responses API** | Supported for OpenAI reasoning models |
| **Dynamic Variables** | Full support for trigger and step data |

---

# AI Assistant Actions: Workflows, Leads & Meetings

Source: https://support.flowmattic.com/kb/article/229/flowmattic-ai-assistant-actions

A FlowMattic AI Assistant doesn't just answer questions — it can *act*. The **Actions** tab turns your chatbot into a lead magnet and a workflow trigger: run automations when it replies, capture visitor details, and let people book a meeting without leaving the chat.

Open your assistant and switch to the **Actions** tab.

![The Actions tab](https://assets.infidesk.support/products/flowmattic/kb-images/ai-assistants/actions-tab.png)

---

## Trigger a workflow on each reply

At the top of the tab you can connect the chatbot to your automations:

- **Event** — when the automation should fire. **Chatbot Response Generated** runs every time the assistant replies. Other events — **Lead Captured**, **Meeting Scheduled**, **Link Clicked** — are available as triggers in the **FlowMattic Chatbot** app inside the workflow builder.
- **Action** — what to do, e.g. **Trigger Workflow**.
- **Workflow** — which workflow to run.

This lets you log every conversation, notify your team on Slack, push leads into your CRM, or anything else a workflow can do — automatically, on each response.

---

## Suggestions

Give visitors a head start with **Suggestions** — default prompt buttons shown under the chat (e.g. *"What services do you offer?"*, *"I want to book a meeting with your team"*). They lower the friction of starting a conversation and steer people toward what your bot does best.

---

## Collect Leads

Enable **Collect Leads** to add a form that gathers visitor information — name, email, and any fields you need — right inside the chat. Captured leads fire the **Lead Captured** event, so you can route them into a workflow (CRM, email, spreadsheet, …) the moment they come in.

---

## Link Button

Add a **Link Button** to display a call-to-action that opens a URL — a pricing page, a signup link, a docs article — so the assistant can guide visitors to the next step.

---

## Schedule Meeting

Turn on **Schedule Meeting** to display an inline calendar so visitors can book time with your team without leaving the conversation. A completed booking fires the **Meeting Scheduled** event for follow-up automations.

---

## Putting it together

A single assistant can, in one conversation: answer from your knowledge base, suggest next questions, capture a lead, book a meeting, and trigger a workflow to notify your team — all configured from this one tab.

---

**Related guides:** [Getting Started](https://support.flowmattic.com/portal/flowmattic/kb/article/227/flowmattic-ai-assistants-getting-started) · [Content Sources](https://support.flowmattic.com/portal/flowmattic/kb/article/228/flowmattic-ai-assistant-content-sources) · [Style & Embed](https://support.flowmattic.com/portal/flowmattic/kb/article/230/flowmattic-ai-assistant-embed)

---

# An image token shows the wrong value or does not update

Source: https://support.flowmattic.com/kb/article/192/an-image-token-shows-the-wrong-value-or-does-not-update

## Symptom

A rendered image shows the wrong text or picture for a token — the old sample value, a blank space, or the raw `{{token}}` text — or an edit to a sample value does not appear in the preview.

## Cause and fix

### The token always shows its sample value

The editor preview always uses the template's saved **sample values** — real workflow runs use the data the workflow supplies. If a token shows the wrong thing on a real run, the action is not sending a value for it, or its key does not match.

**Fix:** open the **Image Builder → Generate Image from Template** action. In **Parameters** mode, confirm the field for that token is mapped to captured data, not left blank. Map it with the variable picker if needed.

### The raw `{{token}}` appears in the image

The `{{token}}` key in the layer must exactly match — case-sensitive — the token/parameter key the workflow supplies. A mistyped, differently cased, or unmatched key is not replaced, so the raw token text shows in the output.

**Fix:** make the key in the element match the saved token and the workflow mapping exactly, keeping it a simple flat key like `{{full_name}}`, and rebind it to the element.

### An edit to a sample value does not show in the preview

The canvas preview, the Data tab, and the Edit Sample Values modal all read from the same set of sample values, so editing a value should update the preview immediately. If it does not, the element may be showing a stale selection.

**Fix:** click elsewhere on the canvas and back, or reopen the template, so the preview re-reads the current sample values.

### A workflow broke after editing the template

Workflows map to tokens by their key. Renaming or removing a token breaks any workflow step that maps to the old key.

**Fix:** after renaming or removing a token, open each workflow that uses this template and update its parameter mapping to the new token.

![The Image Builder action in Parameters mode with a token field highlighted](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-image-template-wf-image-token-field.png)

## Prevention

Decide token keys before you build workflows, keep them flat (`{{full_name}}`, `{{coupon_code}}`), match them exactly (case-sensitive) in every workflow mapping, and give each a realistic sample value. Stable keys and good samples keep the design, the preview, and the workflow output in agreement.

---

# A PDF field shows the wrong or a stale value

Source: https://support.flowmattic.com/kb/article/195/a-pdf-field-shows-the-wrong-or-a-stale-value

## Symptom

A generated PDF shows a value that is out of date, always the same regardless of the workflow data, or the wrong data type (a number where you expected text, or a raw `{{token}}` that was never replaced).

## Cause and fix

### The field always shows the same value — it is reading the sample data

Any token your workflow step does not supply falls back to the value stored in the template's **sample data**. If a field never changes between runs, the action is almost certainly not sending that value, so the render uses the sample.

**Fix:** open the **PDF Builder → Generate PDF from Template** action. In **Parameters** mode, confirm the field for that key is mapped to captured data from an earlier step, not left blank. If it is blank, map it with the variable picker.

### The raw `{{token}}` appears in the PDF

A token that renders literally was not matched to any key in the data you sent. This usually means the token name on the template and the key you mapped do not match, or the path is wrong.

**Fix:** compare the token on the template (for example `{{client.name}}`) with the structure of the data you are sending. The path must match exactly, including nesting. Update either the template token or the mapping so they agree.

### The value has the wrong data type

In **Parameters** mode, values are coerced automatically: `1200` becomes an integer, `true` and `false` become booleans, and a value starting with `{` or `[` is parsed as JSON. If you needed the literal string `"1200"` (for example a zero-padded reference), the coercion changed it.

**Fix:** switch **Dynamic Data Mode** to **JSON** and send the value as a quoted string in the payload, so it is preserved exactly.

### A whole section is missing

If an entire block is empty, the parent key was not supplied and the sample data had nothing for it either.

**Fix:** make sure the top-level key exists in both your template's sample data (so the action generates a field for it) and your action mapping (so a value is actually sent).

![The PDF Builder action in Parameters mode, where each parent-level key maps to your workflow data](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-pdf-template-builder-wf-pdf-parameters.png)

## Prevention

Set complete, realistic sample data on the template before building the workflow step. The action's Parameters fields are generated from the sample data's top-level keys, so accurate sample data gives you the correct fields to map and sensible fallbacks for anything you intentionally leave out.

---

# API by FlowMattic

Source: https://support.flowmattic.com/kb/article/16/api-by-flowmattic

The **API** (Application Programming Interface) is a set of protocols, routines, and tools that enable software applications to interact with one another. APIs allow data sharing and the execution of functions between different systems, making them essential for integrating third-party tools, services, or data into existing applications. APIs are widely used across various platforms like web applications, mobile apps, and more.

In FlowMattic, the **API module** allows users to interact with external APIs, enabling data exchange between different systems and automating a wide range of tasks. With this module, users can perform HTTP/HTTPS actions such as GET, POST, PUT, DELETE, and PATCH to retrieve, update, or delete data across different platforms. The **FlowMattic API module** is particularly useful for automating processes like data synchronization, report generation, and data entry between systems.

### Key Features of the API Module

- Perform HTTP/HTTPS requests (GET, POST, PUT, DELETE, PATCH).

- Retrieve and send data between different systems.

- Supports custom headers and parameters for API requests.

- Multiple authentication options including Basic, Bearer Token, and the newly added **Connects** for pre-authenticated access.

* * *

### Step-by-Step Instructions for Using the FlowMattic API Module

To use the API module in a FlowMattic workflow, follow these steps:

#### 1\. Create a New Workflow

- Log into your WordPress dashboard and and navigate to the **FlowMattic Dashboard**.

- Click the **"New Workflow"** button to start creating a new workflow.

#### 2\. Select the API Integration

- In the workflow builder, click on the **"Choose Application"** button.

- From the available options, select **“API Integration”**.

#### 3\. Choose the Action Event

Once you've selected API Integration, choose the type of action event (HTTP request) that you want to perform:

- **GET**: Retrieves data from the API endpoint.

- **POST**: Creates new data in the API endpoint.

- **PUT**: Updates existing data in the API endpoint.

- **DELETE**: Deletes data from the API endpoint.

- **PATCH**: Partially updates existing data in the API endpoint.

#### 4\. Enter the API Endpoint URL

- Provide the **API endpoint URL** where the action will be performed. The endpoint URL typically consists of the protocol (HTTP/HTTPS), domain name, and the specific path to the API resource.

- The API documentation for the service you're integrating with will specify the correct endpoint URL.

#### 5\. Authentication Option

To ensure secure communication, most APIs require authentication. FlowMattic supports multiple authentication methods:

- **Basic Authentication**: A standard method where the username and password are encoded and passed in the request.

- **Bearer Token Authentication**: Uses an API token or key provided by the API provider.

- **Connects**: This option allows users to leverage pre-authenticated API access data through **[FlowMattic Connects](https://support.flowmattic.com/kb/article/4/how-to-use-connects/ "How to use Connects?")**. If you've already set up API connections in **FlowMattic Connects**, you can select this option to use the stored credentials for authentication, making the setup process faster and more secure.

- **How to Use Connects**: If you've previously configured an API connection in the FlowMattic **Connects** section, simply select the appropriate connection, and the stored credentials will be used automatically for the API request, removing the need to input the authentication details again.

- **When to Use Connects**: This option is particularly useful for APIs that are used frequently across multiple workflows, allowing you to centralize your API authentication management.

#### 6\. Set Custom Headers (Optional)

Some APIs require specific headers, such as `Content-Type` or custom authentication tokens. In FlowMattic, you can define these custom headers as needed:

- Enable the **Custom Headers** option.

- Add the required headers by specifying the **Key** (header name) and **Value** (header content).

#### 7\. Add Parameters (Optional)

If your API request requires parameters (such as query parameters or a request body), you can configure them in the **Parameters** section:

- Enable the **Parameters** option.

- Define the necessary **Key** (parameter name) and **Value** (parameter content) pairs.

#### 8\. View the API Response

After configuring the API step, you can view the **API response** in the step output:

- FlowMattic captures the full API response, including all data returned by the endpoint.

- By default, only the **parent-level keys** are shown in the step output. However, all the data is captured in the background, and you can expand it as needed in subsequent steps.

#### 9\. Conditional Execution

FlowMattic allows you to configure **conditional execution** for the API module. This means you can specify conditions under which the API request will be executed. Conditional execution can make your workflows more efficient by preventing unnecessary API requests:

- Enable the **Conditional Execution** option and set the conditions based on the response from previous steps.

#### 10\. Save and Test the API Request

- Once you’ve configured all the necessary fields, click **“Save & Test Action”**.

- The system will send a live request to the API, and the response will be displayed in the output. This allows you to verify that your API request is functioning as expected.

#### 11\. Finalize the Workflow

- After successfully testing the API step, click **“Save and Continue”** to finalize the workflow.

- The API step is now ready to be executed as part of your workflow.

* * *

### Conclusion

The **API module in FlowMattic** offers a powerful and flexible way to integrate external applications into your automated workflows. Whether you’re retrieving data, sending updates, or deleting information, the API module enables seamless communication between systems via HTTP/HTTPS protocols.

With the new **Connects** feature, managing authentication for your APIs is easier than ever, allowing you to reuse pre-authenticated credentials across multiple workflows. Combined with custom headers, parameters, and conditional execution, FlowMattic provides full control over API requests and ensures they are configured to suit your needs.

By following this step-by-step guide, you can quickly and easily set up API integrations and improve the efficiency of your automated workflows, helping to streamline your business processes.

---

# Authentication keeps expiring or Delay not working

Source: https://support.flowmattic.com/kb/article/46/authentication-keeps-expiring-or-delay-not-working

Sometimes, the authentication token on your website might expire, causing the authentication to fail on your website. This can happen due to various reasons, such as cron jobs not running on time, the website blocking the wp_remote_post() function, etc.

Same goes with the `Delay` module, as it is also depend on the WordPress Cron jobs.

If you're facing the authentication token expiration issue or delay not working issue multiple times, here's how you can troubleshoot and fix the issue -

### 1 ) Cron jobs on your website are not executing on time

Cron jobs are scheduled tasks that run at specific intervals. They are used to renew the authentication token on your website. If the cron jobs on your website are not executing on time, the authentication token will expire, and you will need to re-authenticate your website with Flowmattic.

To fix this issue, you can use a plugin like WP Crontrol to check if the cron jobs on your website are running correctly. If you find that the cron jobs are not running on time, you can try disabling and re-enabling the cron jobs to see if that fixes the issue.

Another and more reliable way to fix this issue is to set up a server-side cron job to run the wp-cron.php file on your website at regular intervals. This will ensure that the cron jobs on your website are running on time and that the authentication token does not expire.

Before setting up a server-side cron job, make sure the WordPress cron is disabled on your website. You can disable the WordPress cron by adding the following line of code to your wp-config.php file -

### Setting Cron using Cloudflare

 ```php
define( 'DISABLE_WP_CRON', true ); 
 ```

If you're using Cloudflare to manage your website, here's how you can set the cron job on Cloudflare -

1. Log in to your [Cloudflare account](https://dash.cloudflare.com/).
2. Choose your domain from the Cloudflare Dashboard 
3. On the sidebar menu, click the **Workers Routes**

![workers routes.png](/storage/kb-images/b34515e097-inline.png)

4. On the Workers Routes page, click the button "**Manage Workers**"

![click-manage-workers.png](/storage/kb-images/fca1ec96d1-inline.png)

5. Now, click the "**Create Application**" button on the Workers & Pages 

![create-application.png](/storage/kb-images/b3fd6dfeb0-inline.png)

6. On the Get Started page, click "Get Started" button next to the "Start with Hello World!" block

![get-started.png](/storage/kb-images/0c902926e5-inline.png)

7. Click **Deploy** and Cloudflare will create a worker for you
![click-deploy.png](/storage/kb-images/545cb30610-inline.png)

8. On the next screen, click “**Edit Code**”

![edit-code.png](/storage/kb-images/b468e3a70b-inline.png)

9. Remove the existing code from worker.js file
10. Copy and paste the following code into the Worker editor and click Deploy button

 ```javascript
addEventListener('scheduled', event => {
  event.waitUntil(handleScheduled(event.scheduledTime))
})

async function handleScheduled(scheduledDate) {
  const response = await fetch('https://yourwebsite.com/wp-cron.php?doing_wp_cron')
  const text = await response.text()
  console.log(text)
} 
 ```
 
![edit-and-replace-code.png](/storage/kb-images/5351519cff-inline.png)

11. Replace 'https://yourwebsite.com/wp-cron.php' with the URL of your website's wp-cron.php file.
12. Click on  **Deploy** button on the same screen, and it will create a cron job for your site.
13. Now, go back to your worker and switch to the "**Settings**" tab.

![worker-settings.png](/storage/kb-images/e882becc38-inline.png)

15. Click on "**Trigger Events**" on the settings page side menu
16. Click on "**+Add**" link in the " **Trigger Events**"

![create-trigger-event.png](/storage/kb-images/c8794cf2bd-inline.png)

17. Select "**Cron Triggers**" from the available options.

![cron-triggers.png](/storage/kb-images/530418da13-inline.png)

18. Set the **Schedule** for the cron job to run every minute or every 5 minutes maximum.
19. Click on the "Add" button at the bottom of the page to save the changes.

![set-5-min-trigger.png](/storage/kb-images/97bc34c495-inline.png)

20. Now, your server-side cron job is set up, and the cron jobs on your website will run on time.

If you're not using Cloudflare, you can set up a server-side cron job using cPanel or any other hosting control panel that your hosting provider offers. You can also contact your hosting provider for help in setting up a server-side cron job on your website.

### 2 ) Website is blocking the wp_remote_post() function

Some websites have security measures in place that block the wp_remote_post() function, which is used to renew the authentication token on your website. If your website is blocking the wp_remote_post() function, the authentication token will expire, and you will need to re-authenticate your website with Flowmattic.

If you're using a security plugin on your website, you can try disabling the plugin temporarily to see if that fixes the issue. If disabling the security plugin fixes the issue, you can contact the plugin developer to see if they can provide a solution to whitelist the wp_remote_post() function on your website.

---

# Automate Bookings with FlowMattic Workflows

Source: https://support.flowmattic.com/kb/article/156/automate-bookings-with-flowmattic-workflows

The **FlowMattic Bookings** application connects your booking calendars to the Workflow Builder. It lets a workflow run automatically whenever something happens to a booking, and it lets a workflow act back on bookings — adding notes, changing status, and more. It also ships ready-made default workflows so confirmation and reminder messaging is driven by automation you can edit, rather than hard-coded email logic.

You'll find it in the Workflow Builder when you choose an application; it's listed as **FlowMattic Bookings** (app slug `bookings`). It's a core integration, so no separate install is needed.

## Triggers: run a workflow when a booking event happens

A **trigger** starts a workflow. Pick **FlowMattic Bookings** as your trigger app, then choose one of these events:

- **New Booking** — fires when a new booking is made on a calendar.
- **Single-Use Calendar Booking Received** — fires when a booking is made specifically on a single-use (one-time) link. (A single-use booking also fires "New Booking".)
- **Booking Updated** — fires when a booking's details are updated.
- **Booking Rescheduled** — fires when a booking is moved to a new time.
- **Booking Cancelled** — fires when a booking is cancelled.
- **Booking Completed** — fires when a booking is marked completed.
- **Booking Marked No-Show** — fires when a booking is marked no-show.
- **Booking Deleted** — fires when a booking is deleted.
- **New Calendar** / **Calendar Updated** / **Calendar Deleted** — fire on calendar lifecycle changes (not individual bookings).

![The Workflow Builder trigger step with "FlowMattic Bookings" selected, the New Booking event chosen](https://assets.infidesk.support/kb/inline/2026/07/jpJ2Jn7JqW8upuyPBUgTvFhWrSLgpQ6RfvucCVDx.png)

### Scoping a trigger to one calendar

Booking triggers carry a **Calendar** picker. Set it to a specific calendar to fire only for that one, or leave it set to **any** to fire for every calendar. Clicking the data icon next to the Calendar field injects your calendar list into the picker; a refresh icon reloads the list from the server if you've just added a calendar.

![Calendar picker set to a specific calendar](https://assets.infidesk.support/kb/inline/2026/07/vLUMsnreSgirA6A0Z2YXHzH3WjGWPkq8ChBqW1PW.png)

### What data each booking event carries

Every booking trigger delivers a flat payload — each key becomes a `{{tag}}` you can map into later steps. The booking events all carry the same set of fields, so one workflow can branch on **status** instead of being duplicated per event:

- `booking_id`, `calendar_id`, `calendar_name`
- `booking_date`, `booking_time`, `booking_end`, `duration_minutes`, `timezone`
- `location`
- `customer_name`, `customer_email`, `customer_phone`
- `company`, `notes`
- `guests` (comma-separated), `guest_count`
- `status`
- `manage_url` (the public page link)
- `send_confirmation`, `send_remind_24h`, `send_remind_1h`, `allow_reschedule`, `allow_cancel` — yes/no flags reflecting that calendar's notification toggles
- `triggered_at`

A **rescheduled** event additionally carries the previous slot as `old_date` and `old_time`, plus `notify` and `message` (whether to notify the attendee and any custom message the host added). Calendar triggers carry a different, calendar-shaped payload (`calendar_id`, `calendar_name`, `calendar_slug`, `calendar_status`, `calendar_type`, `calendar_url`, `duration_minutes`, `location`, `timezone`, `color`, `created`, `updated`).

![booking-trigger-response](https://assets.infidesk.support/kb/inline/2026/07/p14tvkTt5Nwe2iNGEZ3D1UEfYDSlkqwRRaLEaFek.png)

## Actions: act on bookings from a workflow

An **action** is a step a workflow runs. With **FlowMattic Bookings** chosen as an action app, you can manage calendars and bookings programmatically. The available actions include creating, updating, regenerating, deleting and fetching calendars; adding, updating, rescheduling, cancelling, completing, marking no-show, deleting, fetching and finding bookings; sending an email to a booking; and the two highlighted below.

Actions that target a booking can find it by **booking ID** or by **customer email**, or fall back to the booking from the trigger that started the workflow. Actions that target a calendar use the **Calendar** picker (the same one as triggers).

Every action returns a flat result envelope with a `status` and `message` plus the affected booking's or calendar's fields (e.g. `booking_id`, `booking_status`, `customer_email`, `calendar_id`), so you can map them into downstream steps.

![bookings-workflow-action-selection](https://assets.infidesk.support/kb/inline/2026/07/fV44a2HEUHPTQewERVZtxmL5UBzt2ikhV5B7Xtqy.png)

### Add Note to Booking

The **Add Note to Booking** action appends a line to a booking's activity log. It takes a single **note** field (required). The note is recorded in the booking's activity history (prefixed with "Note:") and is visible when you open the booking in the dashboard. Use it to leave context on a booking automatically — for example, the source of the lead, a CRM record ID, or the result of an earlier step.

### Update Booking Status

The **Update Booking Status** action sets a booking's status. It takes a **status** field, which must be one of `confirmed`, `pending`, `cancelled`, `completed`, or `no_show`. The change is written to the booking and logged in its activity history.

Importantly, setting the status to **cancelled**, **completed** or **no_show** also fires that status's matching lifecycle trigger — so an "Update Booking Status → cancelled" step will itself fire the **Booking Cancelled** trigger (and its emails/workflows), exactly as if you'd cancelled it by hand. Keep this in mind to avoid building loops.

![ A workflow action step with "FlowMattic Bookings" selected, the Update Booking Status action chosen, and the status field set to "completed"](https://assets.infidesk.support/kb/inline/2026/07/ybuWcM1q1lAd6VB3vqeSBNSqaxXFeqPAcVNGXUsj.png).

## The bundled default workflows

So that confirmation and reminder messaging isn't hard-coded, the Bookings app bundles ready-made default workflow templates. The calendar notification toggles map onto these instead of fixed email logic, and you can open and edit them freely:

- **Booking confirmation email** — triggers on **New Booking** and emails the invitee a confirmation with the event details (date, time, time zone, and the manage link). Replaces hard-coded confirmation logic.
- **24-hour booking reminder** — triggers on **New Booking**, then uses a Filter step gated on the `{{send_remind_24h}}` flag and a Delay step timed to 24 hours before the meeting, before emailing the reminder. So the reminder only goes out when that calendar has reminders turned on.
- **Booking cancellation notice** — triggers on **Booking Cancelled** and emails the invitee to let them know, with a rebooking link. Replaces hard-coded cancellation logic.

These templates use the same `{{customer_email}}`, `{{customer_name}}`, `{{calendar_name}}`, `{{booking_date}}`, `{{booking_time}}`, `{{timezone}}` and `{{manage_url}}` tags from the trigger payload, so you can rewrite the subject and body to match your voice without touching code.

![The 24-hour booking reminder default workflow open in the builder, showing the New Booking trigger, the Filter step checking send_remind_24h, the Delay step, and the email action](https://assets.infidesk.support/kb/inline/2026/07/Gvzr793TaY0QBYIDRVuTQOcU0mvBmiUC80xjiuE6.png).

## Putting it together

Typical patterns:

- **Push every booking into a CRM** — trigger on New Booking (scoped to a calendar or "any"), add a "create contact" step in your CRM app, and map `customer_name`, `customer_email`, `customer_phone`, `booking_date`, `booking_time`, `notes` and `manage_url`.
- **Log bookings to a Table** — trigger on New Booking and add a Tables "create row" step for reporting.
- **Notify your team** — trigger on New Booking and post the details to Slack or send an SMS.
- **React to cancellations and no-shows** — trigger on Booking Cancelled or Booking Marked No-Show to free up follow-up tasks, re-engage the lead, or update a deal stage.
- **Annotate or progress a booking automatically** — use Add Note to Booking and Update Booking Status inside a larger workflow (or an AI agent's tool chain) to record outcomes and move bookings through their lifecycle.

Because every booking event is a trigger and most booking operations are actions, any FlowMattic workflow can both react to bookings and create or change them — making Bookings a fully scriptable part of your automation, not a closed-off scheduler.

---

# Bind dynamic data in PDF templates with tokens and sample data

Source: https://support.flowmattic.com/kb/article/171/bind-dynamic-data-in-pdf-templates-with-tokens-and-sample-data

A PDF template becomes dynamic when you mark the parts that change per run as **tokens**, and define **sample data** that describes the shape of the data your workflow will send. This guide explains how to do both, and why the sample data matters for the workflow step you build later.

## How tokens work

A token is a placeholder written as `{{path.to.value}}`. When the workflow renders the PDF, each token is replaced with the matching value from the data you send. Tokens can point to nested values using dots (`{{client.name}}`) and to items in a list (`{{line_items}}` for a Table element).

Any text on the canvas can mix static text and tokens, so `Invoice #{{invoice.number}}` renders as `Invoice #1042`.

## Step 1 — Open your template's Data panel

1. Go to **FlowMattic → PDF Templates** and open the template you want to edit.
2. In the editor's right panel, open the **Data** tab. It shows the template's **sample data** as a schema; its **Edit** button opens an **Edit JSON data** editor where you edit the JSON directly.

![The PDF Template Builder with the Data panel open, showing the template's sample data](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-pdf-template-builder-pdf-data-panel.png)

## Step 2 — Write sample data that matches your workflow

The sample data is a JSON object whose keys match the values you will send from your workflow. Edit it so the structure mirrors your real data. For an invoice, that might be:

```json
{
  "invoice": { "number": "1042", "date": "2026-05-01" },
  "client": { "name": "Acme Ltd", "email": "billing@acme.com" },
  "line_items": [
    { "description": "Design work", "amount": 1200 },
    { "description": "Hosting", "amount": 150 }
  ],
  "totals": { "subtotal": 1350, "tax_rate": 0.2 }
}
```

Fill each value with a realistic example. This example is what you see while designing, and it is also the fallback used at render time for any value your workflow does not supply.

## Step 3 — Bind tokens to elements

1. Click a text element on the canvas.
2. Type a token where the value should appear, for example `{{invoice.number}}` in a heading, or `{{client.name}}` in an address block.
3. For a **Table** element, point it at an array such as `line_items` and map its columns to the item keys (`description`, `amount`).
4. For a **Totals** element, use a formula such as `sum(line_items.amount)` or `mul(totals.subtotal, totals.tax_rate)`.

You can also insert tokens from the **Data** tab: drag a field onto an element, or click it to copy its `{{path}}`. In **Preview** the tokens resolve to the sample values, so you can confirm the layout looks right with real-looking content.

![The Billed to element selected — {{client.name}} in its line field, resolved to the sample value on the page in Preview](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-pdf-template-builder-pdf-clientname-binding.png)

## Step 4 — Save the template

Click **Save**. The token names and the sample data are stored with the template.

## Why sample data matters for the workflow step

When you later add the **PDF Builder → Generate PDF from Template** action to a workflow and pick this template, FlowMattic reads the **parent-level keys** of your sample data and generates one labelled field per key under **Parameters**. In the example above you would get fields for `invoice`, `client`, `line_items`, and `totals`.

This means two things:

- If you set the sample data first, the workflow step gives you a clean, labelled form to map your captured data into.
- If the sample data is missing or incomplete, the step has nothing to build those fields from, and you must switch the action to **JSON** mode and hand-write the whole payload.

At render time, any key your workflow does not provide falls back to the value in the sample data. This is useful for fixed values you never change, but it is also worth knowing when a field looks "stuck" — if a binding always shows the same value, it may be reading the sample rather than your workflow data.

---

# Booking reminders and follow-ups are not sending on time

Source: https://support.flowmattic.com/kb/article/172/booking-reminders-and-follow-ups-are-not-sending-on-time

## Symptom

The booking confirmation arrives immediately, but the 24-hour reminder, 1-hour reminder, or post-meeting follow-up arrives late or not at all.

## Cause

The confirmation is sent the moment a booking is made, but reminders and follow-ups are **scheduled** for a future time and dispatched by WordPress cron (WP-Cron). By default WP-Cron only runs when someone visits the site, so on a low-traffic site the scheduled time can pass with no visit to trigger the send — and the email goes out late, or not until the next visit.

This is the single most common cause of delayed reminders, and it affects any time-based FlowMattic feature, not just Bookings.

## Fix

**1. Set up a real system cron**
Have your server (or host) ping `wp-cron.php` on a fixed schedule — for example every minute or every five minutes — instead of relying on visitor traffic. Most hosts offer a cron manager for this; the command pings `https://your-site/wp-cron.php`.

We have prepared a detailed step by step guide to help you setup a server side cron using Cloudflare ( FREE account works ) - [Setup Server side cron using Cloudflare](/portal/flowmattic/kb/article/10/delay-or-scheduled-workflows-not-working)

**2. Confirm the reminders are enabled.**
In the calendar's **Notifications & policies** section, confirm **Email reminders** is on, with the **24 hours before** and **1 hour before** timings you expect. A reminder that is off is never scheduled. The post-meeting **Follow-up** is separate — it is a global email that is off by default, so enable **Follow-up** in the **Email notifications** dialog on the Bookings page if you rely on it.

## How to confirm the fix

Make a test booking for a slot far enough ahead that the reminder is scheduled, then confirm the reminder arrives at the expected time once the system cron is running. Reliable cron is what turns scheduled reminders into on-time reminders.

---

# Bookings

Source: https://support.flowmattic.com/kb/article/174/bookings

Bookings is FlowMattic's built-in scheduling module. You create a booking calendar (an "event type"), publish its page on your own domain, and invitees pick a time within the availability you set. Every booking is stored in WordPress, can fire a workflow, and comes with confirmation, reminder, reschedule, cancellation, and follow-up emails out of the box. It is for anyone who would otherwise use Calendly or SavvyCal but wants the data and the automation on their own site.

## How it works

You build a calendar under **FlowMattic → Bookings**, set its availability and options, and share its public URL (`/booking/{slug}/`) or shortcode. Invitees book a slot; each booking is stored and fires a lifecycle event that a workflow can act on.

## What a calendar controls

Each calendar defines:

- **Duration and location** — 15/30/45/60 minutes or custom, and a location of Zoom, Google Meet, Phone call, or In person. For Zoom or Meet, you pick the connected account that hosts the meeting.
- **Availability** — recurring weekly windows (per day) or specific dates/date ranges, with a meeting timezone.
- **Limits** — buffers before and after, minimum notice, how far ahead bookings can be made, and a maximum per day.
- **Invitee questions** — name and email are always collected; you can also require a phone number (for phone-call bookings), add a preparation note, and let invitees bring guests up to a cap of 2, 5, or 10.
- **Notifications & policies** — an always-on confirmation, email reminders 24 hours and 1 hour before the meeting, and whether invitees may reschedule or cancel.
- **Branding** — a logo, the host's name, photo, and title, an accent color, an optional post-booking redirect, and the "Powered by FlowMattic" footer toggle.

## Meeting links

If the location is Zoom or Google Meet and the host has connected that account under **FlowMattic → Connects**, each booking generates a real join link that is added to the confirmation email and calendar invite.

## Single-use links

A calendar can be set to issue a single-use link (`/booking/d/{token}/`) that locks after one booking — useful for a specific prospect or a paid session. A calendar's single-use type is fixed once created.

## Automation

Booking lifecycle events — created, rescheduled, cancelled, completed, no-show, deleted — all fire with the same flat payload, so one workflow can branch on `status` rather than being duplicated per event. A workflow can also create a booking on a calendar with the **Add Booking** action.

![The Bookings dashboard showing a booking calendar and its shareable scheduling link](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-bookings-bookings-dashboard.png)

---

# Bookings Module: Create Scheduling Calendars and Manage Bookings in FlowMattic

Source: https://support.flowmattic.com/kb/article/154/bookings-module-create-scheduling-calendars-and-manage-bookings-in-flowmattic

Bookings is FlowMattic's built-in scheduling module. You create a booking calendar (also called an "event type"), set the hours you're available, and share a page where people pick an open time. Every booking is saved in your own WordPress site, sends confirmation and reminder emails automatically, and can trigger a workflow. It works like Calendly, but the data and the automation live on your site.

You'll find it under **FlowMattic → Bookings**. A registered license key is required; if your license isn't registered yet, the page shows a notice asking you to register it first.

## What a calendar is

A **calendar** is one bookable meeting type — for example "30-minute Discovery Call" or "Free Consultation". Each calendar has its own:

- Public booking page that visitors use to pick a time
- Availability rules (which days and hours are open)
- Meeting duration and location
- Email notifications and branding
- List of bookings people have made on it

You can create as many calendars as you need, each with different settings. The Bookings index page lists all of them with their total and upcoming booking counts.

![The FlowMattic → Bookings index page showing the list of calendars with their colors, public URLs, and total/upcoming booking counts](https://assets.infidesk.support/kb/inline/2026/07/9SGF2osER7Bh92EHheXm8wKvrE4zL7XXufepO5Vb.png).

## Creating a calendar

Click **New Calendar** on the Bookings index. The calendar **Editor** opens with a live preview of the public page on the right that updates as you change settings.

### Calendar type: Regular vs Single-use link

At the top of the editor you choose the calendar **type**:

- **Regular** — a reusable scheduling page. Anyone with the link can keep booking times on it. This is the default.
- **Single-use link** — a one-time link that locks after a single booking. It uses an unguessable token (like `cvqt-hpz-352`) instead of a friendly slug, and lives at a `/d/{token}/` URL. As soon as someone books, the link flips to "Booked" and stops accepting bookings. This is useful for a specific prospect, a paid session, or anything you only want one person to claim.

The type is **fixed once the calendar is created** — you can't convert a regular calendar to single-use or back. Choose before you save.

### Name and slug

Give the calendar a **Name** (shown as the page heading). For regular calendars a URL **slug** is derived automatically from the name; you can edit it. The slug becomes part of the public link, e.g. `/flowmattic-booking/discovery-call/`.

### Duration

**Duration** is how long the meeting lasts, in minutes. You can pick a preset (15, 30, 45, 60) or enter a custom value. The duration also sets how time slots are spaced on the booking page — a 30-minute duration produces slots every 30 minutes within your available hours.

![bookings-event-details](https://assets.infidesk.support/kb/inline/2026/07/Tmk53t8VSmQqdIWpxmrqXBGlUu0Rj7ib35TCxQrl.png)

### Location

**Location** is where the meeting happens. The four options are:

- **Zoom** — generates a real Zoom meeting link for each booking.
- **Google Meet** — generates a real Google Meet link for each booking (created through a Google Calendar event, so it works with any Google account).
- **Phone call** — the invitee provides a phone number when booking, and you call them.
- **In person** — the invitee provides the meeting address when booking.

For **Zoom** or **Google Meet**, a second picker lets you choose which connected account hosts the meeting. The account must first be connected under **FlowMattic → Connects** (for Zoom you also need the Zoom integration installed). If no account is connected, the booking still goes through — it just won't have an auto-generated join link, and emails point the invitee to the booking page instead.

![The Location section of the calendar editor showing the Zoom / Google Meet / Phone call / In person options with the connected-account picker visible for Zoom.](https://assets.infidesk.support/kb/inline/2026/07/2QH2Te5bigJ2EyUu6VmsX8lvYkoQWE98K1f1kVBG.jpg)

## Availability

The **Availability** section controls which dates and times are open for booking. There are two modes:

### Recurring weekly

**Recurring weekly** is a rolling schedule that's always open within your booking window. Under **Weekly hours**, each day of the week (Sunday through Saturday) can be set to **Unavailable** or given one or more time windows. For each day you can:

- **Add hours** — open a start–end window (e.g. 09:00–17:00).
- **Add another window** — add a second block on the same day (e.g. 09:00–12:00 and 14:00–17:00), to model a lunch break.
- **Copy hours to other days** — copy one day's windows onto other selected days, so you don't re-enter the same hours five times.

By default a new calendar is open Monday to Friday, 09:00–17:00.

![The Weekly hours editor with several days set to 09:00–17:00, one day showing two windows, and the "Copy hours to other days" popup open](https://assets.infidesk.support/kb/inline/2026/07/FxSubdR6GgTQfym5vzbl39rlJPGIEWZSD4Pyt8ki.png)

### Specific dates

**Specific dates** opens a single day or a fixed date range instead of a repeating weekly pattern — useful for a one-off event or a limited booking period. You pick the date(s) and a single start and end time that applies across them.

### Timezone

**Timezone** is the time zone your availability is defined in. Set this to *your* time zone. On the public page, visitors can switch to their own time zone and the open slots are re-displayed in it automatically — so set yours and let theirs adapt.

## Buffers, notice, window and limits

These settings (in the same area as Timezone) fine-tune which slots are actually offered:

- **Buffer before** — minutes of padding added before each meeting, so a new booking can't start right up against an existing one. Slots that would overlap the buffer are hidden.
- **Buffer after** — minutes of padding added after each meeting (for example, 15 minutes to write notes before the next call).
- **Min. notice** — the minimum lead time, in hours, before a meeting can start. With 4 hours of notice, no slot less than 4 hours away is offered. Default is 4.
- **Booking window** — how far into the future people can book, in days. Slots beyond this many days from today are not shown. Default is 60.
- **Max per day** — the maximum number of bookings allowed on any single day. Once a day hits this limit, the whole day closes. Leave it blank (shown as "No limit") for unlimited.

All of these are applied when the page computes open slots: it starts from your weekly/specific hours, removes times that conflict with existing bookings (padded by the buffers), removes times inside the minimum-notice window, removes anything past the booking window, and closes days that have hit the per-day cap.

![The settings row showing Timezone, Buffer before, Buffer after, Min. notice, Booking window, and Max per day fields filled in](https://assets.infidesk.support/kb/inline/2026/07/N9uSHOkKzQKvx2ysPP3Ayec854hAuUWROy8L76La.png)

## Invitee questions

Under **Invitee questions** you decide what the booking form collects. The invitee's **Email address** is always required (it's locked on) so confirmation and calendar invites can be sent. The optional ones are:

- **Phone number** — adds a phone field. (For a Phone call location this is required, since you need a number to call.)
- **Notes** — adds a free-text "anything we should know" field.
- **Guests** — lets the invitee add other guest email addresses. When on, a **maximum guests** chip lets you cap how many they can add.

![bookings-invitee-questions](https://assets.infidesk.support/kb/inline/2026/07/xvMxMFebn6w5MRgpJULeihR3HWBj22dlU9dxH8XO.png)

## Notifications & policies

The **Notifications & policies** section controls automatic emails and what invitees can do after booking:

- **Confirmation email** — sent to the invitee the moment they book (always on).
- **Email reminders** — automatic reminder(s) before the meeting.
- **Allow reschedule** — invitees can move their booking to a new time using a link in their email.
- **Allow cancel** — invitees can cancel up to the minimum-notice period.

Under **Booking emails**, you can override the email template used for any of this calendar's emails. By default each one inherits your account-wide template (set under FlowMattic → Settings → Bookings), and you can pick a different saved Email Template just for this calendar.

![bookings-notification-policies](https://assets.infidesk.support/kb/inline/2026/07/OmqqtLSENev0yJuioxcbPWpcVz0bBrxuBwLIU21I.png)

## Branding

The **Branding** section makes the public page feel like yours. It includes a **Logo**, an **Accent color**, optional per-calendar **Host name** and **Host title**, a **Redirect after booking** option, and the **Show FlowMattic branding** toggle. These are covered in detail in the separate "Bookings public booking page" guide.

![bookings-branding](https://assets.infidesk.support/kb/inline/2026/07/DT4xZXySyKUKCcctmqSGUO8dWitVVPRclVLmOr4W.png)

## Saving and sharing

Click **Save**. The editor gives you the calendar's public URL and the `[flowmattic_booking calendar="{slug}"]` shortcode to embed it. The full public-page experience is covered in the "Bookings public booking page" guide.

## The bookings dashboard

Open a calendar and choose its **Bookings** view (the detail screen) to see and manage everything booked on it. At the top, summary stats show counts by status (such as **Confirmed**, **Completed** and **Cancelled**). A status filter lets you narrow the list, and a **Preview page** button opens the live public page.

A booking moves through these statuses: **Confirmed** (or **Pending**), **Completed**, **Cancelled**, and **No-show**. Cancelled and no-show bookings free their time slot back up so others can book it.

### Calendar, List and Board views

Three view buttons switch how bookings are displayed; your choice is remembered:

- **Calendar** — a month grid with each booking shown on its day.
- **List** — a sortable row-by-row list. Each row has a menu with quick actions.
- **Board** — a Kanban-style board with columns by status (Completed, Cancelled, No-show, and so on).

![The booking detail screen showing the Calendar / List / Board view toggle, the status stat counters across the top, and the month calendar populated with bookings](https://assets.infidesk.support/kb/inline/2026/07/Mz4EBCrv5h5PVatFaiSlbXuuqtkh2RXQQrBoPGev.png).

### Managing a single booking

Open any booking (or use the row menu in List view) to act on it. The available actions are:

- **Reschedule** — move the booking to a different open date and time. The new slot is re-checked against your availability rules before it's accepted, so you can't double-book. You can choose whether to notify the attendee and add a custom message.
- **Cancel booking** — cancel it; the slot reopens and a cancellation email can be sent.
- **Mark completed** — record that the meeting happened.
- **Mark no-show** — record that the invitee didn't show up.

Each booking also keeps an **activity log** that records when it was booked, rescheduled, cancelled, completed, or noted — including notes and status changes made by workflows.

![A single booking's detail drawer showing the invitee details, the Reschedule / Complete / Mark as no-show / Cancel booking actions, and the activity log](https://assets.infidesk.support/kb/inline/2026/07/RQmWewJu2ZW5admT42EP2yaGBJwUjll6jCdjhv8E.png).

## How it helps you

With one calendar set up you have a self-serve scheduling page on your own domain. The availability engine guarantees people can only book times you're actually free, respecting your buffers, notice, window and daily cap. Confirmation, reminder, reschedule and cancellation emails go out automatically, and every booking can kick off a FlowMattic workflow — so you can push attendees into a CRM, post to Slack, log to a Table, or anything else FlowMattic can automate.

---

# Booking times look wrong or in the wrong timezone

Source: https://support.flowmattic.com/kb/article/173/booking-times-look-wrong-or-in-the-wrong-timezone

## Symptom

The times offered on the booking page, or the time shown on a confirmed booking, look wrong — an invitee reports a slot at an unexpected hour, or the times do not match your working hours.

## Cause

A booking calendar has one **timezone**, and the public page lets each invitee switch to *their own* timezone. The displayed slots then convert automatically. Most "wrong time" reports come from a mismatch between how the calendar's timezone is set and how the times are being read.

## Fix

**1. Set the calendar timezone to your own timezone.**
In the calendar's **Availability** settings, set the **Timezone** to the timezone you defined your working hours in. Your hours (for example 09:00–17:00) are interpreted in that timezone, and the public page converts them for each invitee.

![The calendar's Availability settings with the Timezone field highlighted](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-bookings-availability-timezone.png)

**2. Let invitees use the timezone switch.**
On the public booking page there is a **Time zone** selector. An invitee in another region should set it to their own timezone; the slots then display in their local time while still mapping to your actual availability. A slot that "looks wrong" is often just being read in a different timezone than the invitee's.

![The public booking page's timezone selector, letting the invitee change the displayed timezone](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-bookings-booking-timezone.png)

**3. Check the WordPress site timezone.**
If every time is off by a consistent offset, confirm the WordPress site timezone (Settings → General) is correct, since scheduled emails and stored times reference it.

## How to confirm

Open the public page and switch the timezone selector between your timezone and a test one. The same slot should shift by the correct offset in each — that confirms the conversion is working and the calendar timezone is set correctly.

---

# Branch Module by FlowMattic

Source: https://support.flowmattic.com/kb/article/102/branch-module-by-flowmattic

The **Branch module** is a powerful workflow component in FlowMattic that allows you to create conditional paths within your workflows. It provides a simplified alternative to the Router module for scenarios where you need to execute different actions based on a single condition with Yes/No outcomes.

## Why Branch When We Have Router?

While both modules handle conditional workflow execution, they serve different purposes and use cases:

### Router Module
- **Multiple Routes**: Requires you to add conditions to each Route separately
- **Complex Workflows**: Ideal for workflows with multiple conditional paths (3+ routes)
- **Individual Route Conditions**: Each route must have its own condition evaluation
- **Use Case**: Perfect for complex decision trees with multiple outcomes

**Example Router Use Case:**
```
- Route A: If user role = "admin" → Execute admin tasks
- Route B: If user role = "editor" → Execute editor tasks  
- Route C: If user role = "subscriber" → Execute subscriber tasks
- Route D: Default → Execute guest tasks
```

### Branch Module
- **Binary Decision**: Evaluates single or multiple conditions with Yes/No outcomes
- **Simplified Setup**: Define conditions only once for the entire branch
- **Cleaner Workflows**: More readable and easier to understand
- **Nested Support**: Can be nested for complex conditions
- **Use Case**: Perfect for binary decisions and conditional logic

**Example Branch Use Case:**
```
- Condition: Has user submitted X field in the form?
- Yes Path → Continue to add the form to CRM
- No Path → Email user to fill the required fields
```

## How Branch Module Works

### 1. Condition Evaluation
The Branch step evaluates a specified condition using the same Filter system as other FlowMattic modules. Based on the outcome:
- **Conditions Meet** → Executes the **Yes path**
- **Conditions Don't Meet** → Executes the **No path**

### 2. Path Execution Logic
- **Yes Path**: When conditions are met, the workflow executes all steps in the Yes path
- **No Path**: When conditions are not met, the workflow skips all Yes path steps and executes the No path
- **Separate Paths**: Yes and No paths are completely independent - each path executes its own set of actions

### 3. Visual Structure

![Workflow Builder ‹ Branch module.png](/storage/kb-images/382ce135e6-inline.png)

**Important**: Each branch path (Yes/No) is a separate execution flow. After executing either the Yes path or the No path, the workflow ends at that branch unless you have additional steps or branches after the current branch structure.

## Setting Up a Branch

### 1. Add Branch Step
1. Add new action step and choose the **Branch** module from the app library into your workflow
2. The system automatically creates:
   - Branch node (main condition)
   - Yes branch route
   - No branch route

### 2. Configure Branch Condition
1. Click on the Branch step to open settings
2. Set up your conditions for evaluation:
   - **Field**: Select the data field to evaluate
   - **Condition**: Choose comparison operator (equals, contains, greater than, etc.)
   - **Value**: Set the value to compare against
   - **Logic**: Choose AND/OR for multiple conditions

### 3. Add Steps to Paths
1. **Yes Path**: Add steps that should execute when conditions are met
2. **No Path**: Add steps that should execute when conditions are not met
3. Each step will automatically be connected to the appropriate path

## Examples and Use Cases

### Example 1: Lead Qualification for Sales Team
```markdown
**Scenario**: Automatically qualify leads based on company size and route them appropriately

**Branch Condition**: 
- Field: `{form.company_size}`
- Condition: `greater than`
- Value: `50`

**Yes Path (Enterprise Lead)**:
1. Add to CRM with "Hot Lead" tag
2. Assign to Senior Sales Rep
3. Send personalized enterprise welcome email
4. Schedule automatic follow-up call
5. Add to enterprise nurture campaign

**No Path (Small Business Lead)**:
1. Add to CRM with "SMB Lead" tag
2. Send automated product demo video
3. Add to self-service onboarding sequence
4. Send pricing information
```

### Example 2: Order Value Processing
```markdown
**Scenario**: Handle orders differently based on order value

**Branch Condition**:
- Field: `{webhook.order_total}`
- Condition: `greater than`
- Value: `100`

**Yes Path (High Value Orders)**:
1. Apply VIP Processing
2. Assign Priority Support
3. Send Premium Thank You Email
4. Add to VIP Customer List

**No Path (Standard Orders)**:
1. Standard Processing
2. Send Standard Confirmation
3. Add to Regular Customer List
```

### Example 3: Customer Support Ticket Routing
```markdown
**Scenario**: Route support tickets based on customer type and urgency

**Primary Branch**: Is Premium Customer?
├── **Yes Path (Premium Customer)**:
│   ├── Assign to dedicated account manager
│   ├── Send priority support acknowledgment
│   └── **Nested Branch**: Is Critical Issue?
│       ├── **Yes Path**: 
│       │   ├── Create urgent ticket
│       │   ├── Send SMS alert to support manager
│       │   └── Start 1-hour response timer
│       └── **No Path (Non-Critical)**:
│           ├── Create standard priority ticket
│           └── Send email with 4-hour response commitment
└── **No Path (Regular Customer)**:
    ├── Assign to general support queue
    ├── Send auto-reply with FAQ links
    └── Create ticket with 24-hour response time

Note: The nested branch only applies to premium customers, allowing for more refined handling of their issues.
```

### Example 4: Error Handling
```markdown
**Scenario**: Handle API response errors gracefully

**Branch Condition**:
- Field: `{api.status_code}`
- Condition: `equals`
- Value: `200`

**Yes Path (Success)**:
1. Process API Data
2. Update Database
3. Send Success Notification

**No Path (Error)**:
1. Log Error Details
2. Send Alert to Admin
3. Show User-Friendly Error Message
4. Retry Logic (if applicable)
```

## Best Practices

### 1. When to Use Branch vs Router
- **Use Branch when**:
  - You have a simple Yes/No decision
  - You want cleaner, more readable workflows
  - You need to evaluate a single condition
  - You're building binary logic flows

- **Use Router when**:
  - You have 3+ different outcomes
  - Each path needs different conditions
  - You need complex multi-route logic
  - You're building complex decision trees

### 2. Condition Design
- **Keep conditions simple**: Focus on single, clear conditions
- **Use descriptive names**: Label your branches clearly
- **Test thoroughly**: Verify both Yes and No paths work correctly
- **Handle edge cases**: Consider what happens with null/empty values

### 3. Nesting Guidelines
- **Limit nesting depth**: Keep to 2-3 levels maximum for readability
- **Document complex logic**: Use clear naming for nested branches
- **Consider alternatives**: Sometimes a Router might be cleaner than deeply nested branches

### 4. Error Prevention
- **Always define both paths**: Ensure both Yes and No paths have appropriate actions
- **Validate data**: Check that the data you're evaluating exists
- **Default values**: Consider what happens when conditions can't be evaluated

## Advanced Features

### 1. Dynamic Conditions
Use dynamic data in your branch conditions:
```markdown
**Condition**: Compare user's current plan with target plan
- Field: `{user.current_plan}`
- Condition: `equals`
- Value: `{webhook.target_plan}`
```

### 2. Multiple Condition Logic
Combine multiple conditions with AND/OR logic:
```markdown
**Complex Condition**: User is premium AND order value > 50
- Condition 1: `{user.plan}` equals `premium`
- Logic: `AND`
- Condition 2: `{order.total}` greater than `50`
```

### 3. Branch Data Access
Access branch execution results in subsequent steps:
```markdown
**Available Data**:
- `{branch2.path_to_execute}` → Returns "yes" or "no"
- `{branch2.condition_met}` → Returns true or false
```

![Workflow Builder ‹ Branch example.png](/storage/kb-images/53af131ee8-inline.png)

## Troubleshooting

### Common Issues

1. **Wrong path executing**: Check that branch conditions are properly configured
2. **Conditions not evaluating**: Verify that the data fields exist and contain expected values
3. **Steps not executing**: Ensure steps are properly connected to the correct branch path
4. **Nested branches failing**: Check the logic flow and ensure parent branch conditions are met

### Debug Tips

1. **Test conditions**: Use the test feature to verify your conditions work as expected
2. **Check data**: Review the workflow execution logs to see actual data values
3. **Simplify first**: Start with simple conditions and add complexity gradually
4. **Use logging**: Add logging steps to track which path is being executed

## Migration from Router

If you're migrating simple binary decisions from Router to Branch:

1. **Identify binary Router patterns**: Look for Routers with only 2 routes
2. **Extract the condition**: Take the condition from the first route
3. **Create Branch**: Replace Router with Branch using that condition
4. **Move steps**: Move Route 1 steps to Yes path, Route 2 steps to No path
5. **Test thoroughly**: Verify the new branch works the same as the original Router

## Conclusion

The Branch module simplifies conditional workflow creation by providing a clean, intuitive way to handle Yes/No decisions. Use it to:

- **Simplify workflows**: Replace complex Router setups for binary decisions
- **Improve readability**: Make your workflows easier to understand and maintain
- **Reduce complexity**: Minimize the number of conditional configurations needed
- **Enhance maintenance**: Make it easier to update and modify conditional logic

By choosing the right conditional module (Branch vs Router) for your specific use case, you can create more efficient, maintainable, and understandable workflows in FlowMattic.

---

# Build FlowMattic Workflows from Claude Desktop, Cursor or Any MCP Client

Source: https://support.flowmattic.com/kb/article/240/build-workflows-with-claude-desktop-cursor-mcp

Your MCP client can do more than read data out of FlowMattic. With **Workflow Tools** switched on, Claude Desktop, Cursor, or any other MCP client can browse the apps installed on your site, look up what each one can actually do, then build a workflow, revise it, and test it — while you describe what you want in plain language.

This guide covers turning it on, connecting a client, and what to expect once it is working.

---

## Before you start

You need:

- FlowMattic **7.2 or newer**, with the **MCP Server** module enabled
- An MCP client — Claude Desktop, Cursor, Claude Code, or anything else that speaks MCP
- An administrator login on the WordPress site

---

## Step 1: Turn on Workflow Tools

These tools are **off by default**. A connected client can create, change and run automations on your site, so nothing is offered until you decide to allow it.

Go to **FlowMattic → MCP Server** and click **Settings** on your server card. Under **Workflow Tools**, tick *Let connected AI clients build workflows*.

![The Workflow Tools setting in Server Settings](https://assets.infidesk.support/products/flowmattic/kb-images/mcp-workflow-tools/02-workflow-tools-toggle.png)

Click **Save Settings**. The change takes effect on your client's next request — you do not need to reconnect.

![Server Settings with Workflow Tools enabled](https://assets.infidesk.support/products/flowmattic/kb-images/mcp-workflow-tools/03-workflow-tools-enabled.png)

> **Leave this off if you only want your AI client reading data.** Your existing tools — the ones you have added for integrations, workflows or queries — keep working exactly as before either way.

---

## Step 2: Connect your client

On the same screen, copy the **MCP Server URL**.

![The MCP Server URL and Connect button](https://assets.infidesk.support/products/flowmattic/kb-images/mcp-workflow-tools/04-connection-panel.png)

**Claude Desktop and ChatGPT** handle authentication for you. Add the server URL as a connector and approve the login prompt when it appears.

**Cursor, Claude Code and other clients** use the secret token instead. In **Server Settings → Authentication**, reveal the **Secret Token** and send it as the `X-FLOWMATTIC-MCP-TOKEN` header.

A typical `mcp.json` entry looks like this:

```json
{
  "mcpServers": {
    "flowmattic": {
      "url": "https://your-site.com/wp-json/flowmattic/v1/mcp-server/YOUR-SERVER-ID",
      "headers": {
        "X-FLOWMATTIC-MCP-TOKEN": "your-secret-token"
      }
    }
  }
}
```

Replace the URL and token with the values from your own Server Settings. Some clients need `/sse` appended to the URL — the note under the URL field on the MCP Server screen tells you when.

---

## Step 3: Ask for a workflow

Once connected, describe what you want. For example:

> Build me a workflow in FlowMattic: when a webhook comes in with an order, wait two hours, then post the order ID to Slack.

Your client will work through several tools to do this. It is worth knowing what they are, because you will see them being called:

| Tool | What it does |
|---|---|
| `wf_list_trigger_apps` | Lists every app that can start a workflow |
| `wf_list_action_apps` | Lists every app that can run as a step |
| `wf_get_app_events` | Returns one app's real triggers and actions |
| `wf_describe_special_nodes` | Explains Router and Filter structure |
| `wf_validate_workflow` | Checks a draft without saving it |
| `wf_create_workflow` | Saves a new workflow |
| `wf_list_workflows` | Finds existing workflows by name |
| `wf_get_workflow` | Reads one back so it can be edited |
| `wf_update_workflow` | Revises a workflow in place |
| `wf_test_run_workflow` | Runs it once and reports what each step did |

The client picks apps and events from your site's real catalogue rather than guessing, which is why it usually calls two or three of these before writing anything.

When it finishes you get a workflow ID and a link straight into the builder.

---

## Step 4: Review it before switching it on

**Every workflow created this way is saved switched off.** Nothing runs until you open it and turn it on yourself.

Open the edit link and check:

- **The step fields.** The client sets what it can from your description, but connection-specific fields — which Slack channel, which mailing list, which account — are yours to pick.
- **The trigger.** If it is a webhook, copy the URL from the trigger step and point your source at it.
- **Router conditions**, if your workflow branches. Confirm each route's condition matches what you meant.

Then switch it on.

---

## Revising a workflow

You do not need to start over to change something. Ask for the change and name the workflow:

> In the "New order alert" workflow, change the delay from two hours to thirty minutes.

The client finds it, reads the current version, edits it, and writes it back to the **same** workflow. It keeps its ID, its webhook URL and its authentication key, so anything already posting to that URL keeps working. A revision that fails validation changes nothing at all.

---

## Testing a workflow

You can ask for a test run:

> Test that workflow with order ID 1234 and a gold tier customer.

You get back what every step sent and what it received, which is usually enough to spot a wrong field or a condition that never matches.

> **A test run really executes.** Emails are sent, APIs are called, records are written. It is not a simulation. A workflow that is switched off still runs for the test, which is the point — you can check it before it goes live — but use real care on workflows that touch customers.

---

## Frequently asked questions

**Do I need an OpenAI or Anthropic key in FlowMattic for this?**
No. That is what "Generate with AI" in the workflow builder uses. Here the thinking happens in the client you have already connected, so FlowMattic needs no AI provider and no Connect.

**Can the AI switch a workflow on?**
No. Workflows are always saved switched off, and nothing in these tools turns one on. That stays a decision you make in the builder.

**Can it change my existing workflows?**
Only if it can find them, and only while Workflow Tools is on. It can list and read workflows on the site and revise them by ID. If that is more than you want, leave the setting off and use your own tools instead.

**Which workflows can it edit?**
Ones built with the v2 builder. Older v1 workflows can be listed, but not read or revised through these tools.

**It built a Router but the branch never runs.**
Check the branch's condition. The field in a route condition must be written as a token in braces — `{webhook1.email}`, not `webhook1.email`. Written without braces it is compared as plain text and never matches.

**Do these tools work with my existing MCP tools?**
Yes. They are added alongside whatever you have already configured; nothing else changes.

---

## Turning it back off

Go to **FlowMattic → MCP Server → Settings** and untick *Let connected AI clients build workflows*. The tools disappear from your client on its next request. Workflows already created stay exactly as they are.

---

# Bulk-generate images with the Iterator

Source: https://support.flowmattic.com/kb/article/175/bulk-generate-images-with-the-iterator

To produce many images from one template — a batch of coupons, a personalised card per signup, a ticket per attendee — place the **Generate Image from Template** action inside an **Iterator** step. Each pass through the loop renders a separate PNG with its own file and attachment.

## Step 1 — Get a list to loop over

Your workflow needs an array to iterate. This might come from a query step (a FlowMattic Table lookup, a database query, an API response) or from a trigger that provides multiple items. Each item should contain the values a single image needs — for example a name and a unique URL.

## Step 2 — Add an Iterator step

1. Add an **Iterator** step to the workflow.
2. Set its **Iteration Array** field to the array from the previous step.

The Iterator runs the steps inside it once per item, exposing the current item's fields to those steps.

![An Iterator step with its Iteration Array field set to an array from an earlier step](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-image-template-wf-iterator-array.png)

## Step 3 — Add Generate Image inside the loop

1. Inside the Iterator, add **Image Builder → Generate Image from Template**.
2. Select your template in the **Image Template** dropdown.
3. Map each token to the **current item's** fields, not the whole list — for example map `attendee_name` to the item's name and `ticket_url` to the item's link.
4. Set an **Output Filename** that includes a unique field, such as `ticket-{item.id}.png`, so files do not overwrite each other.

![The Generate Image action inside the Iterator, with its token fields mapped to the loop's current-item variables](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-image-template-wf-iterator-image-action.png)

## Step 4 — Use each rendered image

Each iteration returns its own rendered image — its URL, file path, and attachment ID. Add steps inside the loop to act on the current image — email it to the current attendee, upload it, or store its URL against the record.

## Performance note

Each render runs through Cloudflare Browser Rendering and takes a few seconds. For large lists this adds up, so factor the total time into any workflow that renders images in bulk, and be mindful of your Cloudflare render quota.

---

# Changing the Email Address on Your FlowMattic Account

Source: https://support.flowmattic.com/kb/article/153/changing-the-email-address-on-your-flowmattic-account

Your email address is the identity your FlowMattic license is tied to — it's where your license key, renewal notices, and account communications are sent. Because of that, FlowMattic does not let you change the email on your account directly from the dashboard. This guide explains why, what our policy allows, and how to request a change.

## Why email changes aren't self-service

Every FlowMattic license is bound to a single account email. If that email could be changed freely, the same license could end up associated with multiple identities — which leads to license conflicts, duplicate or orphaned activations, and renewal or support records that no longer match the right person.

To keep every license cleanly tied to one verified owner, email changes are handled by our support team rather than through self-service. This protects you — your license stays valid and recoverable — and keeps our records accurate.

## Our email change policy

We do allow email changes, within limits that keep accounts secure and prevent abuse:

- **Lifetime license holders** can change their account email **once** for the lifetime of the license.
- **Annual license holders** can change their account email **once per year**.

These limits apply per account. If you have a genuine reason that falls outside the policy — for example, a company domain change or a typo in your original purchase email — reach out and explain the situation, and we'll do our best to help.

## How to request an email change

Since the change can't be made from your dashboard, our support team handles it for you:

1. Contact FlowMattic support — open a ticket from the [support portal](https://support.flowmattic.com), or reply to any existing ticket.
2. Tell us the **current email** on your account and the **new email** you'd like to use.
3. Verify ownership of the account (see below).
4. Once we confirm your details and that the change is within policy, we'll update your account and confirm by email to the new address.

## What to include in your request

To verify that you own the account and to process the change quickly, please include:

- Your **current account email**
- The **new email address** you want to switch to
- Your **order ID or purchase receipt**, or your **license key**

Sending the request from your current account email, where possible, helps us verify ownership faster.

## Frequently asked

**Can I change my email myself from the dashboard?** No. Email changes are handled by our support team to keep every license tied to one verified owner and to avoid license conflicts.

**How many times can I change my email?** Lifetime license holders can change it once for the life of the license. Annual license holders can change it once per year.

**Will changing my email affect my license or active sites?** No. Your license, activations, and renewal date stay exactly as they are — only the email associated with the account changes.

**I entered the wrong email when I purchased. Does that count against my limit?** Contact us and explain — we handle genuine correction requests reasonably and won't penalize an honest typo.

---

# Choose fonts for a PDF template

Source: https://support.flowmattic.com/kb/article/203/choose-fonts-for-a-pdf-template

The PDF Template Builder does not upload custom font files. Instead it ships with a curated set of Google Fonts whose files are bundled with the plugin, and you choose which ones the document uses. Because the files are bundled, the same font renders identically whether the PDF is produced by Cloudflare Browser Rendering or the mPDF fallback engine.

## Available fonts

The catalog is grouped into Sans serif, Serif, and Monospace. It includes Inter, Roboto, Open Sans, Lato, Poppins, Montserrat, Work Sans, Nunito, Raleway, and Oswald (sans serif); Playfair Display, Merriweather, Lora, PT Serif, and IBM Plex Serif (serif); and IBM Plex Mono, JetBrains Mono, Fira Code, and Source Code Pro (monospace). Every one is bundled, so it is safe to use in either rendering engine.

## Set the document's fonts

Fonts are set for the whole document, not per element. Each element uses one of three roles — body text, headings, or monospace — and you assign a font to each role:

1. Open your template in **FlowMattic → PDF Templates**.
2. Open **Page settings** in the right-hand **Inspector** (shown when no element is selected).
3. In the **Fonts** section, set the three dropdowns:
   - **Body** — used for body text, tables, addresses, and most of the page.
   - **Heading** — used for headings, subheadings, and graph titles.
   - **Mono** — used for code-style labels and barcode captions.

![The Page settings Fonts section with the Body, Heading, and Mono dropdowns](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-pdf-template-builder-pdf-page-fonts.png)

## Adjust size, weight, and colour

The font *family* comes from the three roles above. To change size, weight, colour, line height, or letter-spacing, use the **Default Typography** section in Page settings for document-wide defaults, or select an element and adjust its typography in the Inspector.

## Why pick from the bundled list

Only the bundled fonts have font files to embed. If a template referenced a font that is not bundled, the mPDF engine would have no file for it and would substitute the nearest available face, so the output would no longer match your design. Staying within the bundled catalog guarantees the PDF looks the same in the editor, through Cloudflare, and through mPDF.

![The invoice previewed with the chosen Heading (Playfair Display) and Body (Inter) fonts applied](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-pdf-template-builder-pdf-fonts-rendered.png)

---

# Collect leads and schedule meetings from your chatbot

Source: https://support.flowmattic.com/kb/article/219/collect-leads-and-schedule-meetings-from-your-chatbot

Your AI Assistant can do more than answer questions: it can collect contact details and let visitors pick a meeting slot without leaving the chat. Both are configured when you edit an assistant at **FlowMattic → AI Assistants**, on the **Actions** tab.

**Read this first, before you turn lead collection on:** FlowMattic does **not** store captured leads. There is no leads table and no leads screen in the admin. A captured lead is sent straight to a workflow or a webhook and is not saved anywhere else — so **if you have not connected one, the lead is gone.** Set up the routing described at the end of this article *before* you start collecting.

![The Actions tab of an AI Assistant, showing the Event dropdown and the Collect Leads, Link Button and Schedule Meeting sections](https://assets.infidesk.support/products/flowmattic/kb-images/v70/219-chatbot-leads.png)

## Collecting leads

Turn on **Enable lead collection** and choose how it behaves.

### Style

- **Embedded Form** — a small static form appears in the chat with your fields.
- **Chat messages** — the assistant asks for the details naturally in conversation.

### When to ask

- **At the beginning** — before the conversation starts.
- **After a few messages** — once the visitor is engaged.
- **When keywords are used** — you supply the keywords.
- **When chatbot cannot answer** — a good fallback: hand off to a human instead of dead-ending.

**Cadence** controls whether the assistant asks for everything **All at once** or **One at a time**.

### Your form

**Form Title** and **Form Description** default to "Let's get started" and "Please share your details to begin". Change them to suit the offer.

Under **Fields**, add the details you want with a label, a type and whether it is required. Types available: **Text, Email, Phone, Number, Date, Link and Textarea**. A new assistant starts with **Name** and **Email**, both required.

Required fields are enforced, and email fields are checked for a valid address. Phone fields render a telephone input but are not format-checked, so international numbers arrive as typed.

**An important limitation of "Chat messages" style:** conversational capture always collects **first name, last name and email only**. Your custom Fields list applies to the **Embedded Form** style only. If you need a company name or a phone number, use the embedded form.

Once a visitor has given their details, the assistant remembers and will not ask again in that conversation.

## Scheduling meetings

Turn on **Enable meeting scheduling**. There are two quite different modes, and which one you get depends on a single field.

### Mode 1: your existing booking tool (recommended)

Paste a **Calendar Embed URL** — a Calendly, Cal.com or Google Calendar booking link. The assistant then shows a "Schedule a Meeting" button that opens your real booking page inside the chat.

This is the better option for most people, because your existing tool already handles availability, timezones, reminders and confirmation emails.

**Note:** because the booking is completed inside your provider's page, FlowMattic never sees it. **No meeting event reaches your workflows in this mode** — your booking tool sends the confirmations, as it normally would.

### Mode 2: the built-in slot picker

Leave **Calendar Embed URL** empty and the assistant shows its own small calendar plus a list of **Available Time Slots** (9:00 AM to 5:00 PM in 30-minute steps by default, which you can edit). The visitor picks a date and time and gives their name and email.

Be clear-eyed about what this is: **a slot picker, not a booking system.** It does not check whether you are actually free, does not handle timezones, does not prevent two people choosing the same slot, and does not send a confirmation email. Everything beyond capturing the request is up to the workflow you connect.

If you want real scheduling with availability rules and confirmations, use the [FlowMattic Bookings module](/kb/bookings) and paste your booking page link as the Calendar Embed URL. **The chatbot's meeting feature does not read your Bookings calendars automatically** — the two are separate.

### When to show it

**When to show calendar** is either **Always show in chat** or **When certain keywords are used** (default keywords: meeting, schedule, call, book, appointment).

## Routing leads and meetings into a workflow

This is the part that makes the data useful — and the part that is easy to miss.

**Use the "FlowMattic Chatbot" trigger app in the Workflow Builder.** Create a workflow, choose **FlowMattic Chatbot** as the trigger, and pick the event:

- **Lead Captured**
- **Meeting Scheduled**
- **AI Response Received**
- **Chat Started**
- **Link Button Clicked**

Then do whatever you need with it — add the person to your CRM, send yourself an email, write a row to a table, notify Slack.

**A point of confusion worth getting straight.** The Actions tab has two different things on it. The **Collect Leads** and **Schedule Meeting** sections are where you turn those features on — that is where you have been working. Further down, there is a separate **workflow/webhook trigger** section with an Event dropdown, and that dropdown offers only **Chatbot Response Generated** and **Chat Started**. Lead Captured and Meeting Scheduled are **not** in it. So configure the features on the Actions tab, but route their data using the FlowMattic Chatbot trigger app in the Workflow Builder, not that dropdown.

### What the workflow receives

Every event includes the conversation context: the visitor's latest message, the assistant's latest reply, the thread and chatbot IDs, and — if the visitor is logged in — their user ID and email.

**Lead Captured** adds the submitted fields, keyed by your field labels.

**Meeting Scheduled** adds the meeting details, plus ready-to-map fields so you do not have to parse anything: `meeting_date`, `meeting_time`, `meeting_datetime`, `meeting_date_ymd`, `booker_name` and `booker_email`.

## Troubleshooting

**Leads are being captured but nothing happens.** Check that the connected workflow is switched **on** — a workflow that is off is skipped silently.

**A webhook is not receiving anything.** Webhook calls are sent without waiting for a response and are not retried, so a failing endpoint fails quietly with nothing shown in the chat. Test the URL independently before relying on it.

**The assistant never offers the form or calendar.** Both are offered by the AI when it judges them relevant, so results vary with the model and the conversation. Make the trigger explicit — use keyword triggers, or "At the beginning" for leads — rather than relying on the assistant to decide.

**It asks for details but not the meeting.** Lead collection deliberately comes first; the assistant will not offer the calendar while it still needs contact details.

**The assistant misreads a word as a booking request.** Keyword triggers match words like "book", which can appear in unrelated sentences. Choose distinctive keywords such as "schedule a call" rather than single common words.

## Related

- [How to Set Up Your AI Assistant Chatbot in FlowMattic](/kb/ai-assistant-setup-guide)
- [Customize your chatbot's appearance](/kb/customize-your-chatbots-appearance)
- [Managing Content Sources for Your AI Assistant Chatbot](/kb/ai-assistant-content-sources)

---

# Complete Guide: Integrating Calendly with FlowMattic Connects

Source: https://support.flowmattic.com/kb/article/97/complete-guide-integrating-calendly-with-flowmattic-connects

This guide will walk you through the process of creating a Calendly OAuth application and connecting it with FlowMattic Connects, enabling you to automate your Calendly workflows within WordPress. The integration allows FlowMattic to interact with your Calendly account programmatically, opening up possibilities for automated scheduling, event management, and data synchronization.

## Prerequisites

Before beginning this integration, ensure you have:
- A Calendly account with appropriate permissions to create OAuth applications
- Access to your WordPress dashboard with FlowMattic installed and activated
- Administrative privileges in both systems

## Part 1: Creating Your Calendly OAuth Application

The first phase involves setting up an OAuth application in Calendly's developer console. OAuth (Open Authorization) is a secure protocol that allows FlowMattic to access your Calendly data without storing your password directly.

### Step 1: Access the Calendly Developer Console

Navigate to the Calendly developer console at [https://developer.calendly.com/console/apps](https://developer.calendly.com/console/apps). You'll need to log in with your Calendly credentials if you haven't already. This console is where Calendly allows third-party applications to register for API access.

### Step 2: Create a New OAuth Application

Once in the developer console, look for the option to create a new app. You'll be presented with a form that requires several important pieces of information.

![Calendly OAuth App Creation Form - Step 1](/storage/kb-images/4518abfa94-inline.png)

**Configuring Your Application Details:**

For the **Name of app** field, choose something descriptive that will help you identify this connection later. "FlowMattic Integration" works well, but you might want to be more specific if you plan to create multiple integrations.

When selecting the **Kind of app**, choose "Web" since FlowMattic operates as a web-based service. The "Native" option is intended for desktop or mobile applications, which doesn't apply to our WordPress-based integration.

For the **Environment type**, select "Production" if you're setting up a live integration. The "Sandbox" option is useful for testing but won't work with real Calendly data, so production is typically the right choice for FlowMattic integrations.

The **Redirect URI** is crucial - this is where Calendly will send users after they authorize your application. Enter exactly: `https://api.flowmattic.com/calendly`

This URI is specifically configured by FlowMattic to handle the OAuth callback process. Any typo here will cause the authentication to fail, so double-check this entry carefully.

### Step 3: Save and Retrieve Your Credentials

After clicking "Save & Continue", Calendly will generate your application and provide you with essential credentials.

![Calendly OAuth Credentials - Step 2](/storage/kb-images/6aad43dad2-inline.png)

You'll see three important pieces of information:

1. **Client ID**: This is your application's public identifier. Think of it as your app's username that identifies it to Calendly.

2. **Client Secret**: This is your application's private key - treat it like a password. Never share this publicly or commit it to version control. FlowMattic will store this securely encrypted in your WordPress database.

3. **Webhook Signing Key**: While not needed for basic OAuth integration, this key is used to verify that webhook notifications genuinely come from Calendly if you plan to use real-time event notifications later.

Copy both the Client ID and Client Secret immediately, as the Client Secret won't be shown again after you leave this page. If you lose it, you'll need to generate a new one, which will invalidate the old secret.

## Part 2: Configuring FlowMattic Connects

Now that your Calendly application is ready, we'll configure FlowMattic to use these credentials to establish a connection.

### Step 4: Access FlowMattic Connects

In your WordPress admin dashboard, navigate to FlowMattic → Connects. This section manages all your external service integrations.

![FlowMattic Connects Dashboard](/storage/kb-images/b319109a03-inline.png)

The Connects feature in FlowMattic serves as a centralized authentication manager. It stores your API credentials securely and handles the OAuth flow, so you don't need to manage tokens manually or worry about token refresh cycles.

### Step 5: Add Calendly Integration

Click the "Connect Integration" button (highlighted with the arrow in the screenshot). This opens the integration selection modal.

![Integration Selection Modal](/storage/kb-images/65a3d960c8-inline.png)

In the search field or by scrolling through the available integrations, locate and click on "Calendly". FlowMattic supports numerous integrations, so you might find it faster to use the search function at the top of the modal.

### Step 6: Configure the Calendly Connection

You'll now see the Calendly connection configuration form.

![Calendly Connection Configuration](/storage/kb-images/25f0eec411-inline.png)

Let's understand each field:

**Connect Name**: This helps you identify the connection, especially useful if you manage multiple Calendly accounts. Keep the default "Calendly" or customize it to something like "Main Calendly Account" or "Team Scheduling Account".

**Callback URL**: This field is pre-filled with `https://api.flowmattic.com/calendly` and should match exactly what you entered in the Calendly developer console. This field is typically locked to prevent accidental changes.

**Client ID**: Paste the Client ID you copied from the Calendly developer console. This tells Calendly which application is requesting access.

**Client Secret**: Paste the Client Secret here. FlowMattic will encrypt this before storing it in your database for security.

After entering both credentials, click "Save Connect & Authenticate". This button performs two actions: it saves your credentials locally and initiates the OAuth authorization flow with Calendly.

### Step 7: Authorize FlowMattic to Access Your Calendly Account

After saving, you'll be redirected to Calendly's authorization page.

![Calendly Authorization Page](/storage/kb-images/badd9054ff-inline.png)

This page is hosted by Calendly, not FlowMattic, which is an important security feature of OAuth. Here, Calendly asks you to confirm that you want to allow "FlowMattic Integration" (or whatever you named your app) to access your account and manage your Calendly events.

Review the permissions being requested - these typically include reading and writing calendar events, accessing user information, and managing scheduling links. Click "Connect to Calendly" to grant these permissions.

After authorization, Calendly will redirect you back to FlowMattic with an authorization code. FlowMattic automatically exchanges this code for access tokens behind the scenes, completing the connection setup.

## Part 3: Using Your Calendly Connection in Workflows

With the connection established, you can now use Calendly actions and triggers in your FlowMattic workflows.

### Step 8: Create or Edit a Workflow

Navigate to FlowMattic → Workflows and either create a new workflow or edit an existing one where you want to add Calendly functionality.

### Step 9: Add a Calendly Action

When adding an action step to your workflow, select Calendly as the application. You'll see various action options like "Create One-Off Meeting", "Cancel Event", "Get Event", and more.

![Calendly Action Configuration](/storage/kb-images/c637924b23-inline.png)

Notice the "Choose Connect Account" dropdown. This is where your previously configured connection appears. Select your Calendly connection from the dropdown (it will show as "Calendly" with an ID number, like "ID: 208" in the example).

The connection you select here determines which Calendly account the action will interact with. This separation between connection management and workflow configuration means you can easily switch between different Calendly accounts without re-entering credentials, and multiple workflows can share the same connection.

## Troubleshooting Common Issues

If you encounter problems during setup, here are the most common issues and their solutions:

**Authentication Fails**: Double-check that the Redirect URI in your Calendly app settings exactly matches `https://api.flowmattic.com/calendly`. Even a small difference like http vs https or a trailing slash will cause failure.

**Connection Appears But Doesn't Work**: This often indicates the Client Secret was copied incorrectly. Try deleting the connection in FlowMattic Connects and recreating it, carefully copying the credentials again.

**Permissions Error**: Ensure your Calendly account has the necessary permissions. Some Calendly features require specific subscription levels.

## Security Best Practices

Protecting your integration is crucial for maintaining the security of both your WordPress site and Calendly account:

1. **Regularly rotate your Client Secret**: Consider updating your Client Secret periodically through the Calendly developer console, then updating the connection in FlowMattic.

2. **Monitor usage**: Check your Calendly developer console periodically to review API usage and ensure there's no unexpected activity.

3. **Limit access**: Only give WordPress administrator access to users who need to manage these integrations.

4. **Use HTTPS**: Ensure your WordPress site uses HTTPS to encrypt all communication between your server and external services.

## Next Steps

With your Calendly integration complete, you can now:
- Create automated workflows that schedule meetings based on form submissions
- Sync Calendly events with other systems like CRMs or email marketing platforms
- Send custom notifications when meetings are booked or cancelled
- Generate reports on meeting patterns and scheduling efficiency

The connection you've established serves as the foundation for all these automations, handling the complex authentication process so you can focus on building powerful workflows that save time and reduce manual work in your scheduling processes.

---

# Complete Guide: WooCommerce Abandoned Cart Recovery with FlowMattic

Source: https://support.flowmattic.com/kb/article/106/complete-guide-woocommerce-abandoned-cart-recovery-with-flowmattic

## **The Ultimate Guide to Recovering Lost Sales and Increasing Your Revenue**

Transform abandoned carts into completed sales with FlowMattic's powerful automation. This guide covers everything you need to know to set up, test, and optimize your abandoned cart recovery system.

---

###  What You'll Need Before Starting

✅ **FlowMattic Plugin** - Installed and activated
✅ **WooCommerce Plugin** - Installed and activated
✅ **At least one product** in your store
✅ **Email service** configured (Gmail, SMTP, or any email provider)
✅ **10 minutes** to follow this guide

> **Important:** No coding or technical knowledge required. Everything is done through easy-to-use menus!

---

###  Part 1: Understanding Abandoned Cart Recovery

#### What is Cart Abandonment?
When a customer adds items to their cart but leaves your store without completing the purchase, that's cart abandonment. Studies show that 70% of online shoppers abandon their carts!

#### How FlowMattic Helps
FlowMattic automatically:
- **Detects** when customers abandon their carts
- **Tracks** their cart contents and contact information
- **Triggers** your recovery workflows
- **Sends** personalized recovery emails with discount coupons
- **Monitors** cart status (abandoned, recovered, or completed)

#### Available Features
1. **Cart Abandonment Detection** - Automatically detects abandoned carts
2. **Recovery Email Sending** - Send beautiful recovery emails
3. **Discount Coupon Creation** - Generate attractive offers
4. **Cart Status Checking** - Monitor cart recovery progress
5. **Customer Data Capture** - Collect valuable customer insights

---

###  Part 2: Setting Up Your First Abandoned Cart Recovery Workflow

#### Step 1: Create Your Recovery Workflow

1. **Go to FlowMattic**
   - In your WordPress admin, click **FlowMattic** → **Workflows**
   - Click **"Add New Workflow"**

2. **Name Your Workflow**
   - Enter: `"Abandoned Cart Recovery - 30 Minutes"`
   - This helps you identify the workflow later

3. **Set Up the Trigger**
   - **Choose Application:** Select **"WooCommerce"**
   - **Choose Trigger:** Select **"New Cart Abandonment"**
   - **Save** your trigger

#### Step 2: Add Recovery Actions

##### Option A: Send Recovery Email (Recommended for Beginners)

1. **Add Email Action**
   - Click **"Add Step"**
   - **Choose Application:** Select **"Email"**
   - **Choose Action:** Select **"Send Email"**

2. **Configure Your Recovery Email**
   - **To:** Use `{customer_email}` (this gets the customer's email automatically)
   - **Subject:** `"Don't forget your items! Complete your order now"`
   - **Email Content:** Use this template:

```
Hi {first_name},

You left some amazing items in your cart! Don't let them get away.

🛒 Your Cart Details:
• Total Value: ${cart_total}
• Items: {cart_items}

Complete your order now and get these items before they're gone!

👉 [Complete My Order]({recovery_url})

Need help? Reply to this email and we'll assist you right away.

Best regards,
Your Store Team
```

3. **Save** your email action

##### Option B: Send Email with Discount Coupon (Advanced)

1. **First, Create a Coupon**
   - Add another step
   - **Choose Application:** Select **"WooCommerce"**
   - **Choose Action:** Select **"Create Coupon"**
   - **Configure Coupon:**
     - **Coupon Code:** `SAVE10-{workflow_id}`
     - **Discount Type:** Select **"Percentage"**
     - **Coupon Amount:** `10`
     - **Expiry Days:** `7`
   - **Save** the coupon action

2. **Then, Send Email with Coupon**
   - Add another step for **Email**
   - **Email Content:** Include the coupon:

```
Hi {first_name},

We noticed you left some items in your cart. Here's a special 10% discount to complete your order!

🎉 Your Exclusive Coupon: {coupon_code}

🛒 Your Cart: ${cart_total}
Items: {cart_items}

👉 [Complete Order with 10% Off]({recovery_url})

This offer expires in 7 days, so don't wait!

Happy Shopping!
```

#### Step 3: Activate Your Workflow

1. **Save Your Workflow** - Click the save button
2. **Turn On Your Workflow** - Toggle the switch to **"Active"**
3. **Done!** Your abandoned cart recovery is now live

---

###  Part 3: Testing Your Setup (5-Minute Test)

**Important:** For testing, temporarily change your abandonment threshold to 5 minutes so you don't have to wait 30 minutes.

#### Quick Test Setup

1. **Adjust Threshold for Testing**
   - Go to **FlowMattic** → **Settings** → **WooCommerce**
   - Change **"Cart Abandonment Threshold"** to **5 minutes**
   - **Save** settings

2. **Test Your Workflow**
   - Open your store in a new browser tab
   - **Add a product to cart**
   - Go to **checkout page** and **enter your email address**
   - **Leave the page** without completing the purchase
   - **Wait 5 minutes**
   - **Check your email** for the recovery message

3. **Capture Response Data**
   - In FlowMattic, go to your workflow
   - Click **"Capture Response"**
   - **Complete the test** (add to cart, enter email, abandon)
   - The system will capture real data for you to use

4. **Reset Threshold**
- **Don't forget** to change the threshold back to **30 minutes** after testing for optimal results. You can customize this threshold based on your business needs - some stores use 15 minutes for faster recovery, while others prefer 60 minutes for customers who take longer to decide. Experiment to find what works best for your audience!

#### What Should Happen During Testing

✅ **Email received** within 5 minutes
✅ **Customer email** populated correctly
✅ **Cart total** showing the right amount
✅ **Recovery URL** works and restores the cart
✅ **Coupon code** works (if you added the coupon action)

#### Available Cart Variables

When creating your email templates, you can use these dynamic variables:

- **`{first_name}`** - Customer's first name
- **`{last_name}`** - Customer's last name
- **`{customer_name}`** - Customer's full name
- **`{customer_email}`** - Customer's email address
- **`{cart_items}`** - Complete list of cart items with details
- **`{cart_total}`** - Total cart value (including currency)
- **`{cart_url}`** - Direct link to cart page
- **`{recovery_url}`** - Special recovery link that restores the cart
- **`{coupon_code}`** - Coupon code (when using Create Coupon action)

These variables works best in all - FlowMattic Email Templates and in your custom email content while sending an email with custom content with Send Abandoned Cart Email action.

---

###  Part 4: Advanced Workflows and Strategies

#### Sequential Recovery Emails

Create a single workflow with timed delays for progressive recovery:

**Single Workflow with Sequential Steps:**

1. **Trigger: Cart Abandonment (30 minutes)**
	- Automatically starts when cart is abandoned

2. **Step 1: First Reminder Email**
	- **Subject:** "Did you forget something?"
	- **Content:** Gentle reminder with cart contents
	- **Tone:** Helpful, non-pushy

3. **Step 2: Delay Action (24 hours)**
	- **Choose Application:** Select **"Delay"**
	- **Delay Duration:** Set to **24 hours**

4. **Step 3: Second Reminder Email**
	- **Subject:** "Last chance for your items!"
	- **Content:** Add urgency + 5% discount coupon
	- **Tone:** More urgent, includes incentive

5. **Step 4: Delay Action (48 hours)**
	- **Choose Application:** Select **"Delay"**
	- **Delay Duration:** Set to **48 hours** (total 72 hours from start)

6. **Step 5: Final Attempt Email**
	- **Subject:** "We'll miss you! Here's 15% off"
	- **Content:** Strong discount + limited time offer
	- **Tone:** Final opportunity with best offer

**Timeline Example:**
- **Cart abandoned:** 2:00 PM Monday
- **First email sent:** 2:30 PM Monday (30 min after abandonment)
- **Second email sent:** 2:30 PM Tuesday (24 hours later)  
- **Final email sent:** 2:30 PM Thursday (48 hours after second email)

**Pro Tips for Sequential Recovery:**
- **Add Conditions:** Use "Check Cart Status" before each email to avoid sending to completed carts
- **Escalating Incentives:** Start with no discount, then 5%, then 15%
- **Progressive Urgency:** Increase urgency in tone and messaging with each email
- **Stop on Success:** The workflow automatically stops if the customer completes their purchase

This approach is much more efficient than managing multiple separate workflows and ensures a cohesive customer experience with progressively compelling offers.

#### Cart Value-Based Recovery

**High-Value Carts ($100+)**
- Immediate personal attention
- Phone call follow-up
- WhatsApp follow-ups
- Higher discount percentages

**Low-Value Carts (Under $50)**
- Standard email sequence
- Free shipping offers
- Product recommendations

---

###  Part 5: Using Cart Status Checking

Monitor your recovery success with the **Check Cart Status** action.

#### How to Add Cart Status Monitoring

1. **Add Status Check Action**
   - In any workflow with Cart Abandonment trigger, add a new step
   - **Choose Application:** **"WooCommerce"**
   - **Choose Action:** **"Check Cart Status"**
   - **Cart ID:** Use `{cart_id}` from your trigger

2. **What You'll Get**
   - **Current Status:** abandoned, recovered, or active
   - **Cart Contents:** All product details
   - **Customer Information:** Email, name, contact details
   - **Timing Data:** When abandoned, last activity
   - **Recovery Information:** If and when recovered

3. **Use Cases for Status Checking**
   - **Avoid Duplicate Emails:** Don't send if already recovered
   - **Analytics Tracking:** Monitor recovery rates
   - **Conditional Logic:** Different actions based on status
   - **Customer Service:** Quick cart lookup for support

---

### Part 6: Email Best Practices

#### Subject Line Tips
✅ **Good:** "Your cart is waiting for you!"
✅ **Good:** "Complete your order + get 10% off"
✅ **Good:** "Don't miss out on these items"
❌ **Avoid:** "URGENT!!! BUY NOW!!!"
❌ **Avoid:** "You abandoned your cart"

#### Email Content Guidelines

**Start with Personalization**
- Use `{first_name}` or `{customer_email}`
- Reference specific products they viewed with `{cart_items}`

**Create Urgency (But Don't Overdo It)**
- "Limited time offer"
- "Only 3 left in stock"
- "Sale ends tomorrow"

**Make it Easy**
- Clear call-to-action buttons
- Direct links to cart: `{recovery_url}`
- Simple, clean design

**Add Value**
- Customer reviews
- Free shipping offers
- Related product suggestions

#### Mobile-Friendly Tips
- Short subject lines (under 50 characters)
- Large, clickable buttons
- Concise, scannable content
- Test on different devices

---

###  Part 7: Creating Effective Discount Strategies

#### Discount Types That Work

**Percentage Discounts**
- 10% for first-time customers
- 15% for returning customers
- 20% for high-value carts

**Fixed Amount Discounts**
- $5 off orders over $50
- $10 off orders over $100
- $25 off orders over $200

**Free Shipping**
- Very effective for low-margin products
- Great for international customers
- Combine with minimum order amounts

**Buy One Get One (BOGO)**
- Perfect for inventory clearance
- Increases average order value
- Creates excitement

#### Coupon Best Practices

**Expiration Dates**
- 7 days: Creates urgency
- 14 days: Gives flexibility
- 30 days: For high-consideration purchases

**Usage Limits**
- One per customer: Prevents abuse
- Limited quantity: Creates scarcity
- Minimum order amounts: Protects margins

**Coupon Codes**
- Keep them simple: SAVE10, WELCOME15
- Make them memorable: COMEBACK20
- Use auto-generation: `SAVE10-{workflow_id}`

---

### ❓ Frequently Asked Questions (FAQ)

#### General Setup Questions

**Q: Do I need any coding knowledge to set up abandoned cart recovery?**
A: No! FlowMattic's visual workflow builder makes it easy for anyone to set up cart recovery without any coding.

**Q: How long does it take to set up?**
A: About 10-15 minutes for a basic recovery workflow. Advanced setups with multiple emails might take 30-45 minutes.

**Q: Will this work with my theme?**
A: Yes! The abandoned cart functionality works with any WordPress theme that supports WooCommerce.

**Q: Does this slow down my website?**
A: No. FlowMattic runs in the background and doesn't affect your site's front-end performance.

#### Cart Detection Questions

**Q: When exactly is a cart considered "abandoned"?**
A: A cart is abandoned when a customer adds items and provides their email address but doesn't complete the purchase within 30 minutes (default setting).

**Q: What if a customer doesn't enter their email?**
A: Recovery emails can only be sent to customers who provide their email address. Encourage email collection at checkout for best results.

**Q: Do abandoned carts work for guest customers?**
A: Yes! As long as the customer enters their email address during checkout, the system can track and recover their cart.

**Q: What happens if a customer completes their order after abandoning?**
A: The system automatically updates the cart status to "completed" and you can use this status so the workflows won't send recovery emails for that cart.

#### Email and Recovery Questions

**Q: How many recovery emails should I send?**
A: Start with 2-3 emails: one at 30 minutes, one at 24 hours, and one final attempt at 72 hours. Monitor performance and adjust.

**Q: What's the best time to send recovery emails?**
A: This varies by audience, but generally 10 AM - 2 PM and 6 PM - 8 PM work well. Test different times for your specific customers and according to your timezone.

**Q: Can I customize the email templates?**
A: Yes! You have full control over email content, design, and timing in FlowMattic's workflow builder and Email Template builder.

**Q: Does the recovery URL expire?**
A: Recovery URLs remain valid until the cart is completed or manually cleared. We recommend setting reasonable expectations (like 7-14 days).

#### Discount and Coupon Questions

**Q: What discount percentage works best?**
A: Start with 10-15% for most products. Test different percentages and monitor your profit margins to find the sweet spot.

**Q: Should I offer discounts immediately or only in later emails?**
A: Try both approaches! Some businesses start with a simple reminder and add discounts in follow-up emails to create escalating incentive.

**Q: Can customers use multiple coupons?**
A: You can control this in WooCommerce coupon settings. Generally, allowing one coupon per order prevents abuse while still being generous.

**Q: What if I don't want to offer discounts?**
A: You can focus on other incentives like free shipping, limited-time availability, customer reviews, or personalized product recommendations.

#### Technical Questions

**Q: Does this work with other plugins?**
A: FlowMattic is designed to work with most WordPress plugins. Contact support if you encounter conflicts with specific plugins.

**Q: What happens to old abandoned cart data?**
A: The system automatically cleans up old cart data after 30 days to keep your database optimized. You can customize this time in settings as per your requirements.

**Q: Is my customer data secure?**
A: Yes. All data is stored securely in your WordPress database and follows WordPress security standards. Ensure your site has proper security measures in place.

**Q: Can I use this with WooCommerce subscriptions?**
A: Yes! The abandoned cart feature works with subscription products, variable products, and all WooCommerce product types.

#### Troubleshooting Questions

**Q: My workflow isn't triggering. What should I check?**
A: Verify that:
- Your workflow is active
- WooCommerce is properly installed
- Customers are entering email addresses
- You're waiting the full threshold time (30 minutes default)

**Q: Emails aren't being sent. What's wrong?**
A: Check:
- Your email settings in WordPress
- Spam folders
- Email delivery logs in your SMTP plugin or service
- WordPress email functionality (try a test email)

**Q: The recovery URL doesn't restore the cart. Why?**
A: This can happen if:
- The customer's session expired
- WooCommerce sessions are not properly configured
- Browser cookies are disabled
- The cart contents changed (out of stock, etc.)

**Q: Can I test without waiting 30 minutes?**
A: Yes! For testing purposes, you can temporarily change the abandonment threshold to 5 minutes in FlowMattic settings. Remember to change it back afterward.

#### Integration Questions

**Q: Can I connect this to my email marketing platform?**
A: Yes! FlowMattic integrates with popular email platforms like Mailchimp, MailerLite, and others for comprehensive marketing automation.

**Q: Does this work with SMS notifications?**
A: Yes! You can add SMS actions using FlowMattic's Twilio or WhatsApp integrations for multi-channel recovery campaigns.

**Q: Can I sync abandoned cart data to my CRM?**
A: Yes! FlowMattic supports many CRM integrations including FluentCRM, HubSpot, and others for complete customer journey tracking.

**Q: What about social media retargeting?**
A: You can use FlowMattic's webhook actions to send abandoned cart data to Facebook, Google Ads, or other platforms for retargeting campaigns.

---

### 🛠️ Troubleshooting Common Issues

#### Issue: No Abandoned Cart Emails Being Sent

**Possible Causes:**
- Workflow not activated
- Customer didn't provide email address
- Not enough time passed (check threshold setting)
- Email delivery issues

**Solutions:**
1. Verify workflow is **"Active"** in FlowMattic
2. Test with a logged-in user account
3. Check **FlowMattic** → **Task History** for errors
4. Test email delivery with a simple "Send Email" in FlowMattic Abandoned Cart under WooCommerce menu
5. Check spam folders and email filters

#### Issue: Recovery URL Not Working

**Possible Causes:**
- Customer session expired
- Browser cookies disabled
- Cart contents changed (products removed/out of stock)

**Solutions:**
1. Test immediately after abandonment
2. Ensure customers accept cookies
3. Check product availability
4. Test with simple products first
5. Verify WooCommerce session settings

#### Issue: Wrong Cart Data in Emails

**Possible Causes:**
- Multiple browser sessions
- Cached data issues
- Product variations causing problems

**Solutions:**
1. Clear browser cache and cookies
2. Test in incognito/private mode
3. Use simple products for testing
4. Check cart contents in WooCommerce admin
5. Verify workflow trigger data

#### Issue: Duplicate Emails Being Sent

**Possible Causes:**
- Multiple workflows for same trigger
- Workflow running multiple times
- Cron job issues

**Solutions:**
1. Check for duplicate workflows
2. Add conditions to prevent re-triggering
3. Use cart status checking to avoid duplicates
4. Monitor workflow execution logs
5. Set proper email frequency limits

#### Issue: Low Recovery Rates

**Possible Causes:**
- Poor email content
- Wrong timing
- Weak incentives
- Technical delivery issues

**Solutions:**
1. A/B test different subject lines
2. Adjust email timing (try different hours)
3. Increase discount percentages
4. Improve email design and copy
5. Check email deliverability scores

### 📞 Getting Help and Support

#### FlowMattic Resources
- **Documentation:** Complete guides and tutorials
- **Support Forum:** Community help and discussions
- **Video Tutorials:** Step-by-step visual guides
- **Template Library:** Pre-built workflow templates

#### Best Practices for Getting Help
1. **Check the FAQ first** - Many questions are answered above
2. **Be specific** - Include workflow screenshots and error messages
3. **Test thoroughly** - Try the troubleshooting steps before asking for help
4. **Share details** - WordPress version, plugin versions, and specific issues

---

**🎯 Congratulations!** You now have everything you need to implement a successful abandoned cart recovery system. Start with the basics, test thoroughly, and gradually add advanced features as you grow more comfortable with the system.

**Remember:** The key to success is consistent testing, monitoring, and optimization. What works for one store might not work for another, so always test and adjust based on your specific audience and products.

**Happy selling! 🚀**

---

# Comprehensive Guide to Setting Up Google Console Project for Calendar API Integration

Source: https://support.flowmattic.com/kb/article/85/comprehensive-guide-to-setting-up-google-console-project-for-calendar-api-integration

### Overview
This guide provides a step-by-step process for setting up a Google Cloud project and configuring it to integrate the Google Calendar API. It includes instructions for enabling the API, configuring OAuth credentials, and completing the authentication process.

### Steps to Set Up Google Console Project

#### 1. Create a Google Cloud Project
- Log in to the [Google Cloud Console](https://console.cloud.google.com/).
- Click on the Select a project dropdown at the top of the page, then click on New Project.
- Provide the following details:
-- **Project Name:** Enter a meaningful name (e.g., “Google Calendar API Integration”).
-- **Location:** Leave it as “No organization” if you do not have an organization.
- Click Create. Google will redirect you to the project dashboard

#### 2. Enable Google Calendar API
- Navigate to **[APIs & Services > Library](https://console.cloud.google.com/apis/library)**.
- In the API Library:
-- Search for **Google Calendar API**, click on it, and then click **Enable**.

#### 3. Configure the OAuth Consent Screen
- Go to **[APIs & Services > OAuth consent screen](https://console.cloud.google.com/apis/credentials/consent)**.
- Choose **External** as the user type and click Create.
- Fill out the following details:
-- **App Name:** Enter a meaningful name (e.g., “FlowMattic Google Integration”).
-- **User Support Email:** Enter your email address.
-- **App Logo:** Optional, but you can upload a logo if desired.
-- **Authorized Domains:** Add the following domain: flowmattic.com
-- **Developer Contact Information:** Enter your email address.
- Click Save and Continue.

#### 4. Add Scopes
- On the “[Scopes](https://console.cloud.google.com/auth/scopes)” screen:
- Click Add or Remove Scopes.
-- Select the following scopes from the list or manually add them:
  - `https://www.googleapis.com/auth/calendar`
- Click Update and then Save and Continue
![Image 2025-08-13 at 2.23.23 AM.jpeg](/storage/kb-images/e0159b5669-inline.png)

#### 5. Add Test Users
- On the "[Audience](https://console.cloud.google.com/auth/audience)" tab, under  “**Test Users**” section:
-- Click **Add Users**.
-- Enter the email addresses of the Google accounts you will use to test the integration (e.g., your own or any users who will authenticate the connection).
-- You can add multiple email addresses, separated by commas or one per line.
- Click **Save and Continue**.

![Add Test Users.png](/storage/kb-images/eca60ff313-inline.png)

#### 6. Create OAuth 2.0 Credentials
- Go to **[APIs & Services > Credentials](https://console.cloud.google.com/apis/credentials)**.
- Click **+ Create Credentials** and select **OAuth Client ID**.
- On the **Create OAuth Client ID** screen:
  - Select **Web Application** as the application type.
  - Provide a name for the credential.
  - Add the callback URL to the **Authorized Redirect URIs** : 
  - `https://api.flowmattic.com/google/calendar`
- Save the credentials and securely store the **Client ID** and **Client Secret**.

![Image 2025-08-13 at 2.18.22 AM.jpeg](/storage/kb-images/86ca11a85f-inline.png)

#### 7. Configure Connect in FlowMattic
- Navigate to the **FlowMattic -> Connects** settings in your WordPress dashboard.
- Click **Connect Integration** button
- Search for **Google Calendar** and click the box
- Provide the following details:
  - **Connect Name**: Enter a meaningful name.
  - **Client ID**: Paste the Client ID from Google Cloud.
  - **Client Secret**: Paste the Client Secret from Google Cloud.
- Click **Save Connect & Authenticate** 

#### 8. Authenticate and Generate Tokens
- After saving the connection, you will be redirected to Google’s login page.
- Log in using one of the test user accounts.
- Grant permissions for the specified scopes.
- Upon successful authentication, the application will store the **Access Token** and **Refresh Token** for future API requests.

### Tips
- Ensure that you have enabled the API for **Google Calendar** 
- FlowMattic needs your site's cron jobs to be functional in order to renew the Access Token. Make sure the cron jobs are working fine and you have set up the server side crons.
-  Read more about cron jobs here - 
 [Authentication keeps expiring or Delay not working](https://support.flowmattic.com/kb/article/46/authentication-keeps-expiring-or-delay-not-working)
- Regularly review and update test users as needed.

### Additional Resources
- [Google Cloud Console Documentation](https://cloud.google.com/docs/)
- [Google Calendar Documentation](https://developers.google.com/calendar/api)

---

# Comprehensive Guide to Setting Up Google Console Project for Contacts API Integration

Source: https://support.flowmattic.com/kb/article/96/comprehensive-guide-to-setting-up-google-console-project-for-contacts-api-integration

### Overview
This guide provides a step-by-step process for setting up a Google Cloud project and configuring it to integrate the Google Contacts API. It includes instructions for enabling the API, configuring OAuth credentials, and completing the authentication process.

### Steps to Set Up Google Console Project

#### 1. Create a Google Cloud Project
- Log in to the [Google Cloud Console](https://console.cloud.google.com/).
- Click on the Select a project dropdown at the top of the page, then click on New Project.
- Provide the following details:
-- **Project Name:** Enter a meaningful name (e.g., “Google Contacts API Integration”).
-- **Location:** Leave it as “No organization” if you do not have an organization.
- Click Create. Google will redirect you to the project dashboard

#### 2. Enable Google Contacts API
- Navigate to **[APIs & Services > Library](https://console.cloud.google.com/apis/library)**.
- In the API Library:
-- Search for **Google Contacts API**, click on it, and then click **Enable**.
-- Search for **Google People API**, click on it, and then click **Enable**.

#### 3. Configure the OAuth Consent Screen
- Go to **[APIs & Services > OAuth consent screen](https://console.cloud.google.com/apis/credentials/consent)**.
- Choose **External** as the user type and click Create.
- Fill out the following details:
-- **App Name:** Enter a meaningful name (e.g., “FlowMattic Google Integration”).
-- **User Support Email:** Enter your email address.
-- **App Logo:** Optional, but you can upload a logo if desired.
-- **Authorized Domains:** Add the following domain: flowmattic.com
-- **Developer Contact Information:** Enter your email address.
- Click Save and Continue.

#### 4. Add Scopes
- On the “[Scopes](https://console.cloud.google.com/auth/scopes)” screen:
- Click Add or Remove Scopes.
-- Select the following scopes from the list or manually add them:
  - `https://www.googleapis.com/auth/contacts`
  - `https://www.googleapis.com/auth/contacts.other.readonly`
- Click Update and then Save and Continue
![Image 2025-08-13 at 9.44.35 PM.jpeg](/storage/kb-images/daa4a1182f-inline.png)

#### 5. Add Test Users
- On the **[Audience](https://console.cloud.google.com/auth/audience)** tab, under  “**Test Users**” section:
-- Click **Add Users**.
-- Enter the email addresses of the Google accounts you will use to test the integration (e.g., your own or any users who will authenticate the connection).
-- You can add multiple email addresses, separated by commas or one per line.
- Click **Save and Continue**.

![Add Test Users.png](/storage/kb-images/eca60ff313-inline.png)

#### 6. Create OAuth 2.0 Credentials
- Go to **[APIs & Services > Credentials](https://console.cloud.google.com/apis/credentials)**.
- Click **+ Create Credentials** and select **OAuth Client ID**.
- On the **Create OAuth Client ID** screen:
  - Select **Web Application** as the application type.
  - Provide a name for the credential.
  - Add the callback URL to the **Authorized Redirect URIs** : 
  - `https://api.flowmattic.com/google/contacts`
- Save the credentials and securely store the **Client ID** and **Client Secret**.
![Image 2025-08-13 at 9.49.48 PM.jpeg](/storage/kb-images/f1f9919762-inline.png)

#### 7. Configure Connect in FlowMattic
- Navigate to the **FlowMattic -> Connects** settings in your WordPress dashboard.
- Click **Connect Integration** button
- Search for **Google Contacts** and click the box
- Provide the following details:
  - **Connect Name**: Enter a meaningful name.
  - **Client ID**: Paste the Client ID from Google Cloud.
  - **Client Secret**: Paste the Client Secret from Google Cloud.
- Click **Save Connect & Authenticate** 

#### 8. Authenticate and Generate Tokens
- After saving the connection, you will be redirected to Google’s login page.
- Log in using one of the test user accounts.
- Grant permissions for the specified scopes.
- Upon successful authentication, the application will store the **Access Token** and **Refresh Token** for future API requests.

### Tips
- Ensure that you have enabled the API for **Google Contacts** 
- FlowMattic needs your site's cron jobs to be functional in order to renew the Access Token. Make sure the cron jobs are working fine, and you have set up the server-side side crons.
-  Read more about cron jobs here - 
 [Authentication keeps expiring or Delay not working](https://support.flowmattic.com/kb/article/46/authentication-keeps-expiring-or-delay-not-working)
- Regularly review and update test users as needed.

### Additional Resources
- [Google Cloud Console Documentation](https://cloud.google.com/docs/)
- [Google Contacts Documentation](https://developers.google.com/contacts/api)

---

# Comprehensive Guide to Setting Up Google Console Project for Gmail Integration

Source: https://support.flowmattic.com/kb/article/151/comprehensive-guide-to-setting-up-google-console-project-for-gmail-integration

Connect your Gmail account to FlowMattic to send emails, manage drafts, organize labels, and search your inbox — all from within your automated workflows.

---

## Prerequisites

Before connecting Gmail to FlowMattic, you need to create a Google Cloud project with OAuth credentials. Follow the steps below to set up your Google Cloud Console project.

---

## Step 1: Create a Google Cloud Project

1. Go to [Google Cloud Console](https://console.cloud.google.com/).
2. Click the project dropdown at the top of the page and select **New Project**.
3. Enter a project name (e.g., "FlowMattic Gmail Integration").
4. Click **Create**.

![Create Google Cloud Project](https://assets.infidesk.support/kb/inline/2026/07/jgYFhQC0f1a7z7zJXkMWSY3lDc7LGIMuJtUZzpDZ.png)

---

## Step 2: Enable the Gmail API

1. In the Google Cloud Console, navigate to **APIs & Services > Library**.
2. Search for **Gmail API**.
3. Click on **Gmail API** and then click **Enable**.

![Enable Gmail API](https://assets.infidesk.support/kb/inline/2026/07/Jxo4YOBFx6wRoWIz7jeFNHi2qr2Jw2lBPRzhxRjP.png)

---

## Step 3: Configure the OAuth Consent Screen

1. Navigate to **APIs & Services > OAuth consent screen**.
2. Select **External** as the user type and click **Create**.
3. Fill in the required fields:
   - **App name**: Enter your app name (e.g., "FlowMattic").
   - **User support email**: Select your email address.
   - **App logo**: Optional — upload a logo if desired.
   - **Authorized domains**: Add `flowmattic.com`.
   - **Developer contact email**: Enter your email address.
4. Click **Save and Continue**.

![OAuth Consent Screen](https://assets.infidesk.support/kb/inline/2026/07/AasbdPSuTdf0ic4xya7xHKYqDvdOmrTAWqgtFMAG.png)

---

## Step 4: Add Scopes

1. On the **Scopes** step, click **Add or Remove Scopes**.
2. Search for and add the following Gmail API scopes:
   - `https://mail.google.com/` — Full access to Gmail (read, send, delete, manage).
   - `https://www.googleapis.com/auth/gmail.send` — Send email only.
   - `https://www.googleapis.com/auth/gmail.modify` — Read, send, delete, and manage labels.
   - `https://www.googleapis.com/auth/gmail.readonly` — Read-only access.
3. Select the scopes appropriate for your use case. For full functionality, select `https://mail.google.com/`.
4. Click **Update** and then **Save and Continue**.

![Add Scopes](https://assets.infidesk.support/kb/inline/2026/07/hIIrwNk69tWhgWzwkIKpZO51MkhGZ6melty7LwPH.png)

> **Tip:** If you only need to send emails, the `gmail.send` scope is sufficient. For full workflow automation (search, labels, drafts), use the full `mail.google.com` scope.

---

## Step 5: Add Test Users

1. On the **Test users** step, click **Add Users**.
2. Enter the Gmail email address(es) you want to use for testing.
3. Click **Add** and then **Save and Continue**.

![Add Test Users](https://assets.infidesk.support/kb/inline/2026/07/WsrpQfVfd3xl71JQzRRllDobwGip8CV4YgwOgYJA.png)

> **Note:** While your app is in "Testing" mode, only test users listed here can authorize the connection. Once you publish the app, any Google account can connect.

---

## Step 6: Create OAuth Credentials

1. Navigate to **APIs & Services > Credentials**.
2. Click **Create Credentials** and select **OAuth client ID**.
3. Set the **Application type** to **Web application**.
4. Enter a name (e.g., "FlowMattic Gmail").
5. Under **Authorized redirect URIs**, add the following callback URL:
   ```
   https://api.flowmattic.com/google/gmail
   ```
6. Click **Create**.
7. Copy the **Client ID** and **Client Secret** — you will need these in the next step.

![Create OAuth Credentials](https://assets.infidesk.support/kb/inline/2026/07/Swm8WgeUmjYUF69pdIbVQYcmL7TNfTLTH8LNHhh0.png)

> **Important:** Make sure you copy the Client ID and Client Secret immediately. You can always access them later from the Credentials page, but it's easiest to copy them now.

---

## Step 7: Connect Gmail in FlowMattic

1. In your WordPress dashboard, go to **FlowMattic > Connects**.
2. Click **Add New Connection**.
3. Search for **Gmail** and select **Gmail (Custom)**.
4. Enter the **Client ID** and **Client Secret** from Step 6.
5. Click **Connect**.
6. You will be redirected to Google's authorization page. Sign in with a Google account that is listed as a test user (from Step 5).
7. Review the permissions and click **Allow**.
8. You will be redirected back to FlowMattic with a successful connection.

![Connect Gmail in FlowMattic](https://assets.infidesk.support/kb/inline/2026/07/JXUnzfISFfTsevQpFyQDqDas7KhgpwXSh3iBXV3L.png)

---

## Step 8: Verify the Connection

Once connected, FlowMattic will automatically:
- Retrieve your Gmail profile information.
- Store the access and refresh tokens securely.
- Schedule automatic token renewal via WordPress cron.

You can verify the connection is active by checking the **Connects** page — your Gmail connection should show a green status indicator.

![Verify Connection](https://assets.infidesk.support/kb/inline/2026/07/prbfPgYXLnMNZd4TYeFEl5m0nkGlpB41rDeuzNBN.png)

> **Important:** FlowMattic requires your site's cron jobs to be functional in order to auto-renew the Access Token. If your cron jobs are not running, the connection will expire and need to be re-authorized.

---

## Available Gmail Actions

> **Note:** Gmail provides workflow **actions** only — there is no Gmail trigger. To start a workflow when an email arrives, use the [IMAP Email Parser](/kb/article/117/imap-email-parser), which can monitor a Gmail inbox over IMAP.

Once connected, you can use the following actions in your FlowMattic workflows:

### Email Management

| Action | Description |
|--------|-------------|
| **Send Email** | Send an email to one or more recipients with support for CC, BCC, reply-to, and HTML content. |
| **Send Template Email** | Send an email using a pre-built FlowMattic email template with dynamic variable injection. |
| **Find Email** | Search for a single email in Gmail using search queries. |
| **Find Multiple Emails** | Search for multiple emails with query filters and label filtering. |
| **Get Email Details** | Retrieve full email details and metadata by message ID. |
| **Mark Email as Read** | Mark a specific email as read by message ID. |
| **Reply to Email** | Reply to an existing email thread. |

### Draft Management

| Action | Description |
|--------|-------------|
| **Create Draft** | Create an email draft in Gmail. |
| **Send Draft** | Send a previously created draft. |
| **Delete Draft** | Delete an email draft. |
| **Create Draft Reply** | Create a draft reply to an existing email. |
| **Send Draft Reply** | Send a draft reply. |
| **Delete Draft Reply** | Delete a draft reply. |

### Label Management

| Action | Description |
|--------|-------------|
| **List All Labels** | Retrieve all Gmail labels in the account. |
| **Create Label** | Create a new Gmail label. |
| **Delete Label** | Delete an existing Gmail label. |
| **Add Label to Email** | Apply a label to a specific email. |
| **Remove Label from Email** | Remove a label from a specific email. |

---

## Using Gmail in a Workflow

### Example: Send an Email

1. Create a new workflow or open an existing one.
2. Add a new action step and select **Gmail** as the application.
3. Choose **Send Email** as the action.
4. Select your Gmail connection from the dropdown.
5. Configure the email fields:
   - **To**: Recipient email address (supports dynamic variables).
   - **Subject**: Email subject line.
   - **Message**: Email body (supports HTML formatting).
   - **CC / BCC**: Optional additional recipients.
   - **Reply-To**: Optional reply-to address.
   - **From Name**: Optional sender display name.
   - **Add Signature**: Toggle to include your Gmail signature.
6. Save and test the action.

![Send Email Action](https://assets.infidesk.support/kb/inline/2026/07/Rf2IzUTYUvlVlv40GJVUWPPCmjZV4TJWxDWNI9QQ.png)

### Example: Search and Process Emails

1. Add a **Find Multiple Emails** action to search Gmail.
2. Use Gmail search query syntax in the **Search Query** field:
   - `from:example@gmail.com` — Emails from a specific sender.
   - `subject:invoice` — Emails with "invoice" in the subject.
   - `is:unread` — Only unread emails.
   - `after:2024/01/01` — Emails after a specific date.
   - `has:attachment` — Emails with attachments.
3. Set the **Max Results** to limit the number of returned emails.
4. Optionally filter by **Label** to narrow results.
5. Use the returned message IDs with **Get Email Details** to retrieve full email content.

![Search Emails Action](https://assets.infidesk.support/kb/inline/2026/07/nJ5ziQ1g1R7djWb0BOKnkmrrZnBeshM5ijyV8ULy.png)

---

## Template Email Support

FlowMattic supports sending template-based emails through Gmail with the following features:

- **Dynamic Variables**: Use `{{variable_name}}` syntax to inject workflow data into email templates.
- **Pre-header Text**: Add email preview text that appears in the inbox before the email is opened.
- **Send Count Tracking**: Automatically tracks how many times a template has been sent.

---

## Troubleshooting

### Connection Expired
If your Gmail connection stops working, it may be due to expired tokens. Ensure your WordPress cron jobs are running properly. You can:
- Install a cron job monitoring plugin.
- Set up a real server-side cron job to trigger `wp-cron.php` regularly.
- Re-authorize the connection from the **Connects** page.

### Insufficient Permissions
If you receive permission errors when performing actions, verify that:
- The Gmail API is enabled in your Google Cloud project.
- The correct scopes were added during OAuth consent screen setup.
- The Google account used for authorization has access to the required Gmail features.

### App Not Verified Warning
When authorizing the connection, Google may show an "App not verified" warning. This is normal for custom OAuth apps. Click **Advanced** and then **Go to [App Name] (unsafe)** to proceed with the authorization.

---

## Summary

| Setting | Value |
|---------|-------|
| **OAuth Callback URL** | `https://api.flowmattic.com/google/gmail` |
| **API Base URL** | `https://gmail.googleapis.com/gmail/v1/users/me/` |
| **Authentication** | OAuth 2.0 with automatic token refresh |
| **Available Actions** | 18 (Email, Draft, and Label management) |
| **Template Support** | Yes (dynamic variables and pre-header text) |

---

# Comprehensive Guide to Setting Up Google Console Project for Google Meet API Integration

Source: https://support.flowmattic.com/kb/article/95/comprehensive-guide-to-setting-up-google-console-project-for-google-meet-api-integration

### Overview
This guide provides a step-by-step process to set up a Google Cloud project and configure it for integrating the Google Meet API. It includes instructions for enabling the API, configuring OAuth credentials, and completing the authentication process.

### Steps to Set Up Google Console Project

#### 1. Create a Google Cloud Project
- Log in to the [Google Cloud Console](https://console.cloud.google.com/).
- Click on the Select a project dropdown at the top of the page, then click on New Project.
- Provide the following details:
-- **Project Name:** Enter a meaningful name (e.g., “Google Meet API Integration”).
-- **Location:** Leave it as “No organization” if you do not have an organization.
- Click Create. Google will redirect you to the project dashboard

#### 2. Enable Google Meet API
- Navigate to **[APIs & Services > Library](https://console.cloud.google.com/apis/library)**.
- In the API Library:
-- Search for **Google Meet API**, click on it, and then click **Enable**.

#### 3. Configure the OAuth Consent Screen
- Go to **[APIs & Services > OAuth consent screen](https://console.cloud.google.com/apis/credentials/consent)**.
- Choose **External** as the user type and click Create.
- Fill out the following details:
-- **App Name:** Enter a meaningful name (e.g., “FlowMattic Google Integration”).
-- **User Support Email:** Enter your email address.
-- **App Logo:** Optional, but you can upload a logo if desired.
-- **Authorized Domains:** Add the following domain: flowmattic.com
-- **Developer Contact Information:** Enter your email address.
- Click Save and Continue.

#### 4. Add Scopes
- On the “[Scopes](https://console.cloud.google.com/auth/scopes)” screen:
- Click Add or Remove Scopes.
-- Select the following scopes from the list or manually add them:
  - `https://www.googleapis.com/auth/meetings.space.created`
- Click Update and then Save and Continue

![Image 2025-08-13 at 12.19.20 AM.jpeg](/storage/kb-images/53a501ce9a-inline.png)

#### 5. Add Test Users
- On the **[Audience](https://console.cloud.google.com/auth/audience)** tab, under  “**Test Users**” section:
-- Click **Add Users**.
-- Enter the email addresses of the Google accounts you will use to test the integration (e.g., your own or any users who will authenticate the connection).
-- You can add multiple email addresses, separated by commas or one per line.
- Click **Save and Continue**.

![Add Test Users.png](/storage/kb-images/eca60ff313-inline.png)

#### 6. Create OAuth 2.0 Credentials
- Go to **[APIs & Services > Credentials](https://console.cloud.google.com/apis/credentials)**.
- Click **+ Create Credentials** and select **OAuth Client ID**.
- On the **Create OAuth Client ID** screen:
  - Select **Web Application** as the application type.
  - Provide a name for the credential.
  - Add the callback URL to the **Authorized Redirect URIs** : 
  - `https://api.flowmattic.com/google/meet`
- Save the credentials and securely store the **Client ID** and **Client Secret**.

![Image 2025-08-13 at 12.40.38 AM.jpeg](/storage/kb-images/edaabebd43-inline.png)

#### 7. Configure Connect in FlowMattic
- Navigate to the **FlowMattic -> Connects** settings in your WordPress dashboard.
- Click **Connect Integration** button
- Search for **Google Meet** and click the box
- Provide the following details:
  - **Connect Name**: Enter a meaningful name.
  - **Client ID**: Paste the Client ID from Google Cloud.
  - **Client Secret**: Paste the Client Secret from Google Cloud.
- Click **Save Connect & Authenticate** 

#### 8. Authenticate and Generate Tokens
- After saving the connection, you will be redirected to Google’s login page.
- Log in using one of the test user accounts.
- Grant permissions for the specified scopes.
- Upon successful authentication, the application will store the **Access Token** and **Refresh Token** for future API requests.

### Filter Usage Guide
You can apply filters in Google Meet actions to narrow down the results based on specific criteria. The following filter fields are supported:

- **space.meeting_code** – Filter by the meeting code.
- **space.name** – Filter by the meeting space name.
- **start_time** – Filter by the meeting start time.
- **end_time** – Filter by the meeting end time.

#### Examples
- Filter by Meeting Space Name
``` space.name={google_meet3.name} ```

- Filter by Meeting Code
``` space.meeting_code={google_meet4.meetingCode} ```

- Filter by Date Range (Start Time)
``` start_time>="2025-08-01T00:00:00.000Z" AND start_time<="2025-08-10T00:00:00.000Z" ```

- Filter for Ongoing Meetings (No End Time)
``` end_time IS NULL ```

**Tip**: Always use ISO 8601 date format (YYYY-MM-DDTHH:mm:ss.sssZ) for start_time and end_time filters.

### Tips
- Ensure that you have enabled the API for **Google Meet** 
- FlowMattic needs your site's cron jobs to be functional in order ro auto renew the Access Token. Make sure the cron jobs are working fine and you have set up the server side crons.
-  Read more about cron jobs here - 
 [Authentication keeps expiring or Delay not working](https://support.flowmattic.com/kb/article/46/authentication-keeps-expiring-or-delay-not-working)
- Regularly review and update test users as needed. 

### Additional Resources
- [Google Cloud Console Documentation](https://cloud.google.com/docs/)
- [Google Meet Documentation](https://developers.google.com/workspace/meet/api/guides/overview)

---

# Comprehensive Guide to Setting Up Google Console Project for Sheets and Drive API Integration

Source: https://support.flowmattic.com/kb/article/59/comprehensive-guide-to-setting-up-google-console-project-for-sheets-and-drive-api-integration

### Overview
This guide provides a step-by-step process to set up a Google Cloud project and configure it for integrating Google Sheets and Drive APIs. It includes instructions for enabling APIs, configuring OAuth credentials, and completing the authentication process.

### Steps to Set Up Google Console Project

#### 1. Create a Google Cloud Project
- Log in to the [Google Cloud Console](https://console.cloud.google.com/).
- Click on the Select a project dropdown at the top of the page, then click on New Project.
- Provide the following details:
-- **Project Name:** Enter a meaningful name (e.g., “Google Sheets API Integration”).
-- **Location:** Leave it as “No organization” if you do not have an organization.
- Click Create. Google will redirect you to the project dashboard

#### 2. Enable Google Sheets and Drive APIs
- Navigate to **[APIs & Services > Library](https://console.cloud.google.com/apis/library)**.
- In the API Library:
-- Search for **Google Sheets API**, click on it, and then click **Enable**.
-- Search for **Google Drive API**, click on it, and then click **Enable**.

#### 3. Configure the OAuth Consent Screen
- Go to **[APIs & Services > OAuth consent screen](https://console.cloud.google.com/apis/credentials/consent)**.
- Choose **External** as the user type and click Create.
- Fill out the following details:
-- **App Name:** Enter a meaningful name (e.g., “FlowMattic Google Integration”).
-- **User Support Email:** Enter your email address.
-- **App Logo:** Optional, but you can upload a logo if desired.
-- **Authorized Domains:** Add the following domain: flowmattic.com
-- **Developer Contact Information:** Enter your email address.
- Click Save and Continue.

#### 4. Add Scopes
- On the “[Scopes](https://console.cloud.google.com/auth/scopes)” screen:
- Click Add or Remove Scopes.
-- Select the following scopes from the list or manually add them:
  - `https://www.googleapis.com/auth/spreadsheets`
  - `https://www.googleapis.com/auth/drive`
- Click Update and then Save and Continue

![Add Scopes](/storage/kb-images/6c4f225454-inline.png)


#### 5. Add Test Users
- On the "[Audience](https://console.cloud.google.com/auth/audience)" tab, under  “**Test Users**” ssection:
-- Click **Add Users**.
-- Enter the email addresses of the Google accounts you will use to test the integration (e.g., your own or any users who will authenticate the connection).
-- You can add multiple email addresses, separated by commas or one per line.
- Click **Save and Continue**.

![Add Test Users.png](/storage/kb-images/eca60ff313-inline.png)

#### 6.Create a Google Drive Connect to get the endpoint URL
- Go to your site -> FlowMattic -> **Connects**
- Click the **Connect Integration** button in header and choose Google Drive
- You will a modal similar to the following, copy the **Redirect URL**, we need it for the next step
- Once you get the Client ID and Client Secret after next step, you need to add them here and click **Authenticate and Save Connect**, and process your authentication
- After successful authentication, you can use this Google Drive connect in any of your workflows.

![Google drive connect](https://assets.infidesk.support/kb/inline/2026/07/IsLSh0yTgUDPYz8YwTIn9G2961nQaxWnkCe0We8c.jpg)

#### 7. Create OAuth 2.0 Credentials
- Go to **[APIs & Services > Credentials](https://console.cloud.google.com/apis/credentials)**.
- Click **+ Create Credentials** and select **OAuth Client ID**.
- On the **Create OAuth Client ID** screen:
  - Select **Web Application** as the application type.
  - Provide a name for the credential.
  - Add the callback URL to the **Authorized Redirect URIs** : 
  - `https://yoursite.com/wp-json/flowmattic/v1/auth/google-drive`
- Save the credentials and securely store the **Client ID** and **Client Secret**.

![Copy the Client ID and Client Secret](/storage/kb-images/974f4f819d-inline.png)

#### 8. Configure Connect in FlowMattic
- Navigate to the **FlowMattic -> Connects** settings in your WordPress dashboard.
- Click **Connect Integration** button
- Search for **Google Sheets** and click the box
- Provide the following details:
  - **Connect Name**: Enter a meaningful name.
  - **Client ID**: Paste the Client ID from Google Cloud.
  - **Client Secret**: Paste the Client Secret from Google Cloud.
- Click **Save Connect & Authenticate** 

#### 9. Authenticate and Generate Tokens
- After saving the connection, you will be redirected to Google’s login page.
- Log in using one of the test user accounts.
- Grant permissions for the specified scopes.
- Upon successful authentication, the application will store the **Access Token** and **Refresh Token** for future API requests.

### Tips
- Ensure that you have enabled both the APIs for **Google Spreadsheets** and **Google Drive API**
- FlowMattic needs your site's cron jobs to be functional in order ro auto renew the Access Token. Make sure the cron jobs are working fine and you have set up the server side crons.
-  Read more about cron jobs here - 
 [Authentication keeps expiring or Delay not working](https://support.flowmattic.com/kb/article/46/authentication-keeps-expiring-or-delay-not-working)
- Regularly review and update test users as needed.

### Additional Resources
- [Google Cloud Console Documentation](https://cloud.google.com/docs/)
- [Google Sheets API Documentation](https://developers.google.com/sheets/api/)
- [Google Drive API Documentation](https://developers.google.com/drive/api/)

---

# Comprehensive Guide to Setting Up Google Console Project for Slides API Integration

Source: https://support.flowmattic.com/kb/article/98/comprehensive-guide-to-setting-up-google-console-project-for-slides-api-integration

### Overview
This guide provides a step-by-step process for setting up a Google Cloud project and configuring it to integrate the Google Slides  API. It includes instructions for enabling the API, configuring OAuth credentials, and completing the authentication process.

### Steps to Set Up Google Console Project

#### 1. Create a Google Cloud Project
- Log in to the [Google Cloud Console](https://console.cloud.google.com/).
- Click on the Select a project dropdown at the top of the page, then click on New Project.
- Provide the following details:
-- **Project Name:** Enter a meaningful name (e.g., “Google Slides API Integration”).
-- **Location:** Leave it as “No organization” if you do not have an organization.
- Click Create. Google will redirect you to the project dashboard

#### 2. Enable Google Slides API
- Navigate to **[APIs & Services > Library](https://console.cloud.google.com/apis/library)**.
- In the API Library:
-- Search for **Google Slides API**, click on it, and then click **Enable**.

#### 3. Configure the OAuth Consent Screen
- Go to **[APIs & Services > OAuth consent screen](https://console.cloud.google.com/apis/credentials/consent)**.
- Choose **External** as the user type and click Create.
- Fill out the following details:
-- **App Name:** Enter a meaningful name (e.g., “FlowMattic Google Integration”).
-- **User Support Email:** Enter your email address.
-- **App Logo:** Optional, but you can upload a logo if desired.
-- **Authorized Domains:** Add the following domain: flowmattic.com
-- **Developer Contact Information:** Enter your email address.
- Click Save and Continue.

#### 4. Add Scopes
- On the “[Scopes](https://console.cloud.google.com/auth/scopes)” screen:
- Click Add or Remove Scopes.
-- Select the following scopes from the list or manually add them:
  - `https://www.googleapis.com/auth/presentations`
  - `https://www.googleapis.com/auth/drive`
- Click Update and then Save and Continue
![Image 2025-08-24 at 12.02.59 AM.jpeg](/storage/kb-images/b1cf416825-inline.png)

#### 5. Add Test Users
- On the **[Audience](https://console.cloud.google.com/auth/audience)** tab, under  “**Test Users**” section:
-- Click **Add Users**.
-- Enter the email addresses of the Google accounts you will use to test the integration (e.g., your own or any users who will authenticate the connection).
-- You can add multiple email addresses, separated by commas or one per line.
- Click **Save and Continue**.

![Add Test Users.png](/storage/kb-images/eca60ff313-inline.png)

#### 6. Create OAuth 2.0 Credentials
- Go to **[APIs & Services > Credentials](https://console.cloud.google.com/apis/credentials)**.
- Click **+ Create Credentials** and select **OAuth Client ID**.
- On the **Create OAuth Client ID** screen:
  - Select **Web Application** as the application type.
  - Provide a name for the credential.
  - Add the callback URL to the **Authorized Redirect URIs** : 
  - `https://api.flowmattic.com/google/slides`
- Save the credentials and securely store the **Client ID** and **Client Secret**.
![Image 2025-08-23 at 11.57.50 PM.jpeg](/storage/kb-images/2eccbccd8d-inline.png)

#### 7. Configure Connect in FlowMattic
- Navigate to the **FlowMattic -> Connects** settings in your WordPress dashboard.
- Click **Connect Integration** button
- Search for **Google Slides** and click the box
- Provide the following details:
  - **Connect Name**: Enter a meaningful name.
  - **Client ID**: Paste the Client ID from Google Cloud.
  - **Client Secret**: Paste the Client Secret from Google Cloud.
- Click **Save Connect & Authenticate** 

#### 8. Authenticate and Generate Tokens
- After saving the connection, you will be redirected to Google’s login page.
- Log in using one of the test user accounts.
- Grant permissions for the specified scopes.
- Upon successful authentication, the application will store the **Access Token** and **Refresh Token** for future API requests.

### Tips
- Ensure that you have enabled the API for **Google Slides** 
- FlowMattic needs your site's cron jobs to be functional in order to renew the Access Token. Make sure the cron jobs are working fine, and you have set up the server-side side crons.
-  Read more about cron jobs here - 
 [Authentication keeps expiring or Delay not working](https://support.flowmattic.com/kb/article/46/authentication-keeps-expiring-or-delay-not-working)
- Regularly review and update test users as needed.

### Additional Resources
- [Google Cloud Console Documentation](https://cloud.google.com/docs/)
- [Google Slides Documentation](https://developers.google.com/slides/api)

---

# Connect a form to a workflow

Source: https://support.flowmattic.com/kb/article/176/connect-a-form-to-a-workflow

Every FlowMattic form fires a **New Form Submission** trigger. This guide connects a form to a workflow so each submission runs an automation.

## Step 1 — Note your field keys

Open your form in **FlowMattic → Forms** and check each field's **Field key**. The key is what the workflow receives as `{{key}}` — for example a field keyed `email` becomes `{{email}}`. Set stable, meaningful keys before building the workflow, because renaming a key later breaks any mapping that used it.

![A form field selected in the editor showing its Field key property](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-form-builder-form-field-key.png)

## Step 2 — Create a workflow with the Form Builder trigger

1. Go to **FlowMattic → Workflows** and create a new workflow.
2. For the trigger app, choose **Form Builder**.
3. For the trigger event, choose **New Form Submission**.

![Workflow trigger set to Form Builder with New Form Submission](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-form-builder-wf-form-trigger.png)

## Step 3 — Scope the trigger to a form

Under **Choose Form**, select which form fires this workflow:

- Select a **specific form** for per-form logic — the most common choice.
- Select **Any Form** when one workflow should run for every form submission on the site, such as logging every submission to Slack or a Table.

## Step 4 — Capture a test submission

Submit a test entry on the form (from any page it is embedded on), then click **Capture Response** to pull that submission in. This gives the workflow real field data to map against in the next steps.

## Step 5 — Map the fields in your actions

Add your action steps and map the form fields using their `{{key}}` tokens. For example, a Google Sheets **Create Row** action maps `{{name}}`, `{{email}}`, and `{{message}}` to columns; an Email action maps them into the message body.

![An action step with the variable picker open, showing the captured form fields available as tokens](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-form-builder-wf-form-fields.png)

## Step 6 — Turn the workflow on

Save and enable the workflow. The next submission on the scoped form (or any form, if you chose Any Form) will run it.

---

# Connect Amazon Bedrock to FlowMattic

Source: https://support.flowmattic.com/kb/article/215/connect-amazon-bedrock-to-flowmattic

Amazon Bedrock gives you access to foundation models — Claude, Nova, Llama, Mistral and Cohere — hosted inside AWS. Connecting Bedrock to FlowMattic lets your AI Agent and other AI features use those models with your existing AWS account and billing.

## What this connect does — and does not — give you

**Bedrock is a credentials connect, not a set of workflow actions.** Once connected, Bedrock models become selectable in the AI Agent and FlowMattic's other AI surfaces.

**You will not find "AWS Bedrock" actions in the step picker, and that is correct.** If you are looking for a Bedrock step to drop into a workflow, what you actually want is the **AI Agent** action, with a Bedrock model chosen inside it.

## Setting it up

Go to **FlowMattic → Connects**, add a new connection and choose **AWS Bedrock**.

There are two ways to authenticate. **Use one or the other — not both.**

### Option 1: Bedrock API key (recommended)

In the AWS Console, open **Amazon Bedrock → API keys** and generate a long-lived key. It starts with `ABSK`. Paste it into the **Bedrock API Key** field and **leave the IAM fields blank**.

This is the simpler path and the one we recommend.

### Option 2: IAM credentials

If your organisation requires IAM, create an access key under **IAM → Users → Security credentials** and enter the **Access Key ID** and **Secret Access Key**. Leave the Bedrock API Key field blank.

Note that AWS shows the secret access key **only once**, when you create it. If you did not save it, you cannot retrieve it later — generate a new key pair.

### Region

Set the **region** to match where you have Bedrock access. This matters more than people expect — see below.

## The two things that go wrong

Almost every Bedrock connection problem is one of these two, and neither is a FlowMattic fault.

### 1. You have not requested access to the model

Bedrock does not give you every model by default. **Each foundation model requires you to explicitly request access in the AWS console**, per model. Until AWS approves it, calls to that model fail even though your credentials are perfectly valid.

In the AWS Console, go to **Amazon Bedrock → Model access** and check the status of the model you are trying to use. Request access if it is not already granted. Approval is usually quick, but it is a separate step from creating your key.

### 2. The model is not available in your region

**Bedrock model availability varies by region**, and model access is granted per region. A model you have access to in `us-east-1` is not automatically available in `eu-west-1`.

So if you see *"model not found"* or *"access denied"* on a connection you are sure is configured correctly, check that you requested access to that specific model **in the same region your connect is set to**. A region mismatch produces exactly this error.

## Quick checklist

Before contacting support about a Bedrock connection, confirm:

- You filled in **either** the `ABSK` API key **or** the IAM pair — not both.
- The region on the connect matches the region where you requested model access.
- The model you are trying to use shows as **access granted** in the AWS console, in that region.
- Your AWS account has Bedrock enabled and is in good standing.

If all four are true and it still fails, get in touch and include the exact error message and the region.

---

# Connect Supabase to FlowMattic

Source: https://support.flowmattic.com/kb/article/234/connect-supabase-to-flowmattic

The [Supabase integration](https://flowmattic.com/integration/supabase/) lets your workflows read and write Supabase tables, call Postgres functions, manage Storage files, and react to database changes — all from inside WordPress. Before you can use any of its actions or triggers, you need to create a **Connect**: a saved credential that every Supabase step in your workflows reuses.

This guide walks you through it end to end. You'll enter your credentials once — every action inherits them, so you never re-enter the key or URL on individual steps.

## Before you start

You'll need a Supabase account with a project created at [supabase.com](https://supabase.com). Both free and paid projects work.

## Step 1 — Get your Supabase API key

1. Open your project in the Supabase Dashboard.
2. Go to **Project Settings → API Keys**.
3. Copy a **secret key** (it starts with `sb_secret_…`). If your project still uses legacy JWT keys, the `service_role` key works too.

> **Important:** use a **secret** (`sb_secret_…`) or legacy `service_role` key — not a publishable/anon key. Publishable keys are subject to Row Level Security, so your workflow's inserts and updates would be blocked. The secret key stays on your server and is never exposed to visitors.

## Step 2 — Get your Project REST URL

1. Still in **Project Settings**, open **Data API**.
2. Copy your project's REST endpoint. It looks like:

```
https://your-project-ref.supabase.co/rest/v1
```

That's everything you need from Supabase.

## Step 3 — Create the Connect in FlowMattic

1. In your WordPress admin, go to **FlowMattic → Connects** and click **Connect Integration**.

![The Connects screen with the Connect Integration button](https://assets.infidesk.support/products/flowmattic/kb-images/supabase-connect/connects-page.png)

2. Search for **Supabase** and click the Supabase card.

![Searching for Supabase in the integration picker](https://assets.infidesk.support/products/flowmattic/kb-images/supabase-connect/pick-supabase.png)

3. Fill in the connect form:

   - **Connect Name** — anything that helps you recognize it later, e.g. *My Supabase Project*.
   - **Supabase API Key** — paste the secret key from Step 1.
   - **Project REST URL** — paste the REST endpoint from Step 2.

![The Supabase connect form with all three fields filled](https://assets.infidesk.support/products/flowmattic/kb-images/supabase-connect/connect-form.png)

4. Click **Save Connect**. Supabase now appears in your Connects list, ready to use in any workflow.

## What you can do once connected

Add a **Supabase** action step to any workflow and pick from:

- **Rows:** Insert Row, Bulk Insert Rows, Update Row, Upsert Row, Delete Row, Select Rows, Get Row by ID, Count Rows
- **Functions:** Call a Postgres Function (RPC)
- **Storage:** Upload File, List Files, Delete File, Get Public URL, Create Signed URL

The integration also ships **triggers** — *New Row Inserted*, *Row Updated*, and *Row Deleted*. These are delivered through **Supabase Database Webhooks**: when you add a Supabase trigger to a workflow, FlowMattic shows you a webhook URL, and the trigger step's instructions walk you through adding it under **Database → Webhooks** in your Supabase project.

## Troubleshooting

- **401 / permission denied on writes** — you connected with a publishable/anon key. Create the connect again with a secret (`sb_secret_…`) or `service_role` key.
- **404 or "relation does not exist"** — double-check the Project REST URL: it must be your own project reference and end with `/rest/v1` (no trailing slash).
- **Multiple projects?** Create one Connect per Supabase project and pick the right one on each workflow step.

---

# Connect Zoom or Google Meet for booking links

Source: https://support.flowmattic.com/kb/article/177/connect-zoom-or-google-meet-for-booking-links

When a booking calendar's location is Zoom or Google Meet, FlowMattic can generate a real join link for each booking from the host's connected account. This guide covers connecting the account and assigning it to a calendar.

## Step 1 — Connect the account under Connects

1. Go to **FlowMattic → Connects**.
2. Add the connection for the account that should host the meetings:
   - **Zoom** — the Zoom integration must be installed first (under **FlowMattic → Integrations**), then connect your Zoom account here.
   - **Google Meet** — connect a **Google Calendar** account. Meet links are created through a Google Calendar event, so Bookings uses your Google Calendar connection for Meet.

![The FlowMattic → Connects screen with a Google Calendar account connected](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-bookings-connects-google.png)

The account you connect is the one whose Zoom or Meet space each meeting is created in, so connect the host's account.

## Step 2 — Set the calendar's location and host account

1. Open your calendar under **FlowMattic → Bookings**.
2. In the **Location** section, set the location to **Zoom** or **Google Meet**.
3. In the account picker that appears — **Zoom account** for Zoom, or **Google account** for Google Meet — select the connected account that should host the meetings.
4. Save.

![The calendar editor's Location section set to Zoom, with the Zoom account picker](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-bookings-location-zoom.png)

## What happens on each booking

When an invitee books, FlowMattic creates the meeting in the host's connected account and adds the join link to the confirmation email and the calendar invite automatically.

## If no account is connected

If the location is Zoom or Meet but no account is picked, the booking still goes through — the invitee is booked — but no meeting link is added. As the editor notes, until you pick an account the confirmation email links to the booking page instead of a meeting link. Connect and select the account, and future bookings will include the link.

---

# Context or Action Menu in FlowMattic

Source: https://support.flowmattic.com/kb/article/34/context-or-action-menu-in-flowmattic

In FlowMattic, the **Context Menu** or **Action Menu** appears when you click the three-dot icon next to an action step or route in the workflow. This menu provides a set of relevant actions, such as renaming, duplicating, copying, pasting, or deleting action steps and routes, making it easier to manage and organize your workflow elements.

By offering these options directly within the workflow interface, the context menu streamlines the process of organizing and modifying actions steps and routes, saving time and reducing the need for navigation through other screens.

**Context Menu:** Click the three-dot icon next to an action step or route to access the context menu, which provides various options for managing your workflow, including:

![](/storage/kb-images/7cef2cfa8c-Screenshot-2024-12-08-144809.png)

### 1\. **Rename**

- The **“Rename”** option allows you to change the name of an element to make it more identifiable and organized, which is especially helpful in complex workflows. To rename, select this option, enter the new name, and save it. This ensures better organization and makes the workflow easier to navigate.

- For an action step, renaming allows you to clarify its function or purpose within the workflow, making it easier to track and manage. For a route in a router, renaming helps to distinguish between different routes, improving workflow organization and clarity when managing multiple routes within the same router step.

### 2\. **Duplicate**

- The **“Duplicate”** option allows you to create an exact copy of a selected action step or route, including all its conditions, actions, and configurations. This feature is ideal for reusing similar elements with slight modifications.

- When duplicating an action step, the new copy is inserted just below the current step in the workflow, preserving the workflow’s structure. For a route within a router, the duplicated route is added at the end of the current list of routes, maintaining the logical order of the workflow.

### 3\. **Copy**

- The **“Copy”** option allows you to copy the configuration of an action step or route without immediately placing it in the workflow. This gives you the flexibility to replicate a specific step or route and paste it elsewhere in the workflow when needed, enabling efficient adjustments and organization of your workflow without altering its current structure.

### 4\. **Paste Below**

- The **“Paste Below”** option allows you to insert a copied element beneath the selected one in your workflow, ensuring the correct sequence is maintained.

- When pasting a copied action step, it will be placed directly below the selected step, keeping the workflow’s order intact. For routes within a router, when you paste a copied route using “Paste Below,” it will be inserted next to the current route, ensuring it fits logically within the sequence and maintains the proper execution order.

### 5\.**Paste to Replace**

- The **“Paste to Replace”** option allows you to replace an existing element with a copied one, completely overwriting the original, including all actions and configurations. This ensures that the new element fully replaces the old one, preserving the integrity of the workflow's structure.

- For an action step, when you use "Paste to Replace," the original action step is replaced by the copied one, maintaining the workflow's logical flow. In the case of a route, when you paste a route using “Paste to Replace,” the original route is overwritten, including all the steps within that route, ensuring that the new route takes its place seamlessly in the workflow.

### 6\. Delete

- The **“Delete”** option allows you to permanently remove an action step from your workflow when it is no longer needed. Once deleted, the action step is completely removed, and it cannot be restored. Ensure the action step is no longer required before deleting it.

- For routes within a router, if a route is deleted, it is permanently removed from the workflow. If all routes are deleted, the entire Router step will also be deleted, effectively removing that entire segment from the workflow.

---

# Counter

Source: https://support.flowmattic.com/kb/article/39/counter

The **FlowMattic Counter** is a versatile feature designed to track and manage numerical values in workflows dynamically. Whether you need to generate sequential numbers, assign unique IDs, or keep a count of specific events, the Counter simplifies these tasks through automation. It is ideal for use cases like tracking orders, monitoring event participation, or managing ticket numbers.

This tool allows you to configure starting values, increment or decrement numbers automatically, and format the output with prefixes, suffixes, or padded digits. With its user-friendly interface, you can set up counters with ease while enjoying the flexibility to apply advanced customization for specific workflow requirements.

### Setting Up a Counter in FlowMattic

#### 1\. Create a New Workflow

Go to the FlowMattic Dashboard, where you can manage and create workflows. To start a new workflow, click the&nbsp;**“New Workflow”**&nbsp;button located in the top-right corner of the Dashboard. This will begin the process of creating your new workflow.

#### 2\. Add a Counter Action

- In the workflow editor, click the **+** icon to add a new step. From the list of available tools, select **Counter** under the FlowMattic built-in tools section. This tool is essential for automating the tracking of numbers, whether for incrementing or decrementing purposes.

- Once selected, choose an appropriate **Action Event** for the counter. Select **Incremental Counter** to increase the number or **Decremental Counter** to reduce it. This depends on whether you want to count up (e.g., for order numbers) or count down (e.g., for ticket availability).

![](/storage/kb-images/e03927c2bd-Screenshot-2024-12-11-170822.png)

#### 3\. Configuring the Counter Settings

- **Initial Value**: This is the starting point for your counter, where the counting will begin. You can set it to any integer depending on your needs (e.g., `0`, `1`, or `5`). This ensures the counter starts from a defined number before any counting takes place.

- **Increment/Decrement Value**: This defines the amount by which the counter should change after each execution. If you want the counter to increase, set a positive value (e.g., `1`). For decreasing, set a negative value (e.g., `-1`). This controls how quickly or slowly the counter progresses.

- **Reset on Execution**: Select "Yes" if you want the counter to reset to the initial value after each execution. This ensures the counter starts fresh each time the step is executed. If you select "No," the counter will continue from its current value, without resetting.

![](/storage/kb-images/a8650e8713-Screenshot-2024-12-11-170948.png)

#### 4\. Save and Test the Counter

- Once the configuration is complete, use the **Test Action** feature to verify the counter’s behavior. This allows you to check whether the counter increments or decrements as intended and ensures that the output formatting meets your expectations.

- After testing, click **Save & Close**. This will finalize the counter setup, making it ready for use in your workflow. You can now reference the counter’s output in subsequent actions or integrate it into other applications seamlessly.

---

# Create a booking from a workflow

Source: https://support.flowmattic.com/kb/article/178/create-a-booking-from-a-workflow

A workflow can create a booking on one of your calendars with the **Add Booking** action. This is useful when the booking should follow another event automatically — a successful checkout, a form submission, or a step in an AI agent's chain.

## Step 1 — Have a calendar ready

Create the target calendar under **FlowMattic → Bookings** first, with its availability set. The Add Booking action books a slot on an existing calendar; it does not create the calendar.

## Step 2 — Add the Add Booking action

1. Open your workflow and add an action step.
2. Search for **FlowMattic Bookings** and choose **Add Booking**.

![Adding the FlowMattic Bookings → Add Booking action to a workflow](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-bookings-wf-add-booking-action.png)

## Step 3 — Pick the calendar and fill the booking

1. Select the target **Calendar** from the picker.
2. Fill the required fields: **Date** (`YYYY-MM-DD`), **Time** (`HH:MM`, 24-hour), **Invitee Name**, and **Invitee Email**.
3. Optionally add **Phone**, **Company**, **Notes**, **Guest Emails**, **Time Zone**, and **Status** (Confirmed or Pending).

Map these fields from captured data in earlier steps — for example the customer details from an order trigger or a form submission.

![The Add Booking action fields — Calendar, Date, Time, and Invitee Name mapped from captured data](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-bookings-wf-add-booking-fields.png)

## Step 4 — Save and use the result

Save the step. When it runs, the action:

- Creates the booking on the calendar.
- Schedules that booking's reminder and follow-up emails.
- Fires the same **New Booking** event other bookings fire, so any workflow watching that calendar also runs.
- Returns the booking object, so later steps can use its details (such as the manage URL).

## Note

A booking created this way behaves exactly like one made on the public page — it appears in the calendar's Bookings view and follows the same lifecycle events.

---

# Create a PDF template with AI

Source: https://support.flowmattic.com/kb/article/179/create-a-pdf-template-with-ai

FlowMattic can draft a PDF template from a written description using a connected AI provider. Instead of laying the document out by hand, you describe what you need and the AI generates a starter template in your library, which you then refine in the PDF Template Builder.

## Before you start

AI generation uses a provider connected under **FlowMattic → Connects**, and requires the AI Agent integration to be enabled. Add a provider connection first if you have not already.

## Step 1 — Open the AI generator

1. Go to **FlowMattic → PDF Templates**.
2. Click **Generate with AI** at the top of the page. (You can also start from the **New PDF Template** dialog by choosing the **Generate with AI** tile and clicking **Start with AI**, or use the **Generate with AI** tile inside the builder.)

![The PDF Templates page with the Generate with AI button highlighted](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-pdf-template-builder-pdf-generate-with-ai.png)

## Step 2 — Describe the document

In the **Generate a PDF with AI** dialog:

1. Write your brief in **Describe your document** — the more specific, the better. For example: *"Quarterly SaaS invoice with a line-item table, tax breakdown, and payment terms."* Or click one of the **Or start from a template** chips: Invoice, Receipt, Quote, Report, or Contract.
2. Set the **Page size** and **Orientation**.
3. Optionally set a **Template name** — left blank, it is derived from your brief.
4. Choose the **AI provider** and its **Connect**, and optionally a **Model**.

![The Generate a PDF with AI dialog with a filled-in brief, page size, orientation, and provider selected](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-pdf-template-builder-pdf-ai-modal.png)

## Step 3 — Generate

Click **Generate template**. Generation is experimental and can take roughly 20–60 seconds. When it finishes, the new template opens in the PDF Template Builder.

## Step 4 — Review and refine

Always review the generated result before using it. Check the layout, correct any wording, and confirm the merge tags match the data your workflow will send — the AI marks the dynamic parts as `{{tokens}}`, and you can adjust them in the editor. See *Bind dynamic data in PDF templates with tokens and sample data*.

## Step 5 — Use it in a workflow

Once the template looks right, render it from any workflow with the **PDF Builder → Generate PDF from Template** action, selecting this template and mapping your data. See *Generate a PDF from a template in a workflow*.

---

# Create a single-use booking link

Source: https://support.flowmattic.com/kb/article/180/create-a-single-use-booking-link

A single-use booking link can be claimed once. As soon as someone books, it locks and stops accepting bookings. This is useful for a specific prospect, a paid session, or any slot you only want one person to take.

## Step 1 — Create a single-use calendar

1. Go to **FlowMattic → Bookings** and click **New Booking Calendar**.
2. In the **Event details** section, turn on **Single-use link**. It generates a one-time scheduling link with a random, unguessable URL; after one booking the link locks and shows a "no longer available" page.

A calendar's link type is fixed once the calendar is created — you cannot convert a regular calendar to single-use or back afterward. Decide before you save.

![The calendar editor's Event details with the Single-use link option enabled](https://assets.infidesk.support/kb/inline/2026/07/Mq2QP9PD2ffKZ1s7puzczyE4gWp7ijjJ0Tr6If4d.png)

## Step 2 — Set the slot details

Set the **Duration** and a tight **Date range** covering only the times you have free, so the recipient can only pick from those.

## Step 3 — Copy and send the one-time link

Save the calendar and copy its **Booking link** — a one-time URL ending in `/d/{token}/` with a random token. The share rail labels it **One-time link**. Send this link directly to the one person who should book.

![The calendar's Booking link — the one-time link with its random /d/{token}/ URL and a Regenerate control](https://assets.infidesk.support/kb/inline/2026/07/ppO37Pvn5IvsQw6uodq1ZvZNpmM0KZTpbta5lVfA.png)

## What happens after they book

As soon as the prospect books, the link locks and shows a "no longer available" page, and stops accepting further bookings. If you need to offer that same calendar again, click **Regenerate** on the calendar's **Booking link** to swap in a fresh token (this replaces the calendar's own link). To hand out a new link per customer automatically instead, use the workflow action below.

## Automate it — issue a fresh link on every payment

You don't have to regenerate links by hand. Add a **FlowMattic Bookings → Regenerate Single-Use Link** action to any workflow, and it issues a brand-new single-use link for the calendar each time it runs. A common setup: a payment gateway — Stripe, PayPal, WooCommerce, Paddle, or anything that can send a webhook — confirms a payment, and the workflow emails the buyer their own private booking link.

- Point the action at your single-use calendar, or leave it empty to use the calendar from the trigger.
- Each run returns the new link as the `{{booking_link}}` merge tag — map that into an **Email** step. (The calendar's own link stays in `{{calendar_url}}`.)
- **Issued links are additive.** Sending a new link never voids the ones you've already sent: every issued link books exactly once and locks only itself, and your calendar's own link keeps working too. So you can hand a fresh link to every paying customer without any of them voiding another.

![The workflow builder — a Webhooks trigger, then FlowMattic Bookings → Regenerate Single-Use Link with the Calendar field set, then a Send Email step with the {{booking_link}} tag in the message body](https://assets.infidesk.support/kb/inline/2026/07/RtoSanWFR9Jr3BjwKdrgI1ZozvWCa9RR0s0JaREK.png).

## Note

Single-use bookings fire the same lifecycle events as any other booking, so you can still automate the follow-up with a workflow. See *Trigger a workflow on bookings*.

---

# Create a WP Table from a CSV File

Source: https://support.flowmattic.com/kb/article/243/create-wp-table-from-csv

Have your data in a spreadsheet already? Export it as a CSV and FlowMattic builds the WP Table for you — columns, types and all — ready to use in your workflows in under a minute.

## Step 1 — Open WP Tables and click Import CSV

Go to **FlowMattic → WP Tables**. Next to Create New Table you'll find **Import CSV**.

![The Import CSV button on the WP Tables screen](https://assets.infidesk.support/products/flowmattic/kb-images/wp-table-csv/wpc-01-import-button.png)

## Step 2 — Upload your CSV file

Drag your file onto the upload area, or click to browse. Files up to 20 MB are accepted, and the first row of the CSV is read as the column headers.

![The CSV upload step](https://assets.infidesk.support/products/flowmattic/kb-images/wp-table-csv/wpc-02-upload.png)

## Step 3 — Review the table and its columns

FlowMattic reads the file in your browser and prepares everything for review:

- **Table name** — prefilled from the file name. Letters, numbers and underscores, up to 64 characters.
- **Database** — Local is your WordPress database; any database you've connected is listed too.
- **Fields** — one row per CSV column with its name, a sample value, and the detected type. Numbers, emails, dates, date-times, checkboxes, links and long text are recognized automatically from the data — adjust any name or type, and mark a field Required if every row must include it.

![Reviewing the table name, database and detected columns](https://assets.infidesk.support/products/flowmattic/kb-images/wp-table-csv/wpc-03-mapping.png)

Every table automatically gets an `id` primary key, and field names are lowercased with spaces turned into underscores — `First Name` becomes the `first_name` column.

## Step 4 — Import

Click **Import**. FlowMattic creates the table, then inserts your rows in batches of 50 so large files import reliably. If a batch fails mid-way — a dropped connection, for example — you can resume right where it stopped.

![The finished import](https://assets.infidesk.support/products/flowmattic/kb-images/wp-table-csv/wpc-04-success.png)

## Step 5 — Open your table

Click **Open table** and your data is there — typed columns, inline editing, search, filters and CSV export, like any other WP Table. Workflows can read and write it right away.

![The imported data in the table grid](https://assets.infidesk.support/products/flowmattic/kb-images/wp-table-csv/wpc-05-grid.png)

## Good to know

- **Checkbox values just work.** `yes`/`no`, `true`/`false`, `on`/`off` and similar values become properly checked or unchecked boxes.
- **A column named `id` is renamed `csv_id`** — the automatic primary key owns that name.
- **Table names must be unused.** If a table with the same name already exists in the chosen database (in any letter case), the import tells you so — pick another name.
- **Rows that don't fit are skipped, not mangled.** A value that can't pass its column's type check (text in a number column, say) skips that row and the summary tells you how many were skipped and why.
- **Adding more data later?** Open the table and use its own **Import CSV** button — that one appends rows to the existing table with the same mapping wizard.

---

# Create Custom Variables

Source: https://support.flowmattic.com/kb/article/6/create-custom-variables

Here's a **step-by-step tutorial** based on how to create and use variables in FlowMattic.

### Step-by-Step Guide: Creating a Custom Variable in FlowMattic

#### Step 1: Navigating to the Variables Section

1. **Login to FlowMattic** and access your dashboard.

3. In the left-hand menu, click on **"Variables"**.

- This will take you to the **Variables Management** screen where you can see a list of previously created variables or create new ones.

#### Step 2: Creating a New Variable

1. On the Variables screen, click on the **"Add New Variable"** button (usually located at the top of the page).

3. A form will appear, prompting you to fill in the details for the new variable.

- **Variable Name**:
    - Enter a unique and meaningful name for your variable (e.g., `current_time` or `user_id`).

- **Variable Value**:
    - This field accepts a plain text value, dynamic placeholders, or even a PHP function. For example:
    
    - Entering `PHP:time()` as the value will dynamically call the `time()` function whenever this variable is accessed in your workflow, returning the current Unix timestamp.
    
    - Similarly, you can use other PHP functions like `PHP:date("Y-m-d")` to return a formatted date.

#### Step 3: Using PHP in Variables

- FlowMattic supports PHP functions directly in the **Variable Value** field, which is extremely useful for dynamically generating data.

- **Example:**

- If you input `PHP:time()` as the variable value, FlowMattic will evaluate the PHP code when the variable is accessed in the workflow.

- This ensures that the value is always current and generated at runtime.

#### Step 4: Saving the Variable

1. After entering the **Variable Name** and **Variable Value**, click on **"Save"** or **"Create"**.

- Your variable will now appear in the list of available variables, and its value will be updated each time it is accessed in workflows.

#### Step 5: Using the Variable in a Workflow

1. Navigate to the **Workflows** section of FlowMattic.

3. When creating or editing a workflow, locate the step where you wish to use the variable.

- Most fields that accept dynamic data (such as messages, emails, or API requests) will allow you to insert variables.

1. Click the **"Database"** icon or in the input field to bring the dynamic data dropdown, then find the variable in the "Variables" toggle. OR type the variable name (e.g., `{{variable_name}}`) where you want to use the variable.

- If you created a variable with a PHP function (e.g., `PHP:time()`), this function will be called and evaluated dynamically when the workflow is triggered.

#### Step 6: Testing Your Variable

1. Run your workflow and check the output to ensure that the variable works as expected.

- For example, if you used the `PHP:time()` function, the workflow should output the current Unix timestamp wherever you used the variable.

### Example Use Case

- **Current Timestamp Variable**:

- If you create a variable `current_time` with the value `PHP:time()`, you can use this variable in an email, API request, or other workflow step to always have the exact timestamp when the workflow runs.

- **Formatted Date Variable**:

- If you want the current date in `YYYY-MM-DD` format, you can create a variable with the value `PHP:date("Y-m-d")`.

### Conclusion

By following these steps, you can effectively create and manage custom variables in FlowMattic, using PHP functions for dynamic and real-time data processing in your workflows. This is especially useful for automating tasks that rely on up-to-date information like timestamps, dates, or other PHP-based calculations.

---

# Create QR-coded images

Source: https://support.flowmattic.com/kb/article/181/create-qr-coded-images

An image template can include a QR code whose target is different on every render. This is how you produce unique event tickets, attendee badges, or check-in cards where each person gets their own scannable code.

## Step 1 — Add a QR element

1. Open your template in **FlowMattic → Image Templates**.
2. On the **Elements** tab, drag a **QR Code** element onto the canvas and position it where the code should appear.

![The image editor with a QR Code element placed on the canvas](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-image-template-img-qr-on-canvas.png)

## Step 2 — Bind the QR value to a token

1. Select the QR Code element.
2. On the **Element** tab, set its **URL / Value** field to a token such as `{{ticket_url}}`.

The URL / Value can be any text or URL. Using a token means the encoded value comes from your workflow at render time rather than being fixed. Set the code's on-canvas size with its **W** and **H** under **Position & size**.

![The QR Code element's Element tab with the URL / Value field set to {{ticket_url}}](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-image-template-img-qr-value-field.png)

## Step 3 — Add any supporting tokens

Add other tokens the design needs, such as a `{{attendee_name}}` heading, so each image is personalised alongside its unique code. See *Add tokens and sample data to an image template*.

## Step 4 — Map the token in your workflow

1. In your workflow, add the **Image Builder → Generate Image from Template** action and pick this template in the **Image Template** dropdown.
2. Map `ticket_url` to the unique URL for the current record — for example the manage/booking URL from a booking trigger, or a per-attendee link you generated earlier.
3. Map `attendee_name` to the person's name.

Each time the workflow runs, the QR element resolves its token to that run's value before the image is rendered, so every image encodes a distinct, scannable code.

## Generating many at once

To produce one QR image per person in a list, place the Generate Image action inside an **Iterator** step and map the tokens to the loop's current item. See *Bulk-generate images with the Iterator*.

---

# Create Reusable Workflow Steps with Sub-Workflows

Source: https://support.flowmattic.com/kb/article/110/create-reusable-workflow-steps-with-sub-workflows

Ready to supercharge your FlowMattic workflows? This guide walks you through creating and using Sub-Workflows step by step. By the end, you'll have built your first reusable workflow component.

## Before You Start

**What you'll learn:**
- How to build a Sub-Workflow from scratch
- How to pass data to Sub-Workflows
- How to return data from Sub-Workflows
- How to call Sub-Workflows from parent workflows
- Best practices and troubleshooting tips

**What you'll need:**
- WordPress site with FlowMattic plugin installed
- Access to FlowMattic dashboard in WordPress admin
- Basic familiarity with creating FlowMattic workflows
- 15 minutes to follow along

**Important Note:** FlowMattic is a WordPress plugin, so you'll be working within your WordPress admin dashboard throughout this tutorial.

## The FlowMattic Sub-Workflow Process

FlowMattic has a unique approach to creating Sub-Workflows. Here's the high-level process:

1. **Create parent workflow** → Add trigger and initial steps
2. **Add Call Sub-Workflow action** → Configure parameters to pass
3. **Create Sub-Workflow in new tab** → Set Sub-Workflow trigger
4. **Click "Capture Response"** → Sub-Workflow listens for data
5. **Test parent workflow action** → Sends test data to Sub-Workflow
6. **Sub-Workflow captures parameters** → Now has the data structure
7. **Build Sub-Workflow actions** → Process the captured data
8. **Add Return Response** → Send results back to parent
9. **Complete parent workflow** → Use returned data

**Why this order?** It makes parameter passing automatic and error-free. The Sub-Workflow captures exactly what the parent sends.

---

## Part 1: Create Your Parent Workflow First

Unlike some automation platforms, FlowMattic has a unique workflow for setting up Sub-Workflows. You'll start with the parent workflow, then create the Sub-Workflow. This approach makes parameter passing easier and more intuitive.

Let's create a practical example: a Sub-Workflow that formats customer contact information.

### Step 1: Create the Parent Workflow

1. In WordPress admin, navigate to **FlowMattic → Workflows**
2. Click **Create New Workflow**
3. Name it: "Gravity Forms to CRM" (this is our parent workflow)
4. Click **Save**

### Step 2: Add Your Trigger

For this example, let's use a Gravity Forms trigger:

1. Click **Choose Trigger App**
2. Select **Gravity Forms**
3. Choose **New Form Response** as the trigger event
4. Connect your Gravity account and select your form
5. Test the trigger to ensure data is coming through

### Step 3: Add the Call Sub-Workflow Action

Here's where it gets interesting. You'll add the Sub-Workflow call action BEFORE creating the actual Sub-Workflow:

1. Click **Add New Step**
2. Search for and select **Sub-Workflow**
3. Choose **Call Sub-Workflow** action
4. Click **Continue**

### Step 4: Configure Parameters to Pass

Now define what data you want to send to the Sub-Workflow:

1. Click **Add Parameter** in the Call Sub-Workflow action
2. Add your first parameter:
   - **Key:** `customer_email`
   - **Value:** Map to `{trigger.email_address}` from your form
3. Click **Add Parameter** again
4. Add second parameter:
   - **Key:** `customer_phone`
   - **Value:** Map to `{trigger.phone_number}` from your form
5. Add third parameter:
   - **Key:** `customer_name`
   - **Value:** Map to `{trigger.full_name}` from your form

![call-sub-workflow-action.png](/storage/kb-images/2a94d9ceae-inline.png)

**Parameter naming best practices:**
- Use lowercase with underscores (snake_case): `customer_email` not `CustomerEmail`
- Be descriptive: `order_total` not just `total`
- Group related parameters with prefixes: `customer_email`, `customer_name`, `customer_phone`

**Important:** Don't test this action yet. We need to create the Sub-Workflow first.

---

## Part 2: Create the Sub-Workflow

Now you'll create the actual Sub-Workflow that will process this data.

### Step 5: Open New Tab and Create Sub-Workflow

**Keep your parent workflow tab open!** You'll need to switch between tabs.

1. **Right-click** **FlowMattic → Workflows** and open in a new tab
2. In the new tab, click **Create New Workflow**
3. Name it descriptively: "Format Customer Contact Info"
   - Good names: "Format Customer Data", "Validate Email Address", "Calculate Shipping Cost"
   - Avoid: "Sub-Workflow 1", "Helper", "Utility"

**Why naming matters:** This name appears in dropdowns and helps you identify the workflow's purpose.

### Step 6: Set the Sub-Workflow Trigger

1. Click **Choose Trigger App**
2. Select **Sub-Workflow**
3. Choose **Start Sub-Workflow** as the trigger event
4. Click **Continue**

![sub-workflow - trigger step.png](/storage/kb-images/37cb5095c4-inline.png)

This tells FlowMattic this workflow will be called by other workflows.

### Step 7: Click "Capture Response"

**This is the crucial step that makes FlowMattic unique:**

1. In the Sub-Workflow trigger settings, click **Capture Response** button
2. This puts the Sub-Workflow in "listening mode"
3. You'll see a message: "Waiting to capture request from parent workflow..."
4. **Keep this tab open**

### Step 8: Go Back to Parent Workflow and Test

1. Switch back to your **parent workflow tab**
2. Scroll to the **Call Sub-Workflow** action
3. Click **Test Action**
4. The parent workflow will send the test data to your Sub-Workflow

### Step 9: Return to Sub-Workflow to See Captured Data

1. Switch back to your **Sub-Workflow tab**
2. You should see: "Request captured successfully!"
3. The Sub-Workflow now has the parameters captured:
   - `customer_email`
   - `customer_phone`
   - `customer_name`
4. Click **Save** to store the captured structure

**What just happened?** The parent workflow sent test data, and the Sub-Workflow captured the parameter structure. Now you can use these parameters in your Sub-Workflow actions.

### Step 10: Add Your Processing Actions

Now build the logic to process the captured data:

**Action 1: Clean Email Address**

1. Click **Add New Step**
2. Select **Text Formatter**
3. Choose **Lowercase** action
4. In the **Text** field, insert: `{customer_email}` (available from captured parameters)
5. Click **Save**

**Action 2: Remove Email Whitespace**

1. Add another step
2. Select **Text Formatter**
3. Choose **Trim Whitespace** action
4. In the **Text** field, insert the output from Action 1
5. Click **Save**

**Action 3: Format Phone Number**

1. Add another step
2. Select **Text Formatter**
3. Choose **Extract Numbers** action
4. In the **Text** field, insert: `{customer_phone}`
5. This removes all non-numeric characters: `(555) 123-4567` becomes `5551234567`

**Action 4: Proper Case Name**

1. Add another step
2. Select **Text Formatter**
3. Choose **Title Case** action
4. In the **Text** field, insert: `{customer_name}`
5. This converts `john doe` or `JOHN DOE` to `John Doe`

### Step 11: Add the Return Response Action

**CRITICAL:** Every Sub-Workflow must end with a Return Response action.

1. Click **Add New Step**
2. Select **Sub-Workflow**
3. Choose **Return Response** action
4. Click **Continue**

Now define what data to send back to the parent workflow:

1. Click **Add Response Parameter**
2. Add first response:
   - **Key:** `formatted_email`
   - **Value:** Insert the output from Action 2 (the trimmed, lowercase email)
3. Add second response:
   - **Key:** `formatted_phone`
   - **Value:** Insert the output from Action 3 (numbers only)
4. Add third response:
   - **Key:** `formatted_name`
   - **Value:** Insert the output from Action 4 (title case name)

![return-response.png](/storage/kb-images/fe2c47de42-inline.png)

### Step 12: Save and Enable the Sub-Workflow

1. Click **Save Workflow**
2. **Important:** Toggle the workflow status to **ON** (enabled)
3. The Sub-Workflow is now ready to be called

---

## Part 3: Complete the Parent Workflow

Now go back to your parent workflow and finish it.

### Step 13: Verify the Sub-Workflow Connection

1. Switch back to your **parent workflow tab**
2. In the **Call Sub-Workflow** action, click the **Sub-Workflow** dropdown
3. You should now see "Format Customer Contact Info" in the list
4. Select it
5. Verify your parameters are still mapped correctly

### Step 14: Use the Returned Data

The Sub-Workflow will now return formatted data. Let's use it to create a CRM contact:

1. Click **Add New Step** after the Call Sub-Workflow action
2. Select your **CRM app** (HubSpot, Salesforce, etc.)
3. Choose **Create Contact** action
4. Map the fields using the returned data:
   - **Email:** `{sub_workflow.formatted_email}`
   - **Phone:** `{sub_workflow.formatted_phone}`
   - **Name:** `{sub_workflow.formatted_name}`

**Notice the prefix:** All returned data from Sub-Workflows uses `{sub_workflow.your_key_name}`
> Note: The dynamic tags used  in this article are for representative purpose only. You should use the dynamic tag selection dropdown and choose the tag wisely.

### Step 15: Test the Complete Workflow

1. Click **Test Workflow** on the parent workflow
2. Submit a test form response
3. Watch the execution:
   - Parent workflow triggers
   - Calls Sub-Workflow with parameters
   - Sub-Workflow processes data
   - Returns formatted data
   - Parent workflow creates CRM contact
4. Check your CRM to verify the contact was created with formatted data

**Congratulations!** You've created your first working Sub-Workflow in FlowMattic.

---

## Part 4: Reuse Your Sub-Workflow in Other Workflows

The real power of Sub-Workflows comes from reusing them. Let's create another parent workflow that uses the same Sub-Workflow.

### Example: FluentCart Orders to CRM

Same Sub-Workflow, different data source. This shows the power of reusability.

### Step 1: Create New Parent Workflow

1. Navigate to **FlowMattic → Workflows**
2. Click **Create New Workflow**
3. Name it: "FluentCart Orders to CRM"
4. Set trigger to **FluentCart → New Order**
5. Configure and test the trigger

### Step 2: Add Call Sub-Workflow Action

1. Click **Add New Step**
2. Select **Sub-Workflow**
3. Choose **Call Sub-Workflow** action
4. In the dropdown, select **"Format Customer Contact Info"** (your existing Sub-Workflow)

### Step 3: Map Different Parameters

Now map the FluentCart data to the same Sub-Workflow parameters:

1. **customer_email:** Map to `{trigger.customer.email}`
2. **customer_phone:** Map to `{trigger.customer.phone}`
3. **customer_name:** Map to `{trigger.customer.first_name} {trigger.customer.last_name}`

**Notice:** Same parameter names, different data sources. The Sub-Workflow doesn't care where the data comes from.

### Step 4: Use the Returned Data

1. Add a new step
2. Select your **CRM app**
3. Choose **Update or Create Contact** action
4. Map fields:
   - **Email:** `{sub_workflow.formatted_email}`
   - **Phone:** `{sub_workflow.formatted_phone}`
   - **Name:** `{sub_workflow.formatted_name}`

### Step 5: Save and Test

1. Save the workflow
2. Enable it
3. Test with a real or test FluentCart order

**Result:** Same Sub-Workflow, different trigger, same reliable formatting logic. If you need to change how phone numbers are formatted, update the Sub-Workflow once and both parent workflows instantly use the new logic.

---

## Understanding the Workflow Flow

Here's what happens when a parent workflow runs:

```
1. Parent Workflow Trigger Fires
   (Gravity Form submitted, FluentCart order created, etc.)
   ↓
2. Parent Workflow Actions Execute
   (Any steps before the Sub-Workflow call)
   ↓
3. Call Sub-Workflow Action Sends Data
   Parameters: customer_email, customer_phone, customer_name
   ↓
4. Sub-Workflow Receives Parameters
   Trigger: Start Sub-Workflow captures the data
   ↓
5. Sub-Workflow Actions Execute
   Format email → Trim spaces → Format phone → Format name
   ↓
6. Sub-Workflow Returns Response
   Returns: formatted_email, formatted_phone, formatted_name, status
   ↓
7. Parent Workflow Receives Response
   Data available as {sub_workflow.key_name}
   ↓
8. Parent Workflow Continues
   Uses returned data in subsequent steps
   ↓
9. Parent Workflow Completes
```

---

### Using Dynamic Return Values

You don't have to return static keys. Build them dynamically:

**Example: Return processed item count**
- Action step: Count items in a list → Result: `5`
- Return Response: 
  - Key: `items_processed`
  - Value: `{count_step.result}`

### Nesting Sub-Workflows

Sub-Workflows can call other Sub-Workflows (but avoid circular references):

**✅ Allowed:**
- Sub-Workflow A calls Sub-Workflow B
- Sub-Workflow C calls Sub-Workflow B
- Sub-Workflow A calls Sub-Workflow C

**❌ Not Allowed:**
- Sub-Workflow A calls Sub-Workflow B
- Sub-Workflow B calls Sub-Workflow A
- (This creates an infinite loop)

---

## Best Practices

### Design for Reusability

**Do:**
- Keep Sub-Workflows focused on one task
- Use generic parameter names when possible
- Think about all potential use cases upfront
- Document what parameters expect

**Don't:**
- Hardcode specific values
- Make "mega Sub-Workflows" that do everything
- Use workflow-specific logic

### Naming Conventions

**Parameters and return keys:**
```
✅ Good: customer_email, order_total, is_valid
❌ Avoid: email, total, valid
```

**Why?** Descriptive names prevent confusion when you have multiple Sub-Workflows.

---

## Troubleshooting Common Issues

### Issue: "Capture Response" Not Working

**Possible causes:**
- Parent workflow not set up correctly
- Sub-Workflow not in listening mode

**Solutions:**
- ✅ Ensure you clicked "Capture Response" in the Sub-Workflow BEFORE testing parent workflow
- ✅ Keep the Sub-Workflow tab open and visible while testing parent
- ✅ Check that the Call Sub-Workflow action has parameters configured
- ✅ Try refreshing both browser tabs and start over

### Issue: Sub-Workflow Not Appearing in Dropdown

**Solutions:**
- ✅ Ensure the Sub-Workflow has "Start Sub-Workflow" trigger
- ✅ Verify the Sub-Workflow is saved and enabled (toggle is ON)
- ✅ Refresh the parent workflow page
- ✅ Clear WordPress cache if using a caching plugin

### Issue: Parameters Not Available in Sub-Workflow

**Check:**
- ✅ Did you complete the "Capture Response" step successfully?
- ✅ Did you test the Call Sub-Workflow action in parent workflow?
- ✅ Are you using the correct parameter names (case-sensitive)?
- ✅ Check the Sub-Workflow trigger settings to see captured parameters

### Issue: No Data Returned to Parent Workflow

**Check:**
- ✅ Return Response action is added to Sub-Workflow
- ✅ Return Response is the last step in Sub-Workflow
- ✅ Return Response parameters have valid values mapped
- ✅ Sub-Workflow is enabled and saved
- ✅ Sub-Workflow isn't failing before Return Response step

### Issue: "Sub-workflow is currently disabled" Error

**Solution:**
1. Go to **FlowMattic → Workflows**
2. Find the Sub-Workflow mentioned in the error
3. Click the toggle to turn it **ON**
4. Return to parent workflow and test again

### Issue: Parent Workflow Fails After Sub-Workflow Call

**Check:**
- ✅ Using correct return key names: `{sub_workflow.key_name}`
- ✅ Return keys match exactly what you defined (case-sensitive)
- ✅ Sub-Workflow completed successfully (check execution logs)
- ✅ Returned data type matches expected type in parent workflow

### Issue: "Circular dependency detected" Error

**Solution:**
Your Sub-Workflow structure creates an infinite loop:
- Sub-Workflow A calls Sub-Workflow B
- Sub-Workflow B calls Sub-Workflow A

Restructure your workflows to break the circular reference.

### Issue: Parameters Have Wrong Data

**Check:**
- ✅ Parameter mapping in parent workflow is correct
- ✅ Using the right trigger fields (check field names)
- ✅ Data exists in the trigger (test trigger first)
- ✅ No typos in parameter keys

---

**Need help?** Visit [FlowMattic Support](https://support.flowmattic.com) or contact our support team.

---

**Related Articles:**
- Understanding Sub-Workflows in FlowMattic
- FlowMattic Sub-Workflows and How to Use Them

---

# Creating Custom App for your application using APIs

Source: https://support.flowmattic.com/kb/article/58/creating-custom-app-for-your-application-using-apis

Creating a custom app within FlowMattic provides a powerful way to integrate external applications that are not already available in the FlowMattic integrations library. This guide outlines the steps required to create a custom application using APIs in FlowMattic, enabling you to extend its functionality and streamline your workflows.

### Steps to Create a Custom App

#### 1. Navigate to the Custom Apps Section
Begin by accessing the WordPress dashboard. From there, locate and open the `FlowMattic -> Custom Apps` section to manage or create new custom applications.

#### 2. Create a New Application
To initiate the creation of a custom application:
- Click on the `Create New App` button.
- In the `App Info` tab, provide the necessary details such as the name and description of the app.
- Once all required fields are completed, click on the `Save App Info` button to finalize the creation of your custom application.

#### 3. Add Actions to Your Custom Application
Actions are the tasks your custom app can perform. To define these actions:
- Navigate to the `Actions` tab within your custom app.
- Actions may include tasks like creating, updating, or managing specific data, depending on your requirements.

#### 4. Configure a New Action
To set up a new action for your custom app:
- Click on the `Create New Action` button. This will open a configuration popup.
- In the popup, you will find the following fields to configure:
  - **Action Name**: Provide a meaningful and descriptive name for the action (this is a mandatory field).
  - **Action Description**: Optionally, include a brief description of what the action does.
  - **Action Event API Configuration**: Specify the API endpoint, body, and header parameters. Alternatively, you can import a cURL request for faster setup.

#### 5. Configure Action Settings in Detail
Use the available configuration tabs to define the action’s settings:
- **Basic**:
  - Set the API Endpoint, HTTP Method (e.g., GET, POST, PUT, DELETE), and Request Content Type (e.g., JSON, XML, Form Data).
- **Headers**:
  - Enable and add any headers required by the API you are integrating with.
- **Body**:
  - Enable Request Body Parameters and input the necessary fields.
  - If the API requires custom JSON or XML, you can input it in the `Request Body (Raw JSON/XML)` section.
  - Use placeholders (e.g., `{{title}}`, `{{content}}`) to dynamically reference parameters within your workflow.

#### 6. Save the Configured Action
Once you have completed configuring the action, click the `Save Action` button to store the action within your custom app.

#### 7. Use the Custom Application in Workflows
After completing the setup, your custom app will be available for use in FlowMattic workflows. You can now integrate it seamlessly into your automation processes.

### Importing cURL Requests for Quick API Configuration
FlowMattic simplifies the process of configuring actions by allowing you to import cURL requests directly. Here’s how you can leverage this feature:

1. Open your custom app and navigate to the `Actions` tab.
2. Click on the `Create New Action` button to add a new action.
3. In the action configuration popup, select the `Import cURL Request` button.
4. Paste the cURL request into the provided text area and click the `Process Request` button.
5. FlowMattic will parse the cURL request and automatically set the API endpoint, body, and header parameters.
6. Review the parsed configuration and make any necessary adjustments.
7. After verifying the details, click the `Save Action` button to save the action.

It is recommended to test the action after saving to ensure that it functions as expected. Using the cURL request import feature can significantly reduce setup time, especially when integrating with APIs that provide example cURL requests in their documentation. Tools like Postman can also be used to test APIs and generate cURL requests for import into FlowMattic.

### Additional Tips for Success
- Always have the API documentation for the application you are integrating at hand. This will help you understand the required endpoints, parameters, and authentication methods.
- Thoroughly test API endpoints and parameters before finalizing your configuration to avoid errors during execution.
- Use clear and descriptive names for your actions. This will make it easier to manage and organize your workflows within FlowMattic.

By following these detailed steps, you can effectively extend the capabilities of FlowMattic to connect with virtually any application that supports APIs. This flexibility allows you to create robust and customized automation workflows tailored to your specific needs. If you encounter any issues or require assistance while creating your custom app or importing cURL requests, do not hesitate to reach out to FlowMattic support for guidance. We are always here to help!

---

# CSV Creator by FlowMattic

Source: https://support.flowmattic.com/kb/article/115/csv-creator-by-flowmattic

Export & Generate CSV Files Automatically. CSV Creator is a powerful FlowMattic integration that enables you to automatically generate and export CSV files from multiple data sources in WordPress. Create CSV files from FlowMattic Tables, JSON data, or arrays, with advanced filtering using custom WHERE queries and dynamic date range shortcuts. Perfect for automated data exports, reporting workflows, customer list management, and seamless integration with external systems. All generated CSV files are automatically saved to your WordPress media library with customizable delimiters, headers, and file naming options. Key Features: Database table exports, custom SQL queries, date range filtering (7_DAYS_AGO, 1_MONTH_AGO), JSON to CSV conversion, array data transformation, automatic WordPress media library integration, flexible record limiting and sorting, multiple delimiter support (comma, semicolon, tab, pipe, colon), and dynamic file naming. Use Cases: Automated customer data exports, scheduled sales reports, product catalog generation, email marketing list creation, backup automation, third-party system integration, inventory snapshots, and data pipeline workflows.

## Quick Start

The CSV Creator module provides three powerful actions to generate CSV files:

### 1. Create from FlowMattic Table

Export data from your FlowMattic tables with flexible filtering and sorting options.

**Key Features:**
- Select any database (local or external) and table
- Choose record selection mode:
  - **All Records** - Export everything
  - **First X Records** - Get the first N records
  - **Last X Records** - Get the most recent N records
  - **Custom Query** - Filter with WHERE conditions

**Custom Query Power:**
```
status = 'active'
country = 'USA'
created_at >= '2025-01-01'
price > 100 AND category = 'electronics'
```

**Date Range Shortcuts:**
```
created_at >= 7_DAYS_AGO        # Last 7 days
created_at <= 30_DAYS_AGO       # Older than 30 days
created_at >= 1_MONTH_AGO       # Last month
created_at >= 2_YEARS_AGO       # Last 2 years
```

**Sort & Limit:**
- Sort results by ID (Ascending/Descending)
- Limit number of records returned (optional)

### 2. Create from JSON

Convert JSON data into CSV format with automatic header detection.

**Example:**
```json
[
  {"name": "John", "email": "john@example.com", "status": "active"},
  {"name": "Jane", "email": "jane@example.com", "status": "pending"}
]
```

### 3. Create from Array

Use array data from previous workflow steps to create CSV files.

**Perfect for:**
- Processing data from API responses
- Converting filtered results from previous steps
- Dynamic data transformation workflows

## CSV Options

**Delimiters:**
- Comma (`,`) - Default
- Semicolon (`;`)
- Tab
- Pipe (`|`)
- Colon (`:`)

**Headers:**
- **Include Headers** - Column names as first row (recommended)
- **No Headers** - Data only

**File Naming:**
- Custom filename (optional) - e.g., `customer-export`
- Auto-generated - `FlowMattic-csv-YYYY-MM-DD-HH-MM-SS.csv`

## Response Data

Every CSV creation returns:

```json
{
  "status": "success",
  "file_url": "https://example.com/wp-content/uploads/2025/10/export.csv",
  "file_path": "/var/www/html/wp-content/uploads/2025/10/export.csv",
  "file_size": "15.2 KB",
  "file_size_bytes": 15625,
  "record_count": 250,
  "attachment_id": 1234,
  "message": "CSV file created successfully"
}
```

Use these values in subsequent workflow steps!

## Common Use Cases

**📊 Data Exports**
- Export customer lists for email marketing
- Generate product catalogs for external systems
- Create backup files of important data

**📈 Reporting**
- Daily sales reports
- Monthly active user lists
- Inventory snapshots

**🔄 Data Integration**
- Export data for import into other systems
- Generate feeds for third-party services
- Create data pipelines between applications

**🎯 Filtered Exports**
- Export only active customers: `status = 'active'`
- Get US customers from last 30 days: `country = 'USA' AND created_at >= 30_DAYS_AGO`
- High-value orders: `total > 1000 AND status = 'completed'`

## Tips & Tricks

**1. Combine with Schedulers**
Set up automatic daily/weekly exports using FlowMattic's Schedule trigger.

**2. Email CSV Files**
Chain with Email action to automatically send generated CSV files to recipients.

**3. Use Dynamic File Names**
Include dates or workflow data in filenames: `sales-report-{current_date}`

**4. Test Your Queries**
Start with a small limit (e.g., 10 records) to verify your WHERE conditions work correctly.

**5. Handle Nested Data**
JSON and Array sources automatically encode nested objects/arrays into CSV cells.

---
**Available Since:** FlowMattic 5.4.0

---

# CSV Parser

Source: https://support.flowmattic.com/kb/article/40/csv-parser

The **CSV Parser** by FlowMattic is a powerful tool designed to help users effortlessly parse CSV files into structured JSON data. This allows you to automate the process of reading and processing CSV files without the need for complex coding or manual intervention. It's especially useful for users working with large datasets that need to be transformed into formats compatible with other systems or applications. Whether you're dealing with customer data, sales records, or any other type of structured data, this tool helps you streamline your workflows, making data integration and automation seamless.

FlowMattic’s CSV Parser is ideal for a variety of use cases, such as populating CRMs, updating databases, or syncing information with third-party platforms like Google Sheets. By converting CSV data into JSON, it enables you to take full advantage of FlowMattic's broader automation capabilities, from triggering further actions to passing data between applications. With a few simple steps, you can set up and utilize the CSV Parser in your workflows to save time and increase efficiency in your daily operations.

#### Setting Up a CSV Parser by FlowMattic

Here’s a step-by-step guide to setting up the **CSV Parser** by FlowMattic within your workflow:

### Step 1: Create a New Workflow

Go to the FlowMattic Dashboard, where you can manage and create workflows. To start a new workflow, click the&nbsp;**“New Workflow”**&nbsp;button located in the top-right corner of the Dashboard. This will begin the process of creating your new workflow.

### Step 2: Add the CSV Parser and Select Action Event

- **Add the CSV Parser Tool**:  
    Click the **“+”** icon in your workflow and search for **“CSV Parser”**. Select it from the list to add it as an action step in your workflow. This will enable you to process CSV files automatically.

- **Choose the Action Event**:  
    Select the action event **“Parse CSV File”**, which converts the CSV file (or its URL) into JSON format. This prepares the data for use in the next steps of your workflow.

![](/storage/kb-images/128edf7610-Screenshot-2024-12-11-235231.png)

### Step 3: Configure the Settings

- **Enter CSV file URL**: You need to provide the direct URL where your CSV file is hosted. This could be a link to a file stored on any platform that supports publicly accessible URLs, like Google Drive or Dropbox. Make sure the URL is accessible so FlowMattic can fetch the file and read its contents.

- **Set Header Row**: If your CSV file has a header row (the first row with column names), select **"Yes"**. This will help FlowMattic recognize the column names and treat the data appropriately, so it can be used in future steps of your workflow. If there is no header row, select **"No"**, and FlowMattic will treat the first row as data, not headers.

![](/storage/kb-images/e574221b77-Screenshot-2024-12-11-235409.png)

### Step 4: Test and Save the Workflow

- Once the configuration is complete, use the **Test Action** feature to verify that the CSV file is parsed correctly. This allows you to check whether the data is properly converted into JSON and ensures that the output formatting meets your expectations.

- After testing, click **Save & Close**. This will finalize the CSV parsing setup, making it ready for use in your workflow. You can now reference the parsed data in subsequent actions or integrate it into other applications seamlessly.

---

# Customize booking emails

Source: https://support.flowmattic.com/kb/article/182/customize-booking-emails

Booking calendars send a set of transactional emails: a booking confirmation, a reminder, a reschedule notice, a cancellation notice, a follow-up, and an internal new-booking alert. You control which template each of these uses in two places — a global default for every calendar, and a per-calendar override — and you edit the templates themselves in the Email Templates library.

## Set the global defaults (all calendars)

1. Open **FlowMattic → Bookings**.
2. Click **Email notifications** in the top bar.
3. The **Email notifications** dialog lists each notification — Booking confirmation, Reminder, Reschedule notice, Cancellation notice, Follow-up, and the internal New booking alert.
4. For each one, choose the template it should use and toggle whether it is sent. Booking confirmation is always on; Follow-up is off by default.
5. Click **Save defaults**.

These are the defaults every calendar uses unless a calendar overrides them.

![The Email notifications dialog on the Bookings page — per-notification template selectors and the Save defaults button](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-bookings-email-notifications.png)

## Override the emails for one calendar

1. Open the calendar under **FlowMattic → Bookings**.
2. Scroll to the **Booking emails** section of the calendar editor.
3. Each notification is set to **Use account default**. To override just this calendar, pick a different template for any notification; a **Reset** control on the row returns it to the account default.
4. Save the calendar.

![The Booking emails section inside a calendar's editor, with the per-notification template dropdowns](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-bookings-booking-emails-section.png)

## Edit the template content

Both the global defaults and the per-calendar overrides choose from templates stored in the **Email Templates** library, under the **Booking emails** group. To change the wording, branding, or the dynamic fields a booking email shows (such as the invitee's name, the event name, the date and time, and the meeting link):

1. Open **FlowMattic → Email Templates** (or click **Open the email template builder** from the Email notifications dialog).
2. Open the booking template you want to change — for example **Booking confirmed** or **Reminder — 24 hours before**.
3. Edit and save.

![A booking confirmation template open in the Email Templates editor](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-bookings-email-booking-confirmation.png)

## Note on timing

The confirmation is sent immediately when a booking is made. The reminder and the follow-up are scheduled for a future time and dispatched by WordPress cron, so they depend on cron running on time — see *Booking reminders and follow-ups are not sending on time* if scheduled emails arrive late.

---

# Customize your chatbot's appearance

Source: https://support.flowmattic.com/kb/article/218/customize-your-chatbots-appearance

You can restyle your AI Assistant chatbot to match your site — colours, fonts, shape, avatar and position. Everything here lives on the **Theme** tab when you edit an assistant at **FlowMattic → AI Assistants**.

![The Theme tab of an AI Assistant, showing the fifteen theme presets, the Light/Dark mode switch and the Brand Color field](https://assets.infidesk.support/products/flowmattic/kb-images/v70/218-chatbot-theme.png)

## Start with a theme preset

The quickest route is **Theme Preset**, which applies a coordinated set of colours in one click. Fifteen are available: Default, Gray, Blue, Purple, Green, Red, Orange, Teal, Pink, Indigo, Sky, Amber, Rose, Dark, and Custom.

Pick the one closest to your brand, then adjust individual colours if you need to. Choosing **Custom** lets you set everything by hand.

Separately, **Mode** switches the chatbot between **Light** and **Dark**.

## Colours

**Brand Color** is the one that does the most work — it drives the chat header, the buttons and the accent colours together. If you only change one thing, change this. **Page Background** sets the colour behind the conversation.

For finer control, open the **Advanced Appearance** section, which is collapsed by default. There you will find:

- **Header Text Color**
- **Bot Message Text Color**
- **User Message Background**
- **User Message Text Color**
- **Chatbox Icon Background**

There is no separate control for the header background or the send button — both follow Brand Color.

## Fonts, size and shape

- **Font Family** — System Default, or Inter, Open Sans, Roboto, Lato, Poppins, Nunito, Georgia or Courier New.
- **Font Size** — Small, Medium or Large.
- **Border Radius** — None, Small, Medium, Large or Full Round.
- **Message Bubble Style** — Rounded, Sharp or Bubble.
- **Loading Animation** — Pulsing Dots, Spinner Icon or Wave Dots.
- **Show message timestamps** — on or off.

## Avatar, icon and launcher button

- **Chatbox Icon** — the icon on the floating chat button. A default chat icon is used if you upload nothing.
- **Bot Avatar** — shown next to bot messages and on the chat widget button.
- **Button Label** — optional text beside the chat icon, for example "Chat with us". Leave it empty for an icon-only button.

## Position on screen

**Widget Position** offers **Left** or **Right** — that is, bottom-left or bottom-right. There are no top positions and no margin or offset controls.

**This setting only affects the floating widget embed.** If you embed the chatbot with the shortcode or an iframe, it sits wherever you place it on the page and the position setting does nothing.

## Chat background image

Turn on **Enable chat background image** to put an image behind the conversation. You can upload your own or use the default, then tune it with:

- **Background Size** — Cover, Contain or Auto
- **Background Repeat** — Repeat, No Repeat, Repeat Horizontal or Repeat Vertical
- **Background Blend Mode** — Normal, Multiply, Screen, Overlay, Soft Light, Color Burn, Luminosity, Exclusion or Difference
- **Color Overlay Opacity** — 0 to 100

If text becomes hard to read over a busy image, raise the overlay opacity rather than changing the image.

## Removing "Powered by FlowMattic"

The **Show "Powered by FlowMattic"** toggle is **on by default**. Switch it off to remove the badge from the chat window.

## Text your visitors see

These two live on the **Settings** tab rather than Theme:

- **Welcome Message** — the assistant's opening line. If you leave it empty, visitors see "How can I help you today?"
- **Input Placeholder** — the grey hint in the message box. Empty falls back to "Write your message…"

The chat header shows the **assistant's name**, so rename the assistant itself if you want different header text — there is no separate header title field.

## Embedding, and which settings apply

Three ways to embed, from the **Embed** section:

**1. Shortcode**

```
[flowmattic_chatbot chatbot_id="YOUR_ID" width="600px" height="800px"]
```

`width` defaults to `100%` and `height` to `600px`. This renders the chatbot inline on the page.

**2. iFrame** — paste the supplied `<iframe>` snippet and set the width and height on the tag itself.

**3. Floating widget** — a `<script>` tag that adds the launcher bubble in the corner of every page it loads on.

**Only the floating widget uses Widget Position, Chatbox Icon, Chatbox Icon Background and Button Label.** With the shortcode or iframe, the size comes from the embed code, not from any theme setting — there is no width or height option on the Theme tab.

One thing that is automatic: an iframe-embedded chatbot **expands to the full width of its container**. You do not need to configure this.

There is also a **Share Chatbot** option that gives you a direct URL, if you would rather link to the assistant than embed it.

## What is not available

- **There is no custom CSS box.** Styling is limited to the options above.
- There is no Gutenberg block for the chatbot — use the shortcode.
- There are no top-of-screen widget positions.

## Related

- [How to Set Up Your AI Assistant Chatbot in FlowMattic](/kb/ai-assistant-setup-guide)
- [Managing Content Sources for Your AI Assistant Chatbot](/kb/ai-assistant-content-sources)
- [Collect leads and schedule meetings from your chatbot](/kb/collect-leads-and-schedule-meetings-from-your-chatbot)

---

# Custom Webhook Slug: Stable, Human-Readable Webhook URLs in FlowMattic

Source: https://support.flowmattic.com/kb/article/167/custom-webhook-slug-stable-human-readable-webhook-urls-in-flowmattic

The **Custom Webhook Slug** is an optional field on the FlowMattic **Webhooks by FlowMattic** trigger that lets you give your incoming webhook a stable, human-readable URL (for example `/webhook/capture/orders-api`) instead of relying only on the long, auto-generated workflow ID. The original workflow ID URL keeps working too, so both point to the same workflow at the same time.

## What the Webhook trigger is

When you start a workflow with the **Webhooks by FlowMattic** trigger and choose the **Capture Webhook Response** event, FlowMattic gives you a unique **Webhook URL**. You send (POST or GET) data to that URL from another app or website, and the workflow runs with that data.

By default, the URL looks like this, where the last segment is your workflow's auto-generated ID:

```
https://your-site.com/webhook/capture/abc123def456
```

If your site uses the REST-style base instead (set under **Settings → Core Integrations**), the same workflow's URL looks like:

```
https://your-site.com/wp-json/webhook/capture/abc123def456
```

Both forms are produced by FlowMattic; the slug feature works with whichever base your site is configured to use.

## The problem it solves

The default URL contains the **workflow ID**, and that ID is tied to the specific workflow row in your database. It is not something you control or can keep:

- If you **delete and recreate** the workflow, the new copy gets a brand-new ID, so its webhook URL changes.
- If you **export a workflow from one site and import it** to another (for example, moving from staging to production), the imported copy gets a new ID on the destination site.

In all of these cases, any external app, integration, or service that was pointed at the old `/webhook/capture/<old-id>` URL stops reaching your workflow, and you have to go update the URL everywhere it was used.

The **Custom Webhook Slug** fixes this by letting you choose your own permanent identifier for the URL. You decide on a name like `orders-api`, register it once, and keep using it even if the underlying workflow is recreated — you just re-apply the same slug to the new workflow.

## Where to set the Custom Webhook Slug

1. Open your workflow in the **Workflow Builder**.
2. Click the **trigger step** (the first step) to open its settings. The trigger must be **Webhooks by FlowMattic** with the **Capture Webhook Response** event.
3. In the trigger settings you'll see the **Webhook URL** field at the top, and directly below it the **Custom Webhook Slug** field, marked **Optional**.
4. Type your desired slug (for example `orders-api`) into the **Custom Webhook Slug** field.

As you type, the **Webhook URL** field above updates live to preview the URL your slug produces. If you leave the field blank, FlowMattic uses the auto-generated workflow ID URL as before.

![The Webhook trigger settings showing the Webhook URL field at the top and the Custom Webhook Slug field (marked Optional) directly below it, with a slug typed in and the URL preview updated](https://assets.infidesk.support/kb/inline/2026/07/Vzi3djAQD6wiK3NI3wXjTPu8EqmCkn60KvhdQvct.png)

### The resulting URL format

With a slug of `orders-api`, the **Webhook URL** field shows your stable URL:

```
https://your-site.com/webhook/capture/orders-api
```

(or the `/wp-json/webhook/capture/orders-api` form if your site uses the REST-style base). The slug simply replaces the workflow ID in the last segment of the path.

## Both URLs work at the same time

This is the key behavior: adding a custom slug does **not** disable the original URL.

- The **slug URL** — `/webhook/capture/orders-api`
- The **original workflow ID URL** — `/webhook/capture/abc123def456`

both hit the **same workflow simultaneously**. Internally, FlowMattic keeps a registry that maps each slug to its workflow ID. When a request comes in, FlowMattic checks whether the identifier in the URL matches a registered slug; if it does, it resolves to that workflow's ID, and if it doesn't, it treats the identifier as a workflow ID directly. Either way, the same workflow runs.

This means you can adopt a slug without breaking anything that was already calling the old URL — there's no migration step required, and you can switch your external integrations over to the cleaner slug URL whenever you're ready.

## Validation and uniqueness rules

When you save the workflow, FlowMattic validates the slug before storing it. If the slug is invalid, the save is stopped and you'll see an inline error message under the field rather than a silently broken URL. The rules are:

- **Allowed characters and length:** The slug must be **3 to 64 characters** and may contain only **letters, numbers, dashes (`-`), and underscores (`_`)**. No spaces, slashes, or other symbols. The builder validates this as you type and shows the message: *"Slug must be 3-64 characters; letters, numbers, dashes and underscores only."*
- **Must be unique across workflows:** A slug can only belong to one workflow. If another workflow already uses that slug, you'll get *"This custom webhook slug is already in use by another workflow."* (Re-saving the same workflow with its own existing slug is fine.)
- **Case-insensitive matching:** Slugs are stored and matched in lowercase, so `Orders-API` and `orders-api` are treated as the same slug — you can't have both.
- **Reserved words are blocked:** Certain identifiers are reserved by FlowMattic and can't be used, including `fm_oauth` (the OAuth callback target), `capture`, `webhook`, `oauth`, and `wp-json`. Choosing one returns *"This custom webhook slug is reserved, please choose another."*
- **Can't shadow a real workflow ID:** If your slug happens to exactly match an existing workflow's ID, it's rejected with *"This custom webhook slug matches an existing workflow ID, please choose another."* — this protects the fallback behavior that lets old ID URLs keep working.

![inline-validation-error](https://assets.infidesk.support/kb/inline/2026/07/XIKIyegx3XZZ5BYmarTGRYa7jv4rnPmdxUQYsm6s.png)

## How to use it end to end

1. In the **Webhooks by FlowMattic** trigger, enter a clear, stable slug (such as `orders-api` or `stripe_events`) in the **Custom Webhook Slug** field.
2. Confirm the **Webhook URL** preview shows the slug-based URL, then copy that URL.
3. Click **Capture Webhook Data** and send a test request to the slug URL from your external app so FlowMattic captures the sample payload. (The slug routes correctly even during this capture step, before the workflow is fully saved.)
4. **Save** the workflow. This registers the slug, and from now on both the slug URL and the workflow's original ID URL deliver to this workflow.
5. Paste the slug URL into the external app, service, or integration that will send the webhook.

![capture-response](https://assets.infidesk.support/kb/inline/2026/07/atlxVdWQqISUs3OoSRgVS7XVVjFLOSASKbRmSktg.png)

If you later need to recreate the workflow (or import it onto another site), open the new copy's **Webhooks by FlowMattic** trigger, type the **same slug** into the **Custom Webhook Slug** field, and save. Your external URL stays exactly the same — only the workflow behind it changed.

To stop using a slug, clear the **Custom Webhook Slug** field and save; the slug is released (and becomes available again), and the workflow falls back to its auto-generated workflow ID URL. The slug is also released automatically if you change the trigger to a non-webhook type or delete the workflow.

---

# Date/Time Formatter

Source: https://support.flowmattic.com/kb/article/36/datetime-formatter

Date/Time Formatter by FlowMattic is a tool or feature within the FlowMattic application that allows users to manipulate dates and times in their workflows. It provides various functionalities such as adding or subtracting time from a given date, modifying the current date, and comparing two dates.

With Date/Time Formatter, users can customize the format of dates, convert them to different formats, and perform calculations or operations on them. It offers options to specify the desired date format, time zone, and time units for modification. Users can also compare two dates and specify the formats for the start and end dates.

The tool is designed to simplify date and time manipulation tasks within FlowMattic, making it easier for users to perform calculations, track durations, and format dates according to their specific needs. It enhances workflow automation by providing flexible date and time manipulation capabilities, ensuring accurate and efficient handling of temporal data.

#### Step-by-Step Documentation: Date/Time Formatter by FlowMattic

1. Choose Application Date/Time Formatter: Select the "Application Date/Time Formatter" action from the available actions in your FlowMattic application.

2. **Action Event Options:**
In the Action Event section, you will find three options to choose from:

2.1 Add/Subtract Time: Select this option if you want to manipulate the date by adding or subtracting time.

2.2 Modify Current Date: Choose this option if you want to modify the current date.

2.3 Compare Two Dates: Select this option if you want to compare two dates.

3. **Add/Subtract Time:**

3.1 Enter Date: Provide the date you would like to manipulate. To use the current date, use the input \[current\_date\].

3.2 Expression: Specify the amount of time you want to add or subtract from the date. Use the format \[+/- time\]. Examples: +8 hours 1 minute, +1 month -2 days, -1 day +8 hours.

3.3 To Format: Enter the desired format to which the date should be converted.

3.4 From Format: Optionally, you can specify the format of the original date. 

4. **Modify Current Date:**

4.1 Date Output Format: Specify the desired format for the modified date.

4.2 Time Zone: Select the desired time zone by choosing a city. This is used for the current date and time.

4.3 Operation: Select the operation to determine how you want to modify the date. Like add or subtract the date.

4.4 Time Unit: Choose the time unit (e.g., hours, days, months) to modify the date.

4.5 Time Unit Value: Enter the value for the selected time unit to modify the date.

5. **Compare Two Dates:**

5.1 Enter Start Date: Provide the start date for comparison. Use the format \[dd:mm:yy\]. For the current date, use the code \[current\_date\].

5.2 Enter End Date: Enter the end date for comparison. Use the format \[dd:mm:yy\]. The time zone is assumed to be the same for both dates.

5.3 Start Date Format: Specify the format of the start date (e.g., "ddd MM DD HH:mm" for "Sun Jan 22 23:04").

5.4 End Date Format: Specify the format of the end date (e.g., "ddd MM DD HH:mm" for "Sun Jan 22 23:04").

By following these steps, you can effectively use the Date/Time Formatter by FlowMattic to manipulate dates, add or subtract time, modify the current date, and compare dates in your workflow.

---

# Delay

Source: https://support.flowmattic.com/kb/article/21/delay

The **Delay module** in FlowMattic is designed to introduce a wait time between actions or steps in a workflow. This feature is particularly useful when an action needs to be executed after a certain period of time has passed or when actions must be spaced out to avoid system overload, rate limits, or errors. By using the Delay module, users can ensure their workflows operate at the correct pace, helping to improve workflow efficiency and system stability. With this feature, FlowMattic users can build flexible, responsive workflows that are aligned with their business needs.

The delay period can be fully customized, ranging from seconds to days, allowing users to set precise intervals based on their specific requirements.

### When to Use the Delay Module

The Delay module can be useful in scenarios where:

- You need to pause before executing an action (e.g., waiting a few minutes before sending a confirmation email).

- You want to avoid exceeding API rate limits by spacing out API requests.

- You need to delay the final step in a workflow to allow external processes to complete (e.g., waiting for a payment confirmation before triggering fulfillment).

### Step-by-Step Guide to Using the Delay Module

Assuming you have already created a workflow with several action steps and now want to delay the execution of the last action for a few days, here’s how you can use the Delay module.

#### 1\. Add the Delay Module

- Click on **“Add New Action”** at the point where you want to introduce the delay in the workflow (typically right before the action you wish to delay).

- From the action options, select **“Delay by FlowMattic”**.

#### 2\. Choose the Action Event for the Delay Module

When configuring the Delay module, you can choose from two types of delay events:

- **Delay For**: This option delays the next action by a specified amount of time.

- **Delay Until**: This option delays the next action until a specific date and time.

Let’s break these options down further:

#### 2.1. Delay Until

Choose **“Delay Until”** if you need to delay the next action until a specific date and time in the future.

- **Use Case**: This option is ideal for situations where a task needs to happen at a particular time (e.g., sending a reminder email on the last day of the month).

- **Configuration**: Input the future **date** and **time** using the provided time format.

- **Example**: If you want the next step to execute on **December 31st at 9:00 AM**, you would enter that specific date and time.

#### 2.2. Delay For

Choose **“Delay For”** if you want to introduce a delay for a specific amount of time before the next action.

- **Use Case**: This is ideal when you want to pause for a set period, like delaying an action for a few minutes, hours, or days.

- **Configuration**: Set the delay in terms of a time unit and a value. FlowMattic provides the following time units for the delay:

- **Seconds**

- **Minutes**

- **Hours**

- **Days**

- **Weeks**

#### 3\. Set the Delay Value

After choosing the delay type, set the **Delay Value** (the amount of time) and the **Delay Unit**. For example:

- If you want to delay the action by **2 hours**, select **Hours** as the unit and enter **2** as the value.

- If you want to delay for **3 days**, select **Days** and enter **3** as the value.

#### 4\. Test the Delay

After setting up the delay, you can click **“Save & Test Action”** to verify that the delay is configured correctly. In the test mode, the workflow will simulate the delay settings and display the expected wait time.

#### 5\. Save the Workflow

Once you have tested the delay and confirmed the configuration, click on **Save Workflow**. Your workflow will now run with the specified delay between the steps.

* * *

### Practical Use Cases of the Delay Module:

1. **Email Campaign**: You want to send a follow-up email 24 hours after a user signs up. You can introduce a **24-hour delay** after the sign-up step and then trigger the email sending step.

3. **Waiting for External Processes**: When integrating with third-party services like payment gateways, you may need to delay the next workflow step to wait for payment confirmation. For example, if payment confirmation typically takes 15 minutes, you can set a **15-minute delay** before processing the next action (like order fulfillment).

5. **Event Reminders**: If you’re running an event and want to send reminders at specific intervals (e.g., 1 day and 1 hour before the event), you can use the **Delay Until** feature to send the reminders at precise times.

* * *

### Key Benefits of the FlowMattic Delay Module:

- **Customizable Delays**: Tailor the delay period to your exact needs, whether it’s in seconds, minutes, hours, days, or weeks.

- **Control Workflow Pace**: Prevent workflows from executing too quickly and overwhelming APIs or other services.

- **Precise Scheduling**: Use the Delay Until option for scheduling actions at exact times, enhancing control over workflow timing.

By incorporating the Delay module into your workflows, you can enhance control, precision, and flexibility, allowing your automated processes to run efficiently and smoothly, even when dealing with complex or time-sensitive actions.

* * *

This documentation provides a comprehensive understanding of the Delay module, with actionable steps to incorporate time-based controls into your workflows effectively.

---

# Delay or Scheduled Workflows not working

Source: https://support.flowmattic.com/kb/article/10/delay-or-scheduled-workflows-not-working

If your delayed or scheduled workflows in FlowMattic are not working as expected, the most common culprit is a malfunctioning **WordPress Cron**. By default, WordPress relies on its built-in cron system (WP-Cron) to trigger scheduled tasks, which may fail to execute properly on low-traffic sites.

* * *

### **Why It Happens**

The WordPress cron system depends on website traffic to function. If your site has low traffic or no visitors during certain periods:

- Scheduled tasks, including FlowMattic workflows with delays, may not run.

- Delays in workflows may not trigger as expected, causing interruptions in your automation.

* * *

### **Solution: Set Up a Server-Side Cron**

To ensure consistent execution of delayed and scheduled workflows, you can replace WordPress Cron with a reliable **server-side cron job**. Here's how:

* * *

#### **1\. Using Cloudflare to Trigger the Cron**

If you’re using Cloudflare, you can leverage its features to trigger the cron periodically:

1. **Set Up a Custom Cron URL**:
    - Install a plugin like **WP Crontrol** to generate a cron trigger URL for your WordPress site.

3. **Create a Scheduled Task in Cloudflare**:
    - Log in to your Cloudflare account.
    
    - Navigate to **Workers** or **Scheduled Tasks** (depending on your Cloudflare plan).
    
    - Set up a task to call the cron URL every 5 minutes (or a frequency suitable for your workflows).

5. **Save and Test**:
    - Confirm that the cron URL is being triggered as expected.
    
    - Test your delayed or scheduled workflows in FlowMattic.

* * *

#### **2\. Configure a Cron Job on Your Server**

If you have access to your server, setting up a native cron job is the most reliable solution:

1. **Disable WordPress Cron**:
    - Edit your `wp-config.php` file and add the following line: `define('DISABLE_WP_CRON', true);`

3. **Set Up a Server-Side Cron**:
    - Access your server control panel (e.g., cPanel, Plesk) or use SSH if you have root access.
    
    - Add a new cron job to execute WordPress cron tasks by running the following command every 5 minutes: `wget -q -O - https://yourwebsite.com/wp-cron.php?doing_wp_cron &gt; /dev/null 2&gt;&1`
    
    - Replace `https://yourwebsite.com` with your actual site URL.

5. **Contact Your Hosting Provider**:
    - If you’re unfamiliar with server configurations, contact your hosting provider and ask them to set up a cron job for you.

* * *

### **Why Server-Side Cron is Better**

- **Reliable Execution**: Unlike WordPress Cron, server-side cron jobs don’t depend on site traffic, ensuring tasks are triggered on time.

- **Better Performance**: Offloading cron execution to the server reduces the burden on WordPress, improving site performance.

* * *

### **Conclusion**

If your delayed or scheduled workflows are not working, the issue likely stems from WordPress Cron's dependency on traffic. Setting up a server-side cron, either through Cloudflare or your hosting server, ensures reliable execution of scheduled tasks. Once configured, you can trust your workflows to run smoothly, regardless of your site traffic levels. If you need further assistance, don’t hesitate to reach out to the FlowMattic support team!

---

# Design an image template

Source: https://support.flowmattic.com/kb/article/183/design-an-image-template

This guide covers building an image template by hand in the visual editor. Once saved, a workflow can render it with live data.

## Step 1 — Create a new template

1. Open **FlowMattic → Image Templates**.
2. Click **New Image Template** and enter a **Template Name**, such as `Blog OG Card`.
3. Under **Choose a Starting Point**, pick a path: **Start from a prebuilt template**, **Generate with AI**, or **Create from scratch**.

![The New Image Template modal with the Template Name field and the Choose a Starting Point options](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-image-template-02-new-modal.png)

The starting point sets the canvas dimensions, which become the final image size. You can change them later on the **Template** tab using the **Preset** dropdown or the **W** and **H** inputs.

## Step 2 — Add and arrange elements

The editor has three areas: the **Library** panel on the left, the canvas in the centre, and the inspector on the right.

1. On the **Elements** tab of the Library panel, drag an element onto the canvas — `Heading`, `Paragraph`, `Image`, `Avatar`, `Button`, `Icon`, `Shape`, `Pattern Shape`, `Border Shape`, `Waves`, `Arrow`, `Callout Lines`, `Ribbon`, `Badge`, `Coupon`, `Divider`, `Logo`, or `QR Code`. Clicking a tile adds it to the centre of the canvas.
2. Click an element to select it, then edit it on the **Element** tab of the inspector — typography, colour, size, position, and element-specific options.
3. Drag elements to reposition them and use the handles to resize.

![image-template-elements](https://assets.infidesk.support/kb/inline/2026/07/4Gl2FyXNs4gWFUJeYgVDje1EiW4xD6wZJNtr3SVq.png)

## Step 3 — Set the background

Open the **Template** tab of the inspector and set the **Background**. Its **Type** can be `Gradient`, `Solid`, `Pattern`, or `Image`.

## Step 4 — Save the template

Click **Save**. The design is stored and can now be edited or rendered at any time.

## Step 5 — Render a test image

1. Return to the **Image Templates** listing.
2. Open the template's kebab menu and click **Download Image**.
3. In the **Download Image** modal, render and save the PNG. It uses the template's sample values by default — you can supply your own through the **Dynamic Data (JSON)** field — so you can confirm the output matches your design.

![Image Templates list with a template's action menu open and Download Image highlighted](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-image-template-01-list-download-image.png)

To make the template dynamic — so a workflow can fill it with live data — add tokens next. See *Add tokens and sample data to an image template*.

---

# Display FlowMattic Tables (managed) on the frontend

Source: https://support.flowmattic.com/kb/article/232/display-flowmattic-tables-on-frontend

You can display any **FlowMattic Table** (the managed cloud database) on the front end of your site with the `[flowmattic_table]` shortcode — inside a page, post, or widget — and, if you choose, let logged‑in users **edit cells and add rows** right from that page. The front‑end table renders with the same rich cells you see in the FlowMattic Tables editor (ratings, dropdowns, currencies, dates, and so on), plus optional search, sorting, and pagination.

> **Which tables is this for?** This guide covers **FlowMattic Tables** — the managed database service under Dashboard → FlowMattic → **FlowMattic Tables**. If you store data in your own WordPress/connected database (**WP Tables**) instead, see [Display WP Tables on the frontend](https://support.flowmattic.com/portal/flowmattic/kb/article/231/display-wp-tables-on-frontend) — the shortcode is the same, only the `database` value differs.

The fastest way to set this up is the built‑in **Share / Embed** generator — it fills in the right settings for you, including `database="fm_managed"`.

## Generate the shortcode

Open your table in **FlowMattic Tables** and click **Share** in the toolbar. Tick the columns you want to show, choose the options you need, and copy the generated shortcode — it updates live as you change options.

![The Share generator on a FlowMattic Table](https://assets.infidesk.support/products/flowmattic/kb-images/tables-managed/01-share-modal.png?v=2)

Notice the shortcode already includes `database="fm_managed"` — that's what points it at the managed service instead of a local database.

## What the options do

**Columns to display** — Pick which columns appear on the front end, in the order you tick them. Anything you leave unchecked is never sent to the browser, so hidden columns stay private.

**Let logged‑in users edit cells** — Turns on inline editing. When it's on, choose **Who can write** (the role/capability a visitor must have). Editing is only ever offered to logged‑in users who have that capability.

**Let logged‑in users add rows** — Adds an **Add row** button so permitted users can create new records. For safety, **deleting rows is never possible** from a front‑end table, and neither are column or structural changes.

**Viewer controls** — Optionally show a **Search box**, make columns **sortable**, turn **pagination** on/off (with a rows‑per‑page value), and enable **Only show the user's own rows** so each logged‑in user sees just the records they own.

**Size** — Set the embed **Width** and **Height** (any CSS length, e.g. `100%`, `620px`).

## Paste it on a page

Add the copied shortcode to any page, post, or shortcode/HTML block and publish. The table appears with the columns and controls you chose, rendered with FlowMattic Tables' rich cells:

![A FlowMattic Table displayed on the front end](https://assets.infidesk.support/products/flowmattic/kb-images/tables-managed/02-frontend-table.png)

## Editing and adding rows

When you enable editing or adding, a few things are handled for you automatically and safely:

- **Who did what is recorded.** To track edits, add a **Created by** and/or **Modified by** column to your table. FlowMattic stamps the current user into these automatically — the value can't be spoofed from the browser. The generator reminds you when a table has no such column.
- **Only the columns you allowed are writable.** Even if a visitor tampers with the request, the server only accepts changes to the columns your shortcode granted — every other column is ignored.
- **"Only my rows" is enforced.** With this option on, a user can only see *and* edit the rows they own (matched via the Created by / Modified by column).
- **No deleting, ever.** Front‑end tables never expose delete, nor add/edit/delete‑column, export, or views.

To edit a cell, a permitted user double‑clicks it, makes the change, and clicks **Save**. New rows are added with **Add row** and saved the same way.

## Shortcode reference

If you'd rather write the shortcode by hand, here are all the attributes:

| Attribute | Default | What it does |
|---|---|---|
| `table_name` | — | **Required.** The table's slug (shown in the FlowMattic Tables editor URL). |
| `database` | `local` | Use **`fm_managed`** for FlowMattic Tables (the managed service). |
| `columns` | *(all)* | Comma‑separated list of columns to display, in order. |
| `editable` | `no` | `yes` to allow inline cell editing for permitted users. |
| `editable_columns` | *(all shown)* | Comma‑separated subset of the displayed columns that may be edited. |
| `allow_insert` | `no` | `yes` to show an **Add row** button. |
| `capability` | `edit_posts` | The capability a user must have to edit or add rows. |
| `search` | `no` | `yes` to show a search box. |
| `sortable` | `no` | `yes` to let visitors sort by clicking a column header. |
| `pagination` | `yes` | `no` to show all rows without paging. |
| `page_size` | `15` | Rows per page when pagination is on. |
| `only_mine` | `no` | `yes` to show each logged‑in user only their own rows. |
| `filter_column` / `filter_value` | — | Pre‑filter the table to rows where a column equals a value. |
| `width` / `height` | `100%` / `800px` | The embed's size (any CSS length). |

**Example — a read‑only sales table with search, sorting and paging:**

```
[flowmattic_table table_name="sales_records" database="fm_managed" columns="region,country,item_type,units_sold,total_profit" search="yes" sortable="yes" page_size="10"]
```

**Example — an editable "my submissions" table where authors edit only their own rows:**

```
[flowmattic_table table_name="submissions" database="fm_managed" columns="title,status,notes" editable="yes" allow_insert="yes" capability="edit_posts" only_mine="yes"]
```

## A note on security

Front‑end editing is safe by design. Every embed carries a signed permission token that the server verifies on each read and write, so the browser can never grant itself more than the shortcode allows. Writes additionally require a logged‑in user with the chosen capability, only touch the columns you permitted, and stamp Created by / Modified by on the server. Deleting and any structural changes are never available from the front end.

## Related

- [Display WP Tables on the frontend](https://support.flowmattic.com/portal/flowmattic/kb/article/231/display-wp-tables-on-frontend) — the same shortcode for tables stored in your own WordPress/connected database.

---

# Display WP Tables on the frontend (shortcode + Share button)

Source: https://support.flowmattic.com/kb/article/231/display-wp-tables-on-frontend

WP Tables aren't just for the admin area. With the `[flowmattic_table]` shortcode you can display any WP Table on the front end of your site — inside a page, post, or widget. The front‑end table renders with the same rich cells you see in the admin editor (ratings, links, currencies, statuses, and so on), plus optional search, sorting, and pagination.

> **Which tables is this for?** This guide covers **WP Tables** (Dashboard → FlowMattic → **WP Tables**), which store their data in your own WordPress/connected database. Using the managed **FlowMattic Tables** service instead? See [Display FlowMattic Tables (managed) on the frontend](https://support.flowmattic.com/portal/flowmattic/kb/article/232/display-flowmattic-tables-on-frontend) — the shortcode is the same, only the `database` value differs.

The fastest way to set this up is the **Share / Embed** generator — no need to remember any attributes.

## Generate the shortcode with "Share / Embed"

You can open the generator from two places:

- **WP Tables list** — hover the ⋮ menu on any table and choose **Share / Embed**.
- **Table editor** — open a table and click **Share** in the toolbar.

![The Share / Embed action on the WP Tables list](https://assets.infidesk.support/products/flowmattic/kb-images/tables-frontend/01-share-listing.png)

The generator opens with every column selected. Tick only the columns you want to show, then set the options you need.

![WP Tables - Select column for shortcode](https://assets.infidesk.support/kb/inline/2026/07/74FbgauSk8yAM7FHfz8YkYJvyLA7O8AOd2OtsrtS.jpg)

As you change options, the shortcode at the bottom updates live. Click **Copy shortcode** when you're done.

![WP Tables - shortcode generator](https://assets.infidesk.support/kb/inline/2026/07/HHngbNUhDygQp6GqMUOori9VFM4hhYmeXw6FYT1h.jpg)

## What the options do

**Columns to display** — Pick which columns appear on the front end, in the order you tick them. Anything you leave unchecked is never sent to the browser, so hidden columns stay private.

**Viewer controls** — Optionally show a **Search box**, make columns **sortable**, turn **pagination** on/off (with a rows‑per‑page value), and enable **Only show the user's own rows** so each logged‑in user sees just the records they own.

**Size** — Set the embed **Width** and **Height** (any CSS length, e.g. `100%`, `620px`).

## Paste it on a page

Add the copied shortcode to any page, post, or shortcode/HTML block and publish. That's it — the table appears with the columns and controls you chose:

![A WP Table displayed on the front end](https://assets.infidesk.support/products/flowmattic/kb-images/tables-frontend/04-frontend-table.png)

## Shortcode reference

If you'd rather write the shortcode by hand, here are all the attributes:

| Attribute | Default | What it does |
|---|---|---|
| `table_name` | — | **Required.** The table's name (e.g. `Contact List`). |
| `database` | `local` | The database the table lives on. Leave as `local` for standard WP Tables. |
| `columns` | *(all)* | Comma‑separated list of columns to display, in order. |
| `search` | `no` | `yes` to show a search box. |
| `sortable` | `no` | `yes` to let visitors sort by clicking a column header. |
| `pagination` | `yes` | `no` to show all rows without paging. |
| `page_size` | `15` | Rows per page when pagination is on. |
| `filter_column` / `filter_value` | — | Pre‑filter the table to rows where a column equals a value. |
| `width` / `height` | `100%` / `800px` | The embed's size (any CSS length). |

**Example — a contact list with search, sorting and paging:**

```
[flowmattic_table table_name="Contact List" columns="first_name,last_name,email,score" search="yes" sortable="yes" page_size="10"]
```

## A note on security

Every embed carries a signed permission token that the server verifies on each read and write, so the browser can never grant itself more than the shortcode allows.

## Related

- [Display FlowMattic Tables (managed) on the frontend](https://support.flowmattic.com/portal/flowmattic/kb/article/232/display-flowmattic-tables-on-frontend) — the same shortcode for the managed FlowMattic Tables service.

---

# DNS / Domain Tools Integration in FlowMattic

Source: https://support.flowmattic.com/kb/article/128/dns--domain-tools-integration-in-flowmattic

The DNS / Domain Tools app is a built-in FlowMattic application that provides comprehensive domain and network diagnostic capabilities. Perform DNS lookups, verify email domains, check SSL certificates, inspect HTTP headers, and test port connectivity — all within your automated workflows. No external API key or connection is required.

---

## Overview

Domain and network diagnostics are essential for monitoring, validation, and troubleshooting. The DNS / Domain Tools app uses PHP's built-in network functions to perform all operations directly from your server — no external services or API keys needed, and no data is transmitted to third-party services.

---

## Connection Setup

DNS / Domain Tools is a **core utility app** — no connection setup is needed.

- No API key required
- No external service to configure
- All operations run locally on your server
- Available immediately in all FlowMattic installations using FlowMattic v6+

Simply select **DNS / Domain Tools** when adding an action step to your workflow.

---

## Available Actions

The DNS / Domain Tools app provides **7 actions** for domain and network diagnostics.

### 1. DNS Lookup

Retrieve DNS records for a domain, including A, AAAA, MX, NS, TXT, CNAME, SOA, and SRV records.

**Configuration:**

| Field | Required | Description |
|-------|----------|-------------|
| Domain | Yes | Domain name to look up (e.g., `example.com`). Protocols and paths are automatically stripped. |
| Record Type | No | Type of DNS record to retrieve. Defaults to **All Records**. |

**Record Type Options:**

| Option | Description |
|--------|-------------|
| All Records | Returns all available record types |
| A (IPv4 Address) | Standard IPv4 address records |
| AAAA (IPv6 Address) | IPv6 address records |
| MX (Mail Exchange) | Mail server records |
| NS (Name Server) | Nameserver records |
| TXT (Text) | Text records (SPF, DKIM, DMARC, etc.) |
| CNAME (Canonical Name) | Alias records |
| SOA (Start of Authority) | Start of Authority records |
| SRV (Service) | Service location records |

**Output:**

| Field | Description |
|-------|-------------|
| `status` | `success` or `error` |
| `domain` | The queried domain |
| `record_type` | The record type requested |
| `record_count` | Number of records found |
| `records` | Array of DNS records with type-specific fields |
| `ipv4_addresses` | List of IPv4 addresses (when A records are included) |

![Workflow Builder ‹ FlowMattic — WordPress 2026-03-01 at 12.56.49 AM.png](/storage/kb-images/197983339c-inline.png)

---

### 2. Reverse DNS Lookup

Resolve an IP address to its hostname and retrieve PTR records.

**Configuration:**

| Field | Required | Description |
|-------|----------|-------------|
| IP Address | Yes | IPv4 or IPv6 address to resolve (e.g., `8.8.8.8`). |

**Output:**

| Field | Description |
|-------|-------------|
| `status` | `success` or `error` |
| `ip_address` | The IP that was looked up |
| `hostname` | Resolved hostname |
| `resolved` | `true` if hostname was successfully resolved |
| `ip_version` | `IPv4` or `IPv6` |
| `ptr_records` | Array of PTR records (if available) |

> **Use Case:** Verify reverse DNS (rDNS) configuration for mail servers, or investigate IP addresses found in logs.

---

### 3. MX Lookup

Get mail server (MX) records for a domain, sorted by priority, with IP resolution.

**Configuration:**

| Field | Required | Description |
|-------|----------|-------------|
| Domain | Yes | Domain name to look up MX records for (e.g., `example.com`). |

**Output:**

| Field | Description |
|-------|-------------|
| `status` | `success` |
| `domain` | The queried domain |
| `has_mx` | `true` if MX records exist |
| `mx_count` | Number of MX records found |
| `mx_records` | Array of MX records sorted by priority |

Each MX record contains:

| Field | Description |
|-------|-------------|
| `host` | Mail server hostname |
| `priority` | MX priority (lower = higher priority) |
| `ip` | Resolved IPv4 address of the mail server |

![Workflow Builder ‹ FlowMattic — WordPress 2026-03-01 at 12.57.41 AM.png](/storage/kb-images/0e423ab6c5-inline.png)

![Workflow Builder ‹ FlowMattic — WordPress 2026-03-01 at 12.58.48 AM.png](/storage/kb-images/0a78ef9166-inline.png)

---

### 4. Verify Email Domain

Check whether a domain or email address can receive emails by verifying MX and A records.

**Configuration:**

| Field | Required | Description |
|-------|----------|-------------|
| Email Address or Domain | Yes | Full email address (e.g., `user@example.com`) or domain name (e.g., `example.com`). |

**Output:**

| Field | Description |
|-------|-------------|
| `status` | `success` or `error` |
| `input` | The original input value |
| `domain` | Extracted domain name |
| `is_email` | `true` if input was an email address |
| `is_valid_format` | `true` if email format is valid (only when `is_email` is true) |
| `can_receive_email` | `true` if domain can receive emails (per RFC 5321) |
| `has_mx_records` | `true` if MX records exist |
| `has_a_record` | `true` if A record fallback is available |
| `has_aaaa_record` | `true` if IPv6 address record exists |
| `is_free_provider` | `true` if domain is a known free email provider |
| `mx_records` | Array of MX records with priority |

**Email Deliverability Logic (RFC 5321):**
- If MX records exist → can receive email
- If no MX but A record exists → can receive email (A record serves as fallback)
- If neither MX nor A records exist → cannot receive email

**Free Email Providers Detected:**
gmail.com, yahoo.com, hotmail.com, outlook.com, aol.com, icloud.com, mail.com, protonmail.com, zoho.com, yandex.com, gmx.com, live.com


> **Use Case:** Validate email addresses in registration workflows, filter out free email providers for B2B lead qualification, or check deliverability before sending important emails.

---

### 5. SSL Certificate Info

Retrieve SSL/TLS certificate details including issuer, expiry date, validity, and Subject Alternative Names.

**Configuration:**

| Field | Required | Description |
|-------|----------|-------------|
| Domain | Yes | Domain name to check (e.g., `example.com`). |
| Port | No | HTTPS port. Defaults to `443`. Use `8443` for alternative HTTPS ports. |

**Output:**

| Field | Description |
|-------|-------------|
| `status` | `success` or `error` |
| `domain` | The checked domain |
| `port` | The port checked |
| `subject` | Certificate subject (common name) |
| `issuer` | Certificate authority organization name |
| `issuer_cn` | Certificate authority common name |
| `valid_from` | Certificate start date |
| `valid_to` | Certificate expiry date |
| `is_valid` | `true` if certificate is currently valid |
| `days_remaining` | Number of days until expiry (0 if expired) |
| `serial_number` | Unique certificate serial number |
| `signature_algorithm` | Algorithm used to sign the certificate |
| `san` | Subject Alternative Names (all domains covered) |

![Workflow Builder ‹ FlowMattic — WordPress 2026-03-01 at 12.59.36 AM.png](/storage/kb-images/e722c954bb-inline.png)

> **Use Case:** Monitor SSL certificate expiry dates across your domains. Set up a scheduled workflow to check certificates and send alerts when `days_remaining` drops below 30.

---

### 6. HTTP Headers

Fetch HTTP response headers from a URL to check server configuration, security headers, and response status.

**Configuration:**

| Field | Required | Description |
|-------|----------|-------------|
| URL | Yes | Full URL or domain name. Protocol is added automatically if missing. |
| Method | No | Request method. Defaults to **HEAD** (faster, headers only). Choose **GET** for a full request. |

**Output:**

| Field | Description |
|-------|-------------|
| `status` | `success` or `error` |
| `url` | The requested URL |
| `method` | The HTTP method used |
| `status_code` | HTTP response code (200, 301, 404, 500, etc.) |
| `status_message` | Status text (OK, Redirect, Not Found, etc.) |
| `content_type` | MIME type of the content |
| `server` | Server software identifier |
| `headers` | Complete key-value object of all HTTP headers |

**Common Headers Returned:**

| Header | Description |
|--------|-------------|
| `content-type` | MIME type of the response |
| `server` | Server software (e.g., Apache, Nginx) |
| `cache-control` | Caching policy |
| `strict-transport-security` | HSTS security header |
| `x-frame-options` | Clickjacking protection |
| `x-content-type-options` | MIME sniffing prevention |

> **Use Case:** Monitor website uptime by checking status codes, audit security headers across your sites, or verify server configurations.

---

### 7. Check Port

Test if a specific port is open on a host to verify service availability.

**Configuration:**

| Field | Required | Description |
|-------|----------|-------------|
| Host | Yes | Domain name or IP address (e.g., `example.com` or `192.168.1.1`). |
| Port | Yes | Port number to check (1–65535). |
| Timeout | No | Maximum seconds to wait. Defaults to `5`. Range: 1–30 seconds. |

**Output:**

| Field | Description |
|-------|-------------|
| `status` | `success` or `error` |
| `host` | The checked host |
| `port` | The checked port |
| `service` | Service name for common ports (see table below) |
| `is_open` | `true` if the port is open and accepting connections |
| `response_time_ms` | Connection time in milliseconds (0 if port is closed) |
| `error_code` | Error code (0 = success) |
| `error_message` | Error description (empty if success) |

**Common Port / Service Mapping:**

| Port | Service | Port | Service |
|------|---------|------|---------|
| 21 | FTP | 443 | HTTPS |
| 22 | SSH/SFTP | 465 | SMTPS |
| 25 | SMTP | 587 | SMTP Submission |
| 53 | DNS | 993 | IMAPS |
| 80 | HTTP | 995 | POP3S |
| 110 | POP3 | 3306 | MySQL |
| 143 | IMAP | 5432 | PostgreSQL |


> **Use Case:** Monitor server availability, verify that services are running (SSH, MySQL, Redis), or perform connectivity troubleshooting within your workflows.

---

## Workflow Examples

### Example 1: SSL Certificate Monitoring

Monitor SSL certificates across multiple domains and alert before expiry.

1. **Schedule Trigger** — Run weekly.
2. **DNS / Domain Tools > SSL Certificate Info** — Check `domain1.com`.
3. **Branch** — If `{DNS1.days_remaining}` is less than 30...
4. **Email** — Send alert: "SSL certificate for domain1.com expires in {DNS1.days_remaining} days."


### Example 2: Email Validation Pipeline

Validate email addresses before adding them to a mailing list.

1. **Webhook Trigger** — Receive email address.
2. **DNS / Domain Tools > Verify Email Domain** — Check `{Trigger1.email}`.
3. **Branch** — If `{DNS1.can_receive_email}` is `true` AND `{DNS1.is_free_provider}` is `false`...
4. **Mailchimp** — Add to mailing list.

### Example 3: Website Uptime Monitoring

Check multiple websites and alert on downtime.

1. **Schedule Trigger** — Run every 15 minutes.
2. **DNS / Domain Tools > HTTP Headers** — Check `https://mysite.com`.
3. **Branch** — If `{DNS1.status_code}` is not `200`...
4. **Slack** — Send alert: "Website is down! Status: {DNS1.status_code} {DNS1.status_message}".

### Example 4: Server Port Monitoring

Verify critical services are running on your server.

1. **Schedule Trigger** — Run hourly.
2. **DNS / Domain Tools > Check Port** — Check port 3306 (MySQL) on `db.example.com`.
3. **Branch** — If `{DNS1.is_open}` is `false`...
4. **Email** — Send alert: "MySQL service appears to be down."

---

## Troubleshooting

| Error Message | Cause | Solution |
|---------------|-------|----------|
| "Domain is required" | Domain field is empty. | Enter a valid domain name. |
| "Invalid IP address format" | Malformed IP address in Reverse DNS. | Enter a valid IPv4 or IPv6 address. |
| "DNS lookup failed" | Domain doesn't exist or DNS is unreachable. | Verify the domain name is correct. |
| "Could not retrieve SSL certificate" | Connection failed or no certificate found. | Verify the domain has HTTPS enabled. |
| "cURL extension is required" | PHP cURL not installed on the server. | Contact your hosting provider. |
| "Port must be between 1 and 65535" | Invalid port number. | Enter a port number in the valid range. |
| "Connection timed out" | Host unreachable or port blocked. | Check host accessibility and firewall rules. |

---

## Summary

| Feature | Details |
|---------|---------|
| **Connection Required** | No (built-in core app) |
| **Available Actions** | 7 (DNS Lookup, Reverse DNS, MX Lookup, Verify Email, SSL Info, HTTP Headers, Check Port) |
| **Triggers** | None |
| **External APIs** | None — all operations use PHP built-in functions |
| **Data Privacy** | No data sent to third-party services |
| **PHP Requirements** | cURL extension (for SSL and Port check) |

---

# Email Parser by FlowMattic

Source: https://support.flowmattic.com/kb/article/14/email-parser-by-flowmattic

The Email Parser module analyses incoming emails' content and identifies specific data pieces, such as names, addresses, phone numbers, and dates. In the context of the Email Parser module that provides data such as Basic Email and Email with file attachments, users can configure the parser to identify and extract specific information. This allows for the efficient and accurate processing of incoming emails, enabling businesses and organizations to streamline their workflows and improve productivity.

One of the primary benefits of the Email Parser module is that it can be integrated with other systems and software, such as CRMs, ERPs, and project management tools. This allows users to automatically transfer data from emails to other systems without manual entry.

## **Step 1: Login to your FlowMattic Account**

To create a new workflow on FlowMattic in WordPress, you need to first log in to your FlowMattic account and navigate to the "Dashboard". Once in the "Dashboard", you can select the "New Workflow" button to begin creating your new workflow..

![](/storage/kb-images/d02582d616-Screenshot-2024-12-03-141729-1.png)

Then, click on New Workflow

![](/storage/kb-images/2351d2da25-Screenshot-2024-12-03-143715.png)

## **Step 2 - Click on Change**

Click on the "Change" button and select "Email Parser by FlowMattic" from the list of available applications. The Email Parser module would be a pre-built module that can be selected as the trigger for our workflow. This module would be designed to parse incoming emails and extract specific data that can be used to trigger the workflow.

![](/storage/kb-images/3ed41e585a-Screenshot-2024-12-03-144819.png)

## **Step 3 - Copy the provided email address in the trigger settings and use it to forward your emails**

In FlowMattic, you will be provided with an email address to which you can forward emails you want to trigger the workflow. This email address would be copied and used to forward relevant emails.

![](/storage/kb-images/dd1c1e24f6-Screenshot-2024-12-03-1506224q2-1024x387.png)

## **Step 4 - Send a test email to the above email address**

To test the workflow, you must send a test email to the email address in step 3. This would allow you to verify that the email parser module works correctly and that the workflow will be triggered as expected.

![](/storage/kb-images/ac84fbd832-Screenshot-2024-12-03-151422-1024x318.png)

## **Step 5 - Click on the capture response button**

Once the Email Parser trigger is set up and you get your custom email, click on the "Capture Response" button in your trigger step to capture the test email so that you can identify the incoming data from your emails.

![](/storage/kb-images/5fea9ee77b-Screenshot-2024-12-03-152056.png)

## **Step 6 - Set workflow LIVE and save it once**

Finally, the user must set the workflow to "live" and save it in FlowMattic. This would ensure that the workflow is executed automatically whenever an email is received and parsed by the email parser module and that the actions defined in step 6 are carried out according to the requirements of the workflow.

![](/storage/kb-images/dfb0b33518-Screenshot-2024-12-03-152519-1024x116.png)

## **Conclusion**

The Email Parser module is a powerful tool that can help businesses streamline workflows and improve efficiency by automating the extraction of essential data from incoming emails. Its integration capabilities and customizable rules suit various industries and use cases. By following these steps and tips, you can use the module effectively and optimize its benefits.

---

# Email SMTP Module

Source: https://support.flowmattic.com/kb/article/44/email-smtp-module

The Email SMTP Module within FlowMattic is an essential feature that facilitates seamless integration with any SMTP provider, ensuring that your emails are reliably delivered directly to the recipient's inbox. This module is designed to enhance email communication by providing robust options for sending emails.

### Configuration Options

**Email Provider**

- **WP Default**: This option should be selected if you have configured SMTP settings via any WordPress plugin. It is a straightforward choice for users who have existing SMTP configurations.

- **FlowMattic Default**: This allows you to set up SMTP settings directly within the FlowMattic environment. It offers a more integrated approach to email management, enabling you to customize your email delivery settings within FlowMattic itself.

- **Custom SMTP**: For those who require a more tailored setup, this option allows you to input specific SMTP details directly into your workflow, providing maximum flexibility and control over email sending parameters.

When choosing your preferred method of sending emails, it is important to note that the WP Default option does not provide error reporting, which may be a consideration for troubleshooting and ensuring successful email delivery.

**From Name**

This field is where you input the name that will appear as the sender of the email. It is crucial for establishing the identity of the email sender.

**From Email**

This is the email address from which the email will be sent. It is important to note that if you are using SMTP with the WP Default option, this setting will not be applicable, as the WP Default configuration sends emails exclusively from the email address specified in the SMTP settings.

**Reply-to Email**

Here, you can specify the email address that will be used as the reply address. It is advisable to ensure that this is different from the 'From Email' address. If they are the same, you may choose to skip this field. Additionally, the WP Default configuration will disregard this setting when used with SMTP plugins.

**To Email Required**

This field is mandatory and requires the email address of the recipient to whom the email will be sent.

**CC Email**

In this section, you can enter the email addresses of recipients who should receive a carbon copy of the email. Multiple email addresses can be included, separated by commas. For example: email1@domain.com, email2@domain.com.

**BCC Email**

This field allows you to enter the email addresses of recipients who should receive a blind carbon copy of the email. Similar to the CC field, multiple email addresses can be included, separated by commas. For example: email1@domain.com, email2@domain.com.

**Email Subject Required**

This is a required field where you enter the subject of your email, which is crucial for conveying the purpose or topic of the email to the recipient.

**Email Body Required**

This field is where you input the main content of the email, which can be in HTML or plain text format. To insert a dynamic tag within the email body, simply type '@' at the desired location, and a popup will appear, allowing you to select the appropriate dynamic tag.

**Attachments**

This option allows you to attach files to your email, providing additional information or resources to the recipient.

---

# Encharge Integration

Source: https://support.flowmattic.com/kb/article/114/encharge-integration

Encharge is a powerful marketing automation platform designed specifically for SaaS businesses and digital product companies. It helps you send behavior-based emails, manage user segments, and create personalized customer journeys based on how users interact with your product. With Encharge, you can automate onboarding sequences, track user engagement, score leads, and nurture customers throughout their lifecycle.

---

## Getting Started with Encharge in FlowMattic

Encharge integrates seamlessly with your existing tools and allows you to build sophisticated email flows, segment users based on their actions, and send targeted messages at the right time to drive conversions and reduce churn.
Follow these simple steps to connect Encharge with FlowMattic and start automating your workflows:

### Step 1: Install the Encharge Integration

1. Navigate to **FlowMattic → Integrations** in your WordPress dashboard
2. Search for "Encharge" in the integrations list
3. Click the **Install** button to activate the Encharge integration
4. Wait for the installation to complete

### Step 2: Connect Your Encharge Account

1. Go to **FlowMattic → Connects**
2. Click the **Connect Integration** button
3. Search for "Encharge" in the available integrations
4. Enter your **Encharge API Key**
   - To get your API key, log in to your Encharge account
   - Visit: [https://app.encharge.io/account/info](https://app.encharge.io/account/info)
   - Copy your API key from the "API Key" section
5. Give your connection a memorable name (e.g., "Encharge Production")
6. Click **Save** to establish the connection

### Step 3: Create Your Workflow

1. Go to **FlowMattic → Workflows**
2. Click **Create New Workflow**
3. Choose **Encharge** as your Trigger or Action based on your requirements:

#### Available Triggers:
- **New User** - Triggers when a new person is created in Encharge
- **User Tagged** - Triggers when a specific tag is added to a person
- **User Untagged** - Triggers when a specific tag is removed from a person
- **User Updated** - Triggers when a person's information is updated
- **User Unsubscribed** - Triggers when a person unsubscribes from emails

#### Available Actions:
- **Create a Person** - Add a new person to Encharge with custom fields
- **Update a Person** - Modify existing person information
- **Get a Person** - Retrieve person details by email or user ID
- **Add Tags to a User** - Apply tags to a person for segmentation
- **Remove Tags from a User** - Remove specific tags from a person
- **Unsubscribe a Person** - Unsubscribe a person from email communications
- **Delete a Person** - Remove a person from Encharge completely
- **Make an API Call** - Execute custom API requests to Encharge

4. Configure the trigger/action settings according to your needs
5. Map the data fields as required
6. Add additional workflow steps if needed

### Step 4: Publish and Activate

1. Review your workflow configuration
2. Click the **Publish** button to activate your workflow
3. Your workflow is now live and will start processing automatically!

---

## Key Features

### Dynamic Custom Fields
When creating or updating persons, Encharge integration automatically fetches and displays all available custom fields from your Encharge account. This makes it easy to map data without manually typing field names.

### Tag-Based Automation
Use tags to segment your audience and trigger specific workflows when users are tagged or untagged. Perfect for behavioral targeting and customer journey automation.

### Flexible User Identification
Identify users by email address or custom user ID, giving you flexibility in how you manage and track your contacts.

### Real-Time Webhook Triggers
All triggers use webhooks for instant notification when events occur in Encharge, ensuring your workflows respond in real-time.

---

## Workflow Examples & Use Cases

Here are some powerful workflow automations you can create with the Encharge integration:

### 1. **Sync New WooCommerce Customers to Encharge**
**Trigger:** WooCommerce - New Order  
**Action:** Encharge - Create a Person  
**Use Case:** Automatically add new customers to Encharge when they complete a purchase, then add a "customer" tag for segmentation. Perfect for creating post-purchase email sequences.

### 2. **Tag Users Based on Course Completion**
**Trigger:** LearnDash - Course Completed  
**Action:** Encharge - Add Tags to a User  
**Use Case:** When a student completes a course, tag them in Encharge to trigger a certificate email or upsell sequence for advanced courses.

### 3. **Update Contact Info Across Platforms**
**Trigger:** Encharge - User Updated  
**Action:** Google Sheets - Add Row / Slack - Send Message  
**Use Case:** When contact information is updated in Encharge, log the change to a Google Sheet and notify your sales team via Slack.

### 4. **Re-engagement Campaign for Inactive Users**
**Trigger:** Encharge - User Tagged (tag: "inactive")  
**Action:** WordPress - Create Post / Email - Send Notification  
**Use Case:** When users are tagged as inactive in Encharge, send them a personalized re-engagement email with special offers or create targeted content.

### 5. **Lead Scoring Automation**
**Trigger:** Encharge - New User  
**Actions:** 
- Encharge - Get a Person (to fetch activity data)
- Encharge - Add Tags to a User (based on lead score)
- CRM - Create/Update Lead  
**Use Case:** Automatically score new leads based on their engagement and add appropriate tags, then sync high-value leads to your CRM.

### 6. **Event Registration to Email Sequence**
**Trigger:** WPForms/Gravity Forms - Form Submission  
**Actions:**
- Encharge - Create a Person
- Encharge - Add Tags to a User (tag: "event-attendee")  
**Use Case:** When someone registers for a webinar or event through a form, add them to Encharge and tag them to trigger a pre-event email sequence.

### 7. **Subscription Status Sync**
**Trigger:** WooCommerce Subscriptions - Subscription Status Changed  
**Actions:**
- Encharge - Update a Person
- Encharge - Add/Remove Tags based on subscription status  
**Use Case:** Keep Encharge in sync with subscription statuses - tag active subscribers, remove tags from cancelled subscribers, and trigger appropriate email flows.

### 8. **User Unsubscribe Logging**
**Trigger:** Encharge - User Unsubscribed  
**Actions:**
- Google Sheets - Add Row
- Slack - Send Message to #marketing channel  
**Use Case:** Track all unsubscribes in a spreadsheet for analysis and alert your team when someone opts out.

### 9. **Multi-Step Lead Nurturing**
**Trigger:** Encharge - User Tagged (tag: "free-trial")  
**Actions:**
- Delay - Wait 3 days
- Encharge - Get a Person (check engagement)
- Conditional Logic - If active
- Encharge - Add Tags (tag: "engaged-trial")
- Email - Send upgrade offer  
**Use Case:** Create sophisticated nurture sequences based on user behavior and engagement levels.

### 10. **Custom Field Data Sync**
**Trigger:** Encharge - User Updated  
**Action:** Encharge - Make an API Call  
**Use Case:** When specific custom fields are updated, trigger additional API calls to sync data with other systems or update calculated fields.

### 11. **Abandoned Cart Recovery**
**Trigger:** WooCommerce - Cart Abandoned  
**Actions:**
- Encharge - Create a Person (if new)
- Encharge - Add Tags (tag: "abandoned-cart")  
**Use Case:** Add users who abandon carts to Encharge with a specific tag to trigger an automated cart recovery email sequence.

### 12. **VIP Customer Identification**
**Trigger:** WooCommerce - Order Total Exceeds Amount  
**Actions:**
- Encharge - Get a Person
- Encharge - Update a Person (update MRR, Lead Score)
- Encharge - Add Tags (tag: "vip-customer")  
**Use Case:** Automatically identify and tag high-value customers, update their lead score, and trigger VIP customer workflows.

---

## Troubleshooting

### Connection Issues
- **Problem:** Cannot connect to Encharge
- **Solution:** Verify your API key is correct at [https://app.encharge.io/account/info](https://app.encharge.io/account/info)

### Custom Fields Not Showing
- **Problem:** Custom fields not appearing in configuration tab
- **Solution:** Click the refresh button next to the custom fields section, or check that you've selected a valid connect account

### Trigger Not Firing
- **Problem:** Webhook trigger not activating
- **Solution:** 
  - Ensure the workflow is published
  - Check that the webhook is registered in Encharge settings
  - For tag-based triggers, verify the tag name matches exactly (case-sensitive)

### Person Not Found
- **Problem:** "Person not found" error
- **Solution:** Verify the email or userId exists in Encharge, or use "Create a Person" action first

---

## Support & Documentation

- **Encharge API Documentation:** [https://developers.encharge.io/](https://developers.encharge.io/)
- **FlowMattic Support:** Contact support by creating a new ticket from this site
- **FlowMattic Integration:** [https://flowmattic.com/integration/encharge/](https://flowmattic.com/integration/encharge/)

---

# Error: The PDF engine could not be loaded

Source: https://support.flowmattic.com/kb/article/197/error-the-pdf-engine-could-not-be-loaded

## Symptom

A PDF export fails with the message **"The PDF engine could not be loaded. Open the PDF Templates page once to install it, then try again."**, or a workflow's PDF Builder step returns an error instead of a file.

## Cause

To keep the plugin download small, the bundled mPDF rendering engine is not shipped inside the plugin. Instead it is downloaded once, on demand, from the FlowMattic CDN into `wp-content/uploads` the first time you open the PDF Builder. If that one-time download cannot complete, the engine is not present and PDF generation cannot run.

The download can fail when:

- The server has no outbound HTTPS access to `cdn.flowmattic.com` (a firewall, proxy, or locked-down host blocks the request).
- The `wp-content/uploads` directory is not writable by WordPress.
- The PDF Builder page has never been opened, so the one-time install has not been triggered yet.

## Fix

**1. Open the PDF Templates page once.**
In your WordPress admin, go to **FlowMattic → PDF Templates**. Visiting the page triggers the one-time engine install in the background. Give it a few seconds, then try your export again.

![The FlowMattic → PDF Templates listing page — visiting it triggers the one-time engine install](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-pdf-template-builder-pdf-list-page.png)

**2. Confirm the server can reach the CDN.**
Ask your host to confirm the server can make outbound HTTPS requests to `cdn.flowmattic.com`. On locked-down hosts this is the most common blocker. Allow-listing that host lets the engine download complete.

**3. Confirm the uploads folder is writable.**
The engine installs into `wp-content/uploads`. If that folder is not writable by the web server, the install cannot save the files. Restore normal WordPress upload permissions and reload the PDF Templates page.

**4. Use Cloudflare Browser Rendering instead.**
Cloudflare Browser Rendering does not use the bundled engine at all — it renders through Chrome on Cloudflare's edge. If you configure it under **FlowMattic → Settings → Cloudflare**, PDFs render without needing the local engine. This is also the pixel-accurate option. See *Set up Cloudflare Browser Rendering*.

## Note

Only PDF export rendering depends on this engine. Designing and saving templates in the builder, and every other part of FlowMattic, work normally whether or not the engine has been installed.

---

# Filter and path rules in FlowMattic

Source: https://support.flowmattic.com/kb/article/31/filter-and-path-rules-in-flowmattic

Use filters to guarantee that operations are only carried out on the objects you choose. With filters, you can specify a certain criterion to reach the desired level of granularity.

For instance, you can configure a filter to only record emails with a particular topic line or just clients who make a particular product transaction. Therefore, the next action in your FlowMattic workflow is initiated when the data from your previous action steps including triggers satisfies the criteria of a filter. No more actions are taken if a filter stops an item.

A task that is not passed by a filter is not executed while the workflow execution. Only tasks that are passed by filter are executed..

**Filter rule types**

Different logical rules can be applied using filters. Only the type of data that is indicated in brackets can be used with conditions. Text, numeric, date/time, boolean, and generic are the five different categories of filter rules.

**Examples**

You can see which fields would satisfy a particular rule in this table. Each example's Rule is the filter rule that we've specified, the Value is what we're comparing it to, and the Examples are inputs from action or trigger responses that the filter is comparing.

<table><tbody><tr><td><strong>Rule</strong></td><td><strong>Value</strong></td><td><strong>Examples that would pass</strong></td><td><strong>Examples that wouldn’t pass</strong></td></tr><tr><td>(Text) Contains</td><td>Apples and bananas</td><td>Apples Apple Apples and bananas</td><td>Strawberries</td></tr><tr><td>(Text) Does not contain</td><td>Apples and bananas</td><td>Strawberries</td><td>Apple</td></tr><tr><td>(Text) Exactly matches</td><td>Apples</td><td>Apples</td><td>Apple (not plural) apple (not uppercase)</td></tr><tr><td>(Text) Does not exactly match</td><td>Apples</td><td>Apple Banana And more</td><td>Apples</td></tr><tr><td>(Text) Is in</td><td>Apples, bananas</td><td>Apples Bananas</td><td>Apple Banana Strawberries</td></tr><tr><td>(Text) Is not in</td><td>Apples, bananas</td><td>Strawberries Apple</td><td>Apples Bananas</td></tr><tr><td>(Text) Starts with</td><td>App</td><td>Apples Applesauce</td><td>Apricots Bananas</td></tr><tr><td>(Text) Does not start with</td><td>App</td><td>Apricots Bananas</td><td>Apples Applesauce</td></tr><tr><td>(Text) Ends with</td><td>s</td><td>Bananas Apple and bananas</td><td>Apple</td></tr><tr><td>(Text) Does not end with</td><td>s</td><td>Apple Banana</td><td>Apples Bananas</td></tr><tr><td>(Number) Greater than</td><td>10</td><td>11100</td><td>9-1</td></tr><tr><td>(Number) Less than</td><td>10</td><td>9-1</td><td>100</td></tr><tr><td>(Date/time) After</td><td>12/31/2018 1:00</td><td>01/01/2019 12/31/2018 01:01</td><td>12/31/2017</td></tr><tr><td>(Date/time) Before</td><td>12/31/2018 1:00</td><td>12/31/2017</td><td>01/01/2019</td></tr><tr><td>(Date/time) Equals</td><td>12/31/2018 1:00</td><td>12/31/2018 1:00</td><td>12/31/2019 12/31/2018 00:00</td></tr><tr><td>Exists</td><td>n/a</td><td>Apple 10 01/01/2019</td><td></td></tr><tr><td>Does not exist</td><td>n/a</td><td></td><td>Apple 10 01/01/2019</td></tr></tbody></table>

**Text filters**

Text filters only work with text data, so they won’t work with numbers or dates.

1. Contains: Verifies if a field contains a specific value. It is not case-sensitive.

3. Does not contain: Verifies if a field does not contain a specific value. It is not case-sensitive.

5. Exactly matches: Checks if a field matches a value precisely, letter-for-letter. It is case-sensitive.

7. Does not exactly match: Checks if a field does not match a value precisely, letter-for-letter. It is case-sensitive.

9. Is in: Determines if a field exists in a list of values. It is not case-sensitive.

11. Is not in: Determines if a field does not exist in a list of values. It is not case-sensitive.

13. Starts with: Validates if a field starts with a particular value. It is not case-sensitive.

15. Does not start with: Validates if a field does not start with a particular value. It is not case-sensitive.

17. Ends with: Verifies if a field ends with a specific value. It is not case-sensitive.

19. Does not end with: Verifies if a field does not end with a specific value. It is not case-sensitive.

**Number filters**

Number filters only work with numeric values, like 1 or 100. They do not work with written forms of numbers (one, two, one hundred) or dates.

11. Greater than: Checks if a numerical field is greater than a specific value.

13. Less than: Checks if a numerical field is less than a specific value.

15. Equal to: Checks if a field is equal to a specific value. This is case-sensitive for text fields and exact for numerical fields.

17. After (date/time): Checks if a date or time field occurs after a specific date or time.

19. Before: Checks if a date or time field occurs before a specific date or time.

21. Equal: Checks if a field is equal to a specific value. This is case-sensitive for text fields and exact for numerical fields.

**Boolean filters**

17. Is true (Boolean): Checks if a Boolean field is set to true.

19. Is false: Checks if a Boolean field is set to false.

**Generic filters**

19. Exists: Checks if a field has a value or is not empty.

21. Does not exist: Checks if a field does not have a value or is empty.

**If you have a series of items like this:**

Whether FlowMattic continues to pass the filter depends on whether you use positive or negative filter conditions.

Examples of positive filter conditions are "contains" and "starts with".

Examples of negative filter conditions are "does not contain" and "does not start with".

**If all filter conditions are positive**

If all conditions are positive, at least one line item must pass all filter conditions for FlowMattic to continue.

In the example below, one item satisfies both positive conditions, even though the other does not, so FlowMattic continues.&nbsp;

**If the filter condition is both positive and negative, or all negative**

If negative conditions are included, all line items must pass all filter conditions for FlowMattic to continue.

In the example below, one or more line items did not meet the filter criteria, so FlowMattic will not continue.

---

# Filters

Source: https://support.flowmattic.com/kb/article/32/filters

### FlowMattic Filter Module Documentation

The **Filter module** in FlowMattic allows you to control the flow of your workflow based on specific conditions. This module provides flexibility to decide whether or not the workflow should continue to the next step, depending on whether the data meets the specified criteria. It helps ensure that only relevant data moves through the workflow, making your automation more efficient and accurate.

With the **Filter module**, you can create powerful conditional logic in your workflows, deciding when to proceed and when to stop based on real-time data evaluation.

* * *

### Step-by-Step Guide to Using the FlowMattic Filter Module

#### 1\. Create a New Workflow

- Log in to your WordPress dashboard where FlowMattic is installed.

- Navigate to your **FlowMattic Dashboard**.

- Click on **"New Workflow"** to start creating a new workflow.

#### 2\. Add the Filter Module

- Once inside the workflow editor, click **"Add New Action"** to add a new step to your workflow.

- Select **"Filter by FlowMattic"** from the list of available applications.

#### 3\. Choose the Action Event

FlowMattic's Filter module provides two primary action events to control how the workflow behaves based on your conditions:

##### 3.1. Continue If Condition Is Met

- Choose this option if you want the workflow to proceed to the next step **only if** the conditions set in the filter are met. If the conditions are not met, the workflow will stop execution at this point.

##### 3.2. Exit If Condition Is Met

- Select this option if you want the workflow to **stop** when the conditions are met. If the conditions are not met, the workflow will proceed to the next step as usual.

These two options provide flexibility to control how and when your workflows should continue or stop, based on real-time data.

#### 4\. Set Up Filter Conditions

In the **Filter Setup & Testing** section, you will define the conditions that control the workflow's execution. Here’s how to set up the conditions:

##### 4.1. Choose the Field (First Dropdown)

- From the first dropdown, select the **field** or **variable** that you want the filter to check. This could be data retrieved from previous steps or external inputs, such as values from an API response or form submissions.

##### 4.2. Set the Condition (Second Dropdown)

- In the second dropdown, choose the **comparison operator** that defines how the selected field should be evaluated. Here are a few available conditions-

- **Equals**

- **Contains**

- **Does Not Contain**

- **Greater Than**

- **Less Than**

- **Is Empty** / **Is Not Empty** These operators allow for a range of conditional checks to suit your workflow requirements.

For detailed overview of the conditions, read: [Filter and path rules in FlowMattic](https://support.flowmattic.com/kb/article/31/filter-and-path-rules-in-flowmattic/ "Filter and path rules in FlowMattic")

##### 4.3. Define the Value (Third Dropdown)

- In the third input field, specify the **value** that the selected field will be compared against. For example, if you're checking if an email field contains the domain "@gmail.com", you would select "contains" in the second dropdown and input "@gmail.com" in this field.

#### 5\. Add Multiple Conditions (Optional)

If your filter needs to evaluate multiple conditions, you can add more criteria using the **AND** or **OR** logic:

- **AND**: All conditions must be true for the workflow to proceed.

- **OR**: At least one condition must be true for the workflow to proceed.

This allows you to create complex conditional logic to manage various workflow scenarios.

#### 6\. Save and Test the Filter

Once you have set up the filter conditions, follow these steps:

- **Save the Filter**: Click on the **“Save”** button to save your changes.

- **Test the Filter**: To ensure that the filter works as expected, click on the **“Test Action”** button. This will test the filter with sample data to verify that the conditions are being correctly applied. The test results will show whether the workflow will proceed or stop based on the current filter settings.

#### 7\. Save the Workflow

Once you’ve tested and confirmed that the filter is working correctly:

- Click on the **"Save Workflow"** button to finalize and save your workflow.

* * *

### Use Cases for the Filter Module

Here are a few examples of how the **Filter module** can be used in your workflows:

- **Lead Qualification**: Use the filter to continue the workflow only if a lead’s details (e.g., budget, location, or business size) meet certain criteria.

- **Email Campaigns**: Stop the workflow if the recipient’s email domain is not on your preferred list (e.g., if you only want to send emails to corporate domains).

- **Form Submissions**: Proceed with the workflow only if a user’s form submission contains all the required fields, and stop if any are missing or incomplete.

* * *

### Conclusion

The **Filter module** in FlowMattic is a versatile and essential tool for managing workflow conditions and improving the efficiency of your automation. By setting up filters, you can control when and how a workflow should proceed, ensuring that only relevant and appropriate data is processed.

With options like **Continue If Condition Is Met** and **Exit If Condition Is Met**, as well as the ability to create complex conditions using AND/OR logic, the Filter module empowers users to build highly dynamic workflows that respond to the needs of their business.

By following the steps outlined in this guide, you can effectively set up, test, and implement filters in FlowMattic, helping you automate smarter and more efficiently.

---

# FlowMattic AI Assistants: Getting Started

Source: https://support.flowmattic.com/kb/article/227/flowmattic-ai-assistants-getting-started

FlowMattic **AI Assistants** are context-aware AI chatbots you build in FlowMattic and embed on your website — and their conversations can trigger your workflows, so a reply, a captured lead, or a booked meeting can kick off an automation. Each assistant runs on **your own OpenAI API key**, connected through FlowMattic Connects, so you stay in control of the model and the cost.

This guide walks you through creating your first assistant and configuring the essentials.

---

## The AI Assistants dashboard

Open **FlowMattic → AI Assistants**. The dashboard shows every assistant you've built, with its connection, model, and conversation count at a glance.

![The AI Assistants dashboard](https://assets.infidesk.support/products/flowmattic/kb-images/ai-assistants/assistants-list.png)

Click **Create New Assistant** to start a new one, or open an existing assistant to edit it.

---

## The assistant editor

The editor has two panes: your **configuration** on the left (organised into **Setup**, **Content**, **Actions**, **Theme**, and **Conversations** tabs) and a **live Preview** on the right that updates as you make changes. **Help**, **Embed**, and **Share** sit in the top-right.

![The Setup tab of the assistant editor](https://assets.infidesk.support/products/flowmattic/kb-images/ai-assistants/setup-tab.png)

Everything below lives on the **Setup** tab.

### Identity

- **Chatbot Name** — shown in the chat header and used to identify the assistant.
- **Description** — a short note about what this assistant is for (up to 512 characters).

### AI Configuration

- **Connect** — the FlowMattic Connect linked to your OpenAI account. Manage these under **Connects**.
- **AI Model** — the model this assistant uses. Faster/cheaper models suit high-volume support; larger models give the best answers — pick per your needs.
- **Vector Store ID** — powers file search. Paste an existing vector store ID or let FlowMattic create one; this is where uploaded knowledge is retrieved from (see the *Content Sources* guide).

### Behavior & Responses

- **Instructions** — the system prompt: tell the assistant who it is, what it should and shouldn't do, and the tone to use.
- **Welcome Message** — the first thing visitors see when the chat opens.
- **Input text** — the placeholder in the message box (e.g. "Ask me anything here").

---

## Preview and save

Use the **Preview** pane to chat with your assistant as you configure it — try a few questions to check the tone and accuracy. When it behaves the way you want, click **Save Changes**.

---

## Next steps

Your assistant works out of the box, but it gets much more useful once you:

- **Give it knowledge** — upload files, crawl your site, or sync a FlowMattic Table so it answers from *your* content.
- **Wire up actions** — trigger a workflow on each reply, collect leads, or let visitors book a meeting.
- **Style and embed it** — match your brand and drop it onto your site.

---

**Related guides:** [Content Sources](https://support.flowmattic.com/portal/flowmattic/kb/article/228/flowmattic-ai-assistant-content-sources) · [Actions, Leads & Meetings](https://support.flowmattic.com/portal/flowmattic/kb/article/229/flowmattic-ai-assistant-actions) · [Style & Embed](https://support.flowmattic.com/portal/flowmattic/kb/article/230/flowmattic-ai-assistant-embed)

---

# FlowMattic Browser: Screenshots, PDFs, Web Scraping and an AI Browse Tool

Source: https://support.flowmattic.com/kb/article/163/flowmattic-browser-screenshots-pdfs-web-scraping-and-an-ai-browse-tool

**FlowMattic Browser** is a built-in (core) integration that opens any web page in a real, full-featured Chrome browser running in Cloudflare's cloud, then lets your workflows capture screenshots, generate PDFs, scrape data, extract clean text, pull links, archive pages, build social images, and search Google Maps. It also adds a **browse_url** tool to the FlowMattic **AI Agent**, so an AI agent can open and read web pages on its own.

## What "Cloudflare Browser Rendering" actually is

Most simple web requests just download a page's raw HTML. That breaks on modern sites built with React, Vue, or other JavaScript frameworks, because the real content is only assembled after the browser runs the page's scripts.

**Cloudflare Browser Rendering** solves this by running an actual headless Chrome browser (real Chrome, with no visible window) in Cloudflare's cloud. The browser loads the page, runs its JavaScript, waits for the network to settle, and only then does FlowMattic capture the result. That is why this integration can screenshot a single-page app, render a JavaScript dashboard to PDF, or scrape a price that only appears after the page finishes loading — things a plain HTTP fetch cannot do.

Because the browser runs on Cloudflare's servers (not your WordPress host), it needs **your own Cloudflare account credentials**. These same credentials also power FlowMattic's **PDF Template Builder** exports and the **AI Agent's browse_url tool** — one set of credentials, three features.

## How it works end to end

1. You add an action from the **FlowMattic Browser** app to a workflow step (or your AI Agent calls the **browse_url** tool).
2. FlowMattic sends the URL and your chosen options to Cloudflare's Browser Rendering API using your Account ID and API Token.
3. Cloudflare opens the page in real headless Chrome, runs its JavaScript, and returns the result — an image, a PDF, rendered HTML, clean Markdown, a list of links, or scraped values.
4. For actions that produce a file (screenshot, PDF, social image, archive), FlowMattic saves it where you chose (Media Library or a raw folder) and gives you a **public URL** plus an **attachment ID** you can pass into later steps like Email, Slack, Google Drive, or S3/R2.

If your credentials are missing, every Browser action and the AI Agent's browse tool return a clear error telling you to configure them first.

## Required setup: Cloudflare Account ID + API Token

Before any Browser action will run, you must add two values in FlowMattic's settings.

### Where to enter the credentials

Go to **FlowMattic → Settings**, then open the **Cloudflare** tab in the left sidebar. You'll find the **Cloudflare Browser Rendering** section with two fields:

- **Cloudflare Account ID** — found on the right-hand sidebar of your Cloudflare dashboard (on any page under your account).
- **Cloudflare API Token** — a token you create in Cloudflare. It must have the **Account → Browser Rendering → Edit** permission.

The settings screen links straight to Cloudflare's **Create API Token** page and to Cloudflare's Browser Rendering docs to help you generate the right token.

![The Cloudflare tab in FlowMattic Settings showing the "Cloudflare Browser Rendering" card with the Account ID and API Token fields](https://assets.infidesk.support/kb/inline/2026/07/bIJAazvN20SJhDO2O0PHFqX2aXmzVOOwO2XAtMCw.png)

Once both fields are filled and saved, the section shows a green **"Cloudflare Browser Rendering is configured"** confirmation. Until then it shows a warning that exports fall back to the bundled mPDF renderer (for PDF templates) and that Browser / AI Agent browse actions will return an error.

![The green "Cloudflare Browser Rendering is configured" confirmation note after saving valid credentials](https://assets.infidesk.support/kb/inline/2026/07/kBBBkrxhrDHtZzMl1DYmi9hHol6GFVZMfbWBClZ0.png)

### The credentials banner inside actions

Every Browser action shows a small orange reminder banner at the top with an **"Open settings →"** link, so if you haven't set up credentials yet you can jump straight to the right place.

## Settings shared by many actions

A few options appear across multiple actions. Here's what they do once, so you don't have to relearn them per action.

### URL

Almost every action starts with a **URL** field (marked **Required**). This is the absolute web address to open in headless Chrome, for example `https://example.com/page`. Like other FlowMattic fields, it supports captured data from earlier steps, so you can browse a URL produced dynamically by your workflow.

### Settle animations before capture?

Available on **Take Screenshot of URL** and **Generate PDF from URL**, this dropdown controls whether FlowMattic prepares the page before capturing it:

- **Yes** — scrolls the whole page, waits for fonts and images to load, and disables CSS animations so scroll-reveal effects and lazy-loaded images all appear. This adds roughly 3–6 seconds.
- **No** — captures immediately.

Turn this on for marketing pages with fade-in/scroll animations or lazy-loaded images; leave it off for speed on simple pages.

### Save to (file destination)

Actions that produce a file (**Take Screenshot**, **Generate PDF**, **Generate Social Image (OG)**, **Archive Page**) include a **Save to** dropdown with three choices:

- **Media Library (default uploads / YYYY / MM folder)** — saves the file as a normal WordPress attachment in the standard dated uploads folder. You get an attachment you can reuse in other FlowMattic actions.
- **Media Library — custom folder** — saves it as an attachment but inside a folder you specify. This reveals a **Custom Folder Path** field (for example `flowmattic/screenshots` or `clients/{client_id}/invoices`). The path is relative to `wp-content/uploads/`, is created automatically if missing, and gets an `index.php` guard to block directory listing.
- **Raw file (uploads/flowmattic-browser/, no media library entry)** — drops the file straight onto disk with no WordPress attachment record. This is the leanest option for high-volume workflows where you don't want to clutter the Media Library.

![The "Save to" dropdown expanded, showing Media Library, Media Library custom folder, and Raw file options, with the Custom Folder Path field visible](https://assets.infidesk.support/kb/inline/2026/07/g0EdAZLgGQpwfWPF5ArgjrjgoqK0QbPijS5KKzuq.png)

## The 9 actions

### 1. Take Screenshot of URL

Captures a PNG or JPEG image of any web page. Key fields:

- **Image Format** — **PNG** or **JPEG**.
- **Full Page?** — **No** captures only the visible viewport area; **Yes** captures the entire scrollable page top to bottom.
- **Viewport Width** and **Viewport Height** — the browser window size in pixels (defaults 1440 × 900; allowed range 320–4000).
- **Settle animations before capture?** and **Save to** (see shared settings above).

It returns the saved file's **url** and **path**, the **attachment_id**, the **file_size**, the original **source** URL, and even a **base64** copy of the image so you can pass it into actions that expect inline image data. Chain it into Slack, Google Drive, S3/R2, or Email.

### 2. Generate PDF from URL

Renders any web page to a PDF file. Key fields:

- **Output Filename** — the file name to save (a `.pdf` extension is added automatically if you omit it). Defaults to a timestamped name.
- **Page Size** — **Letter**, **A4**, **Legal**, **A3**, or **A5**.
- **Orientation** — **Portrait** or **Landscape**.
- **Settle animations before capture?** and **Save to** (see shared settings).

PDFs are rendered with backgrounds printed and a half-inch margin on all sides. The action returns the file **url**, **path**, **attachment_id**, **file_size**, and a **base64** copy. Chain it into Email (as an attachment), R2/S3 (upload), or the Archive step.

### 3. Scrape Content by Selector

Extracts specific text values from a page using CSS selectors — ideal for pricing intelligence, job boards, or real-estate feeds flowing into Google Sheets. Key field:

- **Selectors** (**Required**) — one `name: css_selector` pair per line (or a JSON object). For example:
  - `title: h1`
  - `price: .product-price`
  - `in_stock: [data-stock]`

Each **name** you choose becomes a key in the output. The action returns a `data` object mapping your names to the extracted text (for example `data.price`), plus the original `source` URL and the `raw` matches for advanced use.

![The Scrape Content by Selector action with the Selectors textarea filled with several name: selector pairs](https://assets.infidesk.support/kb/inline/2026/07/btevZC3nRfIqkMFDmwo3pYk2dNPdJVuTQHo19mLG.png)

### 4. Page to Markdown

Fetches a clean, boilerplate-free **Markdown** version of a page — navigation, ads, and clutter stripped out, leaving just the readable content. This is the ideal format to feed an **AI Assistant** or **Chatbot** step for summarizing, Q&A, or RAG ingestion. The only field is the **URL**. It returns the `markdown` text, the `source` URL, and the content `length`.

### 5. Get Page Links

Returns every outgoing link found on the page. Key field:

- **Restrict to Same Origin?** — **No** includes all outbound links; **Yes** keeps only links pointing to the same hostname as the page you browsed.

It returns a `links` array and a `count`. Pair it with the **Iterator** action to build a simple crawler that walks a site.

### 6. Get Rendered HTML

Returns the page's fully rendered HTML **after** its JavaScript has run. This is the action to use for React/Vue single-page apps where a plain HTTP fetch would return little or nothing. The only field is the **URL**. It returns the `html` string, the `source` URL, and the content `length`.

### 7. Archive Page (HTML + PNG)

Captures both the rendered HTML **and** a full-page screenshot in one step — perfect for CRM evidence and audit trails. Key fields:

- **Label (optional)** — a short label used in the saved file names (for example `client-proposal`).
- **Save to** (see shared settings).

It always uses a full-page screenshot with animations settled, and returns an **image_url** plus an **html_url** (each with its own attachment ID and size), a **timestamp**, and the **source** URL — everything you need to attach to a record or log.

### 8. Generate Social Image (OG)

Turns custom HTML — or a built-in card template — into a share-ready PNG at your exact dimensions, great for dynamic Open Graph / social cards. Key fields:

- **Custom HTML (optional)** — paste your own HTML to render. If you provide only an HTML fragment, FlowMattic wraps it in a complete, correctly sized document for you. Leave it blank to use the built-in card template.
- **Title** — the headline used by the built-in card template.
- **Subtitle / Kicker** — the small label above the title in the built-in template.
- **Background Color** and **Foreground Color** — hex colors for the built-in card (defaults `#0f172a` background, `#ffffff` text).
- **Width** and **Height** — output size in pixels (defaults 1200 × 630, the standard size for Open Graph, X/Twitter, and LinkedIn cards; range 200–2400).
- **Save to** (see shared settings).

It returns the image **url**, **path**, **attachment_id**, **file_size**, a **base64** copy, and the final **width**/**height**.

![The Generate Social Image (OG) action showing the Title, Subtitle, Background/Foreground color, and Width/Height fields](https://assets.infidesk.support/kb/inline/2026/07/QUCMg7vbP3T95oK0u8umw46nVfYKaiume0INEp6v.png)

### 9. Search Google Maps

Pulls business listings from Google Maps for a search term, using headless Chrome to load and scroll the Maps results (it never calls Google's paid APIs). Key fields:

- **Search Term** (**Required**) — whatever you'd type into Google, for example `coffee shops in nyc`.
- **Page** — `1` returns the first 10 results; use the returned **next_page** value in an Iterator to walk further pages.
- **Country** — an ISO 2-letter code such as `us`, `uk`, `de`, `in` (defaults to `us`).
- **Language** — an ISO 2-letter code such as `en`, `es`, `de` (defaults to `en`).

It returns up to **10 listings per page**, each with `name`, `rating`, `review_count`, `category`, `address`, `phone`, `website`, and `maps_url`, plus `next_page` and `has_more` flags so you can chain into an iterator.

![The Search Google Maps action filled with a search term, page, country, and language](https://assets.infidesk.support/kb/inline/2026/07/UvLnpooEQNi0z2DiaWyIe2YGZ4RuTxPrJodc41Ar.png)
## The AI Agent "browse_url" tool

Beyond the workflow actions above, FlowMattic Browser registers a native **browse_url** tool with the FlowMattic **AI Agent**. When you give your agent this tool, the AI can decide on its own to open a web page and read it — the tool's description tells the model to use it "whenever the user asks about a web page or link, or when you need fresh/current information from the web."

This is what lets an AI agent answer questions about live web pages, look up current information, or reason over a link the user pasted — instead of being limited to what it already knew. The agent supplies two arguments:

- **url** (required) — the absolute URL to open.
- **mode** — what to bring back:
  - **markdown** (default) — clean, readable content, best for the AI to reason over.
  - **content** — the full rendered HTML.
  - **links** — every link on the page.
  - **screenshot** — a full-page PNG.

Under the hood, this is the same universal browse engine exposed as the **Browse URL (for AI Agent)** workflow action, which offers the identical **Mode** dropdown (Markdown, Content, Links, Screenshot). You can add that action to a workflow yourself whenever you want one single, mode-switchable browse step — or let the AI Agent call it automatically. Either way, it uses your Cloudflare credentials and returns the same kind of result.

![The Browse URL (for AI Agent) action showing the Mode dropdown with Markdown, Content, Links, and Screenshot options](https://assets.infidesk.support/kb/inline/2026/07/VoGVNYslPT75nUmq3pQlXE2ob9ohc2XPXle8DYAP.png)

---

# FlowMattic Data Transformer - Complete User Guide

Source: https://support.flowmattic.com/kb/article/99/flowmattic-data-transformer---complete-user-guide

The Data Transformer is a powerful core module in FlowMattic that allows you to modify, encode, decode, hash, and format data as it flows through your workflows. This module is essential for preparing data for different systems, securing sensitive information, and ensuring data compatibility across various platforms and integrations.

## Quick Start Guide

### Step 1: Add Data Transformer Action
When building your workflow, add the Data Transformer action after your trigger event:

1. Click **"Add Action"** in your workflow builder
2. Search for "Data Transformer" in the app selection
3. Select **Data Transformer** from the Core Apps section
![Image 2025-08-27 at 10.54.31 PM.jpeg](/storage/kb-images/89abb822c2-inline.png)
4. Choose your specific transformation action
![Image 2025-08-27 at 10.58.37 PM.jpeg](/storage/kb-images/a7e5f6c4d6-inline.png)

### Step 2: Configure Your Transformation
Each transformation type has specific configuration options. Simply:
- Enter or map your input data
- Configure any additional parameters (like secret keys for HMAC)
- Test your transformation to verify output
- Use the transformed data in subsequent workflow steps

---

## Available Data Transformation Actions

### 1. HTML Encode
**What it does**: Converts special characters in text to their HTML entity equivalents to prevent security issues and display problems.

**When to use**:
 - User-generated content from forms needs to be displayed safely on websites
 - Storing content in databases that will later be shown on web pages
 - Email templates with dynamic content that might contain HTML
 - Any time you need to prevent XSS (Cross-Site Scripting) attacks

**Real-World Example**: 
Your Gravity Forms contact form collects customer feedback that might contain HTML code. Before saving it to your WordPress database or displaying it on your website, you need to make it safe.

**Practical Workflow**:
```
Gravity Forms (Form Submission) → Data Transformer (HTML Encode) → WordPress (Create Post/Update Database)
```

**What happens**:
- **Input from form**: Great product! <script>alert('spam')</script> Highly recommend!
- **After HTML Encode**: Great product! &lt;script&gt;alert(&#039;spam&#039;)&lt;/script&gt; Highly recommend!
- **Result**: Safe to display on your website without executing malicious code

---

### 2. HTML Decode
**What it does**: Converts HTML entities back to readable characters for editing or processing.

**When to use**:
 - Converting stored HTML entities back to readable text for editing
 - Processing content from systems that automatically encode HTML
 - Preparing content for platforms that don't need HTML encoding
 - Making encoded text human-readable in notifications

**Real-World Example**:
You're running a customer support system where incoming tickets are stored in the database with HTML entities for safety. But when you push those tickets into Slack for team visibility, you don’t want them to look messy with `&amp;quot;, &amp;lt;, and &amp;gt;`.

**Practical Workflow**:
```
Fluent Support (New Ticket Created) → Data Transformer (HTML Decode) → Slack (Post Message to Channel)
```

**What happens**:
- **Input from WordPress**:`Customer says: &amp;quot;I can&amp;#039;t access my account &amp;lt;again&amp;gt;&amp;quot;`
- **After HTML Decode**: `Customer says: "I can't access my account <again>"`
- **Result**: Support team sees a clean, readable message in Slack without confusing HTML entities.

---

### 3. Base64 Encode
**What it does**: Converts plain text or binary data into Base64 encoded format for safe transmission through text-based systems.

**When to use**:
 - APIs require files to be sent as Base64 strings
 - Transmitting binary data through JSON APIs
 - Sending images or documents through webhooks
 - Converting files for storage in text-based databases
 - Preparing attachments for email APIs

**Real-World Example**:
A customer uploads a PDF invoice through your Contact Form 7. You need to send this document to your app for further processing, but the API requires Base64 encoded files.

**Practical Workflow**:
```
Contact Form 7 (File Upload) → Data Transformer (Base64 Encode) → your app (Send to Processing Service)
```

**What happens**:
- **Input**: PDF file from form upload
- **After Base64 Encode**: `JVBERi0xLjQKJeLjz9MKMSAwIG9iago8PAovVHlwZSAvQ2F0YWxvZwo...`
- **Result**: File data that can be transmitted through JSON APIs

---

### 4. Base64 Decode
**What it does**: Converts Base64 encoded data back to its original format.

**When to use**:
 - Processing files received from APIs as Base64 strings
 - Converting encoded images from mobile applications
 - Handling file attachments from email APIs
 - Processing encoded documents from external services
 - Converting API responses with embedded files

**Real-World Example**:
Your supplier sends product images via webhook as Base64 encoded data. You want to save these images directly to your WordPress media library for use in WooCommerce products.

**Practical Workflow**:
```
Webhook (Supplier Product Data) → Data Transformer (Base64 Decode) → WordPress (Upload to Media Library) → WooCommerce (Update Product Images)
```

**What happens**:
- **Input**: `iVBORw0KGgoAAAANSUhEUgAAAAEAAAABCAYAAAAfFcSJAAAADUlEQVR42mP8/5+hHgAHggJ/PchI7wAAAABJRU5ErkJggg==`
- **After Base64 Decode**: Actual image file data
- **Result**: Image files saved to your media library

**Best for**:
- Processing API responses with encoded files
- Converting encoded images from external systems
- Handling file data from mobile applications
- Processing encoded documents from services

---

### 5. SHA256 Hash
**What it does**: Creates a secure SHA256 hash of your input data for security and integrity verification.

**When to use**:
 - Secure password hashing (though bcrypt is preferred for passwords)
 - Creating tamper-proof data signatures
 - Generating unique, secure identifiers
 - Data integrity verification
 - Duplicate detection while maintaining privacy

**Real-World Example**:
You want to create tamper-proof order references when syncing WooCommerce orders with your inventory management system via webhook. This ensures order data hasn't been modified during transmission.

**Practical Workflow**:
```
WooCommerce (New Order) → Data Transformer (SHA256 Hash of Order Details) → API (Send to Inventory System with Hash)
```

**What happens**:
- **Input**: `order_12345_john_doe_299.99_2024-08-27`
- **After SHA256**: `a665a45920422f9d417e4867efdc4fb8a04a1f3fff1fa07e998e86f7f7a27ae3`
- **Result**: Unique, tamper-proof identifier for order verification

---

### 6. SHA1 Hash
**What it does**: Generates SHA1 hash for legacy system compatibility and basic integrity checks.

**When to use**:
 - Legacy payment processors require SHA1 hashes
 - Older systems that specifically need SHA1 format
 - Git-like versioning systems (though not for security)
 - Basic file integrity checking (non-security critical)

**Real-World Example**:
Your payment processor's older system requires SHA1 hashes for transaction verification. While not ideal for new security applications, it's necessary for this specific integration.

**Practical Workflow**:
```
WooCommerce (Payment Processing) → Data Transformer (SHA1 Hash Transaction Data) → Legacy Payment Gateway Webhook (Verify Transaction)
```

**What happens**:
- **Input**: `transaction_67890_customer_jane_amount_150.00`
- **After SHA1**: `7d865e959b2466918c9863afca942d0fb89d7c9ac0c99bafc3749504ded97730`
- **Result**: Hash format required by legacy payment system

**⚠️ Note**: Use SHA256 or higher for new security-critical applications.

---

### 7. SHA512 Hash
**What it does**: Provides maximum security hashing for enterprise and high-security applications.

**When to use**:
 - Enterprise security requirements
 - Banking and financial integrations
 - Government and healthcare systems
 - Maximum security compliance needs
 - High-value transaction verification

**Real-World Example**:
Your enterprise client requires the highest level of security for their Learning Management System integration. User authentication data must be hashed with SHA512 for compliance.

**Practical Workflow**:
```
LearnDash (User Enrollment) → Data Transformer (SHA512 Hash User Credentials) → your app (Secure Authentication Setup)
```

**What happens**:
- **Input**: `enterprise_user_jane_doe_department_hr_2024`
- **After SHA512**: `b109f3bbbc244eb82441917ed06d618b9008dd09b3befd1b5e07394c706a8bb980b1d7785e5976ec049b46df5f1326af5a2ea6d103fd07c95385ffab0cacbc86`
- **Result**: Maximum security hash for enterprise compliance

---

### 8. HMAC SHA256
**What it does**: Creates authenticated hash using a secret key for secure message verification and API authentication.

**When to use**:
 - Verifying webhook authenticity (Stripe, PayPal, etc.)
 - Two-way API authentication
 - Secure message verification between systems
 - Preventing man-in-the-middle attacks
 - Ensuring data hasn't been tampered with during transmission

**Real-World Example**:
You receive payment notifications from Stripe webhooks. To ensure these are legitimate Stripe notifications and not malicious fake requests, you verify them using HMAC SHA256 with your Stripe webhook secret.

**Practical Workflow**:
```
Stripe (Payment Notification) → Data Transformer (HMAC SHA256 Verification) → Conditional Logic (If Valid) → WooCommerce (Update Order Status)
```

**Configuration**:
- **Message**: Webhook payload data from Stripe
- **Secret Key**: Your Stripe webhook endpoint secret
- **Output**: Authentication hash to compare with Stripe's signature

**What happens**:
- **Input Message**: `payment_intent.succeeded`
- **Secret Key**: `whsec_your_stripe_secret_key_here`
- **After HMAC SHA256**: `4a1c6c10b8ab0b2a5f6d8e3c9d7f2e8a9b5c1d4e7f8a2b3c6d9e0f3a6b9c2d5e8`
- **Result**: Verified authentic webhook from Stripe

---

### 9. MD5 Hash
**What it does**: Generates basic checksums for duplicate detection and legacy compatibility.

**When to use**:
 - Quick duplicate file detection (non-security critical)
 - Cache key generation
 - Legacy system integration that requires MD5
 - Basic file integrity checking (for change detection only)
 - Simple content comparison

**Real-World Example**:
You want to prevent duplicate product images in your WooCommerce store to save storage space. MD5 can help identify identical files quickly.

**Practical Workflow**:
```
WooCommerce (Product Image Upload) → Data Transformer (MD5 Hash) → Conditional Logic (Check Against Existing Hashes) → WordPress (Store Only If Unique)
```

**What happens**:
- **Input**: Image file data or filename
- **After MD5**: `5d41402abc4b2a76b9719d911017c592`
- **Result**: Quick duplicate detection without storing identical images

**⚠️ Important**: MD5 is cryptographically weak. Never use for passwords or security-critical applications.

---

### 10. Strip Tags
**What it does**: Removes HTML and XML tags from text, leaving clean plain text content.

**When to use**:
 - Sending content to messaging platforms (WhatsApp, SMS, Slack)
 - Creating plain text versions of HTML content
 - Preparing content for social media platforms
 - Data export to text-only systems
 - Search engine optimization (extracting readable content)
 - Content migration between different systems

**Real-World Example**:
Your WooCommerce order confirmation emails contain HTML formatting, but you want to send clean, simple WhatsApp messages to customers with just the essential information.

**Practical Workflow**:
```
WooCommerce (Order Completed) → Data Transformer (Strip Tags from Order Details) → WhatsApp Cloud API (Send Clean Message)
```

**What happens**:
- **Input**: `<h2>Order Confirmed!</h2><p>Your order <strong>#12345</strong> for <em>$299.99</em> has been processed. <a href="track-link">Track here</a>.</p>`
- **After Strip Tags**: `Order Confirmed! Your order #12345 for $299.99 has been processed. Track here.`
- **Result**: Clean text perfect for messaging apps

---

## Industry-Specific Workflow Examples

### E-Commerce Security & Processing
**Secure Payment Processing**:
```
WooCommerce Order → Data Transformer (HMAC SHA256) → Payment Gateway → Verified Processing
```

**Safe Product Reviews**:
```
WooCommerce Review → Data Transformer (HTML Encode) → WordPress Display → Safe Customer Reviews
```

**Inventory Sync with Integrity**:
```
WooCommerce Stock Update → Data Transformer (SHA256 Hash) → Inventory API → Tamper-Proof Sync
```

### Content Management & Migration
**Blog Content Migration**:
```
WordPress Export → Data Transformer (HTML Decode) → WPForms Pre-fill → Content Editing
```

**Multi-Channel Content Distribution**:
```
WordPress Post → Data Transformer (Strip Tags) → Social Media APIs → Clean Text Posts
```

**Document Processing Pipeline**:
```
Contact Form 7 Upload → Data Transformer (Base64 Encode) → Document API → Processed Files
```

### Marketing Automation
**Clean Communication Flow**:
```
Email Campaign Content → Data Transformer (Strip Tags) → WhatsApp API → Clean Messages
```

**Lead Verification**:
```
Gravity Forms Lead → Data Transformer (SHA256 Hash Email) → CRM Webhook → Secure Lead Storage
```

**File Processing for Marketing**:
```
Media Upload → Data Transformer (Base64 Encode) → Image Processing API → Optimized Assets
```

### Customer Service & Support
**Secure Ticket Creation**:
```
Contact Form → Data Transformer (HTML Encode) → Support System → Safe Support Tickets
```

**Multi-Channel Notifications**:
```
Support Update → Data Transformer (Strip Tags) → SMS + WhatsApp → Clean Status Updates
```

**Document Handling**:
```
Customer Document Upload → Data Transformer (Base64 Encode) → Support API → Secure Processing
```

---

## Best Practices & Pro Tips

### Security Best Practices
- **Choose appropriate hashing**: SHA256+ for security, MD5 only for non-security duplicate detection
- **Protect HMAC secrets**: Store webhook secrets securely, never expose in logs
- **Validate before transforming**: Always verify input data format and content
- **Use HTTPS**: Ensure encrypted transmission of sensitive transformed data
- **Regular security audits**: Review hash algorithms periodically for compliance

### Performance Optimization
- **Transform efficiently**: Choose the least resource-intensive method that meets requirements
- **Cache transformed results**: Store frequently used transformations to avoid repeated processing
- **Batch processing**: Group similar transformations when possible
- **Monitor resource usage**: Track transformation performance in high-volume workflows

### Workflow Design Tips
- **Plan transformation sequence**: Map required transformations before building workflows
- **Document your logic**: Maintain clear records of why specific transformations are chosen
- **Test with real data**: Always test transformations with actual production data samples
- **Error handling**: Plan for transformation failures and invalid input scenarios
- **Version control**: Keep track of transformation configuration changes

### Testing Strategy
1. **Start with static data**: Test transformations with known, predictable input
2. **Use production samples**: Test with real data from your actual triggers
3. **Edge case testing**: Test with empty fields, special characters, maximum data sizes
4. **System compatibility**: Verify output works correctly with receiving systems
5. **Load testing**: Ensure transformations perform well under expected volume
6. **Security testing**: For hash functions, verify output meets security requirements

---

### Debugging Tips
1. **Use test data first**: Always test transformations with simple, known data
2. **Check character encoding**: Ensure UTF-8 compatibility across your workflow
3. **Verify input format**: Confirm input data matches expected format
4. **Compare with examples**: Use online tools to verify transformation results
5. **Monitor error logs**: Check FlowMattic logs for transformation errors
6. **Test incrementally**: Add transformations one at a time to isolate issues

---

## Quick Reference Table

| Need to... | Use This Action | Common Scenarios |
|------------|----------------|------------------|
| **Make user content safe for web display** | HTML Encode | Form submissions, comments, reviews |
| **Edit previously encoded content** | HTML Decode | Content editing, form pre-filling |
| **Send files through text-based APIs** | Base64 Encode | Document processing, image APIs |
| **Process files from API responses** | Base64 Decode | Saving API files, mobile app data |
| **Secure passwords or create unique IDs** | SHA256 Hash | User authentication, order verification |
| **Work with legacy systems** | SHA1 Hash | Older payment processors, legacy APIs |
| **Maximum security compliance** | SHA512 Hash | Enterprise, banking, government |
| **Verify webhooks or authenticate APIs** | HMAC SHA256 | Stripe/PayPal verification, API security |
| **Detect duplicate files (non-security)** | MD5 Hash | File deduplication, cache keys |
| **Send clean text messages** | Strip Tags | WhatsApp, SMS, plain text emails |

---

## Getting Advanced Support

The Data Transformer integrates seamlessly with all FlowMattic workflow steps, and transformed data can be mapped into subsequent actions just like any other workflow data.

**Pro Tip**: Always test your data transformations with real data samples before deploying workflows to production. This ensures compatibility and prevents unexpected issues.

Ready to transform your data workflows? Start building with FlowMattic Data Transformer today!

---

# FlowMattic GitHub Integration: Complete Setup & Configuration

Source: https://support.flowmattic.com/kb/article/225/flowmattic-github-integration-complete-setup-configuration

Trigger workflows from GitHub events and run GitHub actions as workflow steps. Uses a **bring-your-own OAuth App** — you create one GitHub OAuth App, paste its Client ID/Secret into FlowMattic, and authorize.

---

## Overview

| | |
|---|---|
| **Auth** | OAuth 2.0 (your own GitHub OAuth App) |
| **Capabilities** | Triggers (webhook-based) + Actions (REST API) |
| **Scopes requested** | `repo` · `workflow` · `admin:org` · `admin:repo_hook` · `gist` · `user` · `delete_repo` · `read:project` |

These scopes let FlowMattic read/write repos and issues, run and read Actions workflows, create repository webhooks, manage org membership, and create gists on your behalf.

---

## Step 1 — Create a GitHub OAuth App

1. Go to **GitHub → Settings → Developer settings → OAuth Apps → New OAuth App**.
2. Fill in:
   - **Application name** — e.g. `FlowMattic`.
   - **Homepage URL** — your site URL.
   - **Authorization callback URL** — must match **exactly**:
     ```
     https://your-site.com/wp-json/flowmattic/v1/auth/github
     ```
     Replace `your-site.com` with your domain. A mismatch here is the #1 cause of failed connections.
3. **Register application**, then copy the **Client ID**.
4. **Generate a new client secret** and copy it (shown only once).

![GitHub OAuth App registration form with callback URL filled in](https://assets.infidesk.support/kb/inline/2026/07/9aduykht95VqEjrE8IwMlNPqEYxleMmISAdK6ccB.png)
---

## Step 2 — Connect in FlowMattic

1. In FlowMattic open **Connects → Add → GitHub**.
2. Paste **Client ID** and **Client Secret**.
3. Click **Authorize** → approve on GitHub → you're redirected back and connected.

![FlowMattic GitHub connect dialog (Client ID / Secret fields)](https://assets.infidesk.support/kb/inline/2026/07/5yVIRfFGsWNiECVhWTQ77hhUpic2HRja5B0q8eCN.png)
The connected account now appears in every GitHub step's **Choose Connect Account** dropdown.

---

## Step 3 — Set Up a Trigger

FlowMattic registers the webhook on GitHub for you — no manual webhook entry needed.

1. Add a **GitHub** trigger step to a workflow.
2. Pick **Connect Account**, **Trigger Event**, and **Repository**.
3. Save/enable. FlowMattic creates (or reuses) a repo webhook pointing at the workflow.

**Requirements**

- Connected account needs **admin** rights on the repo (needed to create webhooks). A `404` means repo not found *or* no admin access.
- Site must be **publicly reachable** by GitHub — localhost won't receive deliveries.

**Test:** perform the real event on GitHub (open an issue, push, etc.); the trigger fires with the payload.

![GitHub trigger step — event + repository selected](https://assets.infidesk.support/kb/inline/2026/07/MxRuVwP2y5XTT8PoSX4lOLKkyPMV6bA45A2KhRfe.png)

---

## Actions & Triggers

Full event/action menus are listed inside the step's dropdowns in the workflow builder — no need to memorize them. Coverage spans issues, pull requests, repositories, files, commits, releases, labels, milestones, collaborators, Actions/CI, users, search, and security events.

**Multi-value fields** (Assignees, Labels): each value goes on its own row — click **Add More** for another, the box-X to remove, the refresh icon to reload options from the repo.

![Add Assignees action showing the repeater rows](https://assets.infidesk.support/kb/inline/2026/07/vgVEBSTpaF7CWiP0aHFqCHjT4qnEQYJ58hHGwV14.png)

---

## Troubleshooting

| Symptom | Fix |
|---|---|
| Authorization fails | Callback URL on the OAuth App must exactly equal `https://your-site.com/wp-json/flowmattic/v1/auth/github` (check http/https, slash, domain). |
| "Repository not found / lacks admin rights" | Account needs **admin** on the repo; for org repos, get the OAuth App approved for the org. |
| Trigger never fires | Site must be publicly reachable by GitHub — no localhost. |
| Empty Connect dropdown | Create a GitHub connect first (Step 2). |

---

# FlowMattic MCP Server: Developer Integration Guide - Add custom tools to MCP Server

Source: https://support.flowmattic.com/kb/article/89/flowmattic-mcp-server-developer-integration-guide-for-adding-custom-mcp-tools

## Overview

The FlowMattic MCP (Model Context Protocol) Server provides a powerful way for plugin developers, theme developers, and website developers to integrate their custom functions directly into MCP clients like Claude Desktop, without building an MCP server from scratch.

## What is FlowMattic MCP Server?

FlowMattic MCP Server acts as a bridge between your custom WordPress functions and MCP clients. Instead of developing a complete MCP server infrastructure, developers can simply hook their functions into FlowMattic's existing MCP server using a simple PHP API.

### Key Benefits

- **Zero MCP Server Development**: No need to build MCP server infrastructure
- **Automatic Tool Registration**: Your tools automatically appear in MCP clients
- **Admin Interface**: Tools are listed on the FlowMattic MCP server admin page
- **Execution History**: Track tool usage and performance
- **Simple Integration**: Just a few lines of PHP code

## How It Works

1. **Hook Your Functions**: Use FlowMattic's API to register your custom functions
2. **Automatic Discovery**: FlowMattic lists your tools to connected MCP clients
3. **Seamless Execution**: FlowMattic handles all MCP communication and function execution
4. **Response Handling**: Your function responses are automatically formatted for MCP clients

## Getting Started

### Prerequisites

- WordPress website
- FlowMattic plugin installed and activated
- Basic PHP knowledge

### Basic Integration

To add custom tools to FlowMattic MCP Server, use the `flowmattic_add_mcp_tools()` function:

```php
if ( function_exists('flowmattic_add_mcp_tools') ) {
    $tools = array();
    
    // Define your tools here
    
    flowmattic_add_mcp_tools( 'Your Plugin Name', $tools );
}
```

## Function Structure

### Tool Definition Array

Each tool requires the following structure:

```php
array(
    'name'          => 'Tool Display Name',
    'description'   => 'What this tool does',
    'function_name' => 'your_php_function_name',
    'parameters'    => array(
        'param1',
        'param2',
        // ... more parameters
    ),
    'request_type'  => 'array', // Optional: 'array' or omit for individual parameters
)
```

## Complete Examples

### Example 1: Simple User Lookup Tool

This example shows how to create a tool that retrieves WordPress user data by ID:

```php
/**
 * Function to get user by ID and return user data.
 *
 * @param int $user_id The WordPress user ID.
 * @return array The user data or an error message if the user does not exist.
 */
function my_plugin_get_user_by_id( $user_id ) {
    // Get user
    $user = get_userdata( $user_id );

    // Check if user exists - Example of error reporting to MCP tool
    if ( ! $user ) {
        return array(
            'error' => 'User not found.',
        );
    }

    // Get the user data
    $user_data = (array) $user->data;
    $user_fields = array();

    foreach ( $user_data as $key => $value ) {
        // Skip empty values
        if ( empty( $value ) ) {
            continue;
        }
        $user_fields[ $key ] = $value;
    }

    // Return user fields - can be string or array
    return $user_fields;
}

// Register the tool
if ( function_exists('flowmattic_add_mcp_tools') ) {
    $tools = array();
    
    $tools[] = array(
        'name'          => 'Get User by ID',
        'description'   => 'Retrieve a user profile details by their WordPress user ID.',
        'function_name' => 'my_plugin_get_user_by_id',
        'parameters'    => array(
            'user_id',
        ),
    );

    flowmattic_add_mcp_tools( 'User Management Plugin', $tools );
}
```

### Example 2: Array-Based Input Tool

This example demonstrates handling multiple parameters as an array:

```php
/**
 * Generate dummy data based on received input array.
 *
 * @param array $input_array The input associative array with some data.
 * @return array The dummy data response, enhanced or modified.
 */
function generate_dummy_data( $input_array ) {
    if ( ! is_array( $input_array ) ) {
        return array(
            'error' => 'Invalid input. Expected an array.',
        );
    }

    $dummy_data = array(
        'name'    => isset( $input_array['name'] ) ? $input_array['name'] : 'John Doe',
        'email'   => isset( $input_array['email'] ) ? $input_array['email'] : 'john.doe@example.com',
        'age'     => isset( $input_array['age'] ) ? $input_array['age'] : 30,
        'address' => isset( $input_array['address'] ) ? $input_array['address'] : '123 Main St, Anytown, USA',
        'phone'   => isset( $input_array['phone'] ) ? $input_array['phone'] : '123-456-7890',
        'notes'   => isset( $input_array['notes'] ) ? $input_array['notes'] : 'No additional notes provided.',
    );

    return $dummy_data;
}

// Register the tool with array request type
if ( function_exists('flowmattic_add_mcp_tools') ) {
    $tools = array();
    
    $tools[] = array(
        'name'          => 'Generate Dummy Data',
        'description'   => 'Generate dummy data based on the provided associative array.',
        'function_name' => 'generate_dummy_data',
        'parameters'    => array(
            'name',
            'email',
            'age',
            'address',
        ),
        'request_type'  => 'array', // Parameters passed as array to function
    );

    flowmattic_add_mcp_tools( 'Data Generator Plugin', $tools );
}
```

### Example 3: Database Query Tool

This example shows a more complex tool that queries the database:

```php
/**
 * Search posts by keyword in title or content.
 *
 * @param string $keyword The search keyword.
 * @param string $post_type The post type to search (optional).
 * @return array Search results or error message.
 */
function search_posts_by_keyword( $keyword, $post_type = 'post' ) {
    if ( empty( $keyword ) ) {
        return array(
            'error' => 'Keyword parameter is required.',
        );
    }

    $args = array(
        's'         => sanitize_text_field( $keyword ),
        'post_type' => sanitize_text_field( $post_type ),
        'posts_per_page' => 10,
        'post_status' => 'publish',
    );

    $query = new WP_Query( $args );
    
    if ( ! $query->have_posts() ) {
        return array(
            'message' => 'No posts found matching your search criteria.',
            'results' => array(),
        );
    }

    $results = array();
    while ( $query->have_posts() ) {
        $query->the_post();
        $results[] = array(
            'id'      => get_the_ID(),
            'title'   => get_the_title(),
            'excerpt' => get_the_excerpt(),
            'url'     => get_permalink(),
            'date'    => get_the_date(),
        );
    }
    wp_reset_postdata();

    return array(
        'message' => sprintf( 'Found %d posts matching "%s"', count( $results ), $keyword ),
        'results' => $results,
    );
}

// Register the search tool
if ( function_exists('flowmattic_add_mcp_tools') ) {
    $tools = array();
    
    $tools[] = array(
        'name'          => 'Search Posts',
        'description'   => 'Search for posts by keyword in title or content.',
        'function_name' => 'search_posts_by_keyword',
        'parameters'    => array(
            'keyword',
            'post_type',
        ),
    );

    flowmattic_add_mcp_tools( 'Content Search Plugin', $tools );
}
```

## Parameter Handling

### Individual Parameters (Default)

When `request_type` is not specified, FlowMattic passes parameters individually:

```php
// MCP Client sends: {"keyword": "wordpress", "post_type": "page"}
// Your function receives: search_posts_by_keyword( "wordpress", "page" )
```

### Array Parameters

When `request_type` is set to `"array"`, all parameters are passed as a single array:

```php
// MCP Client sends: {"name": "John", "email": "john@example.com"}
// Your function receives: generate_dummy_data( array( "name" => "John", "email" => "john@example.com" ) )
```

## Error Handling

Always include proper error handling in your functions:

```php
function my_custom_function( $param ) {
    // Validate input
    if ( empty( $param ) ) {
        return array(
            'error' => 'Parameter is required.',
        );
    }

    // Validate data types
    if ( ! is_numeric( $param ) ) {
        return array(
            'error' => 'Parameter must be a number.',
        );
    }

    // Your logic here...
    
    return $result;
}
```

## Response Formats

Your functions can return:

- **String**: Simple text response
- **Array**: Structured data (recommended)
- **Error Array**: `array( 'error' => 'Error message' )`

## Tool Execution History

FlowMattic automatically tracks:

- When each tool was executed
- What parameters were passed
- Function responses
- Execution time
- Success/error status

This history is available in the FlowMattic MCP server admin interface.

## Best Practices

### Security

- Always sanitize input parameters
- Use WordPress nonces for sensitive operations
- Validate user permissions when necessary

```php
function secure_user_function( $user_id ) {
    // Sanitize input
    $user_id = absint( $user_id );
    
    // Check permissions
    if ( ! current_user_can( 'manage_users' ) ) {
        return array( 'error' => 'Insufficient permissions.' );
    }
    
    // Your logic here...
}
```

### Performance

- Limit database queries
- Use WordPress caching when appropriate
- Set reasonable limits on returned data

```php
function get_recent_posts( $limit = 10 ) {
    // Limit the number of results
    $limit = min( absint( $limit ), 50 ); // Maximum 50 posts
    
    // Use WordPress query optimization
    $args = array(
        'posts_per_page' => $limit,
        'no_found_rows'  => true,
        'fields'         => 'ids', // Only get IDs if that's all you need
    );
    
    return get_posts( $args );
}
```

### Documentation

- Use clear, descriptive function names
- Write comprehensive descriptions for each tool
- Include parameter documentation in your functions

## Multiple Tools Registration

You can register multiple tools at once:

```php
if ( function_exists('flowmattic_add_mcp_tools') ) {
    $tools = array();
    
    // Tool 1: Get user data
    $tools[] = array(
        'name'          => 'Get User Data',
        'description'   => 'Retrieve user information by ID.',
        'function_name' => 'get_user_data',
        'parameters'    => array( 'user_id' ),
    );
    
    // Tool 2: Update user meta
    $tools[] = array(
        'name'          => 'Update User Meta',
        'description'   => 'Update user metadata fields.',
        'function_name' => 'update_user_meta_data',
        'parameters'    => array( 'user_id', 'meta_key', 'meta_value' ),
    );
    
    // Tool 3: Search content
    $tools[] = array(
        'name'          => 'Search Content',
        'description'   => 'Search posts and pages by keyword.',
        'function_name' => 'search_site_content',
        'parameters'    => array( 'keyword', 'post_types' ),
        'request_type'  => 'array',
    );

    // Register all tools under your plugin name
    flowmattic_add_mcp_tools( 'My Awesome Plugin', $tools );
}
```

## Troubleshooting

### Common Issues

1. **Tool not appearing**: Ensure FlowMattic is installed and `flowmattic_add_mcp_tools()` function exists
2. **Function not executing**: Check function name matches exactly in the tool definition
3. **Parameter errors**: Verify parameter names and types match your function signature
4. **Permission errors**: Ensure proper WordPress capabilities are checked

### Debug Tips

- Use WordPress error logs to debug function execution
- Test functions independently before registering as MCP tools
- Check FlowMattic admin interface for execution history and errors

## Conclusion

The FlowMattic MCP Server makes it incredibly easy to expose your custom WordPress functionality to MCP clients. With just a few lines of code, you can create powerful tools that integrate seamlessly with AI assistants and other MCP-compatible applications.

Remember to follow WordPress coding standards, implement proper security measures, and thoroughly test your tools before deployment.

---

# FlowMattic Sub-Workflows and How to Use Them

Source: https://support.flowmattic.com/kb/article/111/flowmattic-sub-workflows-and-how-to-use-them

Hey FlowMattic fans! If you've ever found yourself rebuilding the same workflow steps over and over, you're going to love what I'm about to show you. Sub-Workflows are going to change how you build automations—and I'm going to prove it with real examples you can use today.

**Quick note:** FlowMattic is a WordPress automation plugin, so all these workflows are built right in your WordPress admin. No external platforms needed!

## What This Feature Actually Does

Sub-Workflows let you build reusable workflow components that you can call from other workflows. Instead of copying the same 5 steps into 10 different workflows, you build those steps once and reference them whenever needed.

For anyone with programming experience, a Sub-Workflow works like a function—you pass in parameters, it does some work, and returns results you can use.

**But here's the real magic:** When you need to update those steps, you change them in one place and every workflow using them instantly gets the update. No more hunting through dozens of workflows making the same change over and over.

## The Three Key Components

Every Sub-Workflow setup uses these three pieces:

### 1. Start Sub-Workflow (Trigger)
- Used inside the Sub-Workflow only
- Defines what data (parameters) the Sub-Workflow receives
- Always the first step of a Sub-Workflow

### 2. Call Sub-Workflow (Action)
- Used in parent workflows (the ones calling the Sub-Workflow)
- Activates the Sub-Workflow and passes data to it
- Receives results back when Sub-Workflow completes

### 3. Return Response (Action)
- Used inside the Sub-Workflow only
- Always the last step of a Sub-Workflow
- Sends processed data back to the parent workflow

**Think of it like this:** The parent workflow says "Hey Sub-Workflow, here's some data, do your thing!" The Sub-Workflow processes it and says "Done! Here are your results."

### FlowMattic's Unique Workflow

FlowMattic has a smart approach to building Sub-Workflows that prevents errors:

1. **Create parent workflow first** - Add the Call Sub-Workflow action and configure parameters
2. **Create Sub-Workflow second** - Set trigger to Start Sub-Workflow
3. **Click "Capture Response"** - Sub-Workflow listens for incoming data
4. **Test parent workflow** - Sends data to Sub-Workflow
5. **Parameters captured automatically** - No manual configuration needed!

This "capture response" method ensures the Sub-Workflow knows exactly what parameters to expect. It's one of FlowMattic's best features.

---

## Real-World Example 1: Extracting and Formatting Email Data

Let me show you a practical example that'll make this crystal clear.

### The Scenario

You have multiple workflows that process contact information from different sources. Sometimes the email comes in a field with extra text, like:

- `Contact us at: john@example.com for more info`
- `john@example.com (preferred contact)`
- `Email: JOHN@EXAMPLE.COM`

You need to extract just the email, convert it to lowercase, and validate the format. You use this logic in 6 different workflows.

### The Sub-Workflow Solution

Instead of building the extraction logic 6 times, you build one Sub-Workflow.

**Sub-Workflow: "Extract and Validate Email"**

**Step 1 - Trigger: Start Sub-Workflow**
- Input parameter: `raw_text` (the field containing the email)

**Step 2 - Action: Text Formatter → Extract Pattern**
- Pattern: Email regex pattern
- Text: `{raw_text}`
- Result: Extracted email

**Step 3 - Action: Text Formatter → Lowercase**
- Text: Result from Step 2
- Result: Lowercase email

**Step 4 - Action: Text Formatter → Trim Whitespace**
- Text: Result from Step 3
- Result: Clean email

**Step 5 - Action: Filter (Optional)**
- Check if email format is valid
- If not valid, set error status

**Step 6 - Action: Return Response**
- `email`: Result from Step 4
- `is_valid`: `true` or `false` based on Filter
- `status`: `success` or `error`

### Using It in Parent Workflows

**Parent Workflow 1: "Google Forms → MailChimp"**

```
Trigger: New Google Forms response
  ↓
Action: Call Sub-Workflow → "Extract and Validate Email"
  → raw_text: {trigger.contact_field}
  ↓
Filter: Only continue if {call_sub_workflow.is_valid} = true
  ↓
Action: Add subscriber to MailChimp
  → Email: {call_sub_workflow.email}
```

**Parent Workflow 2: "Webform → HubSpot"**

```
Trigger: New webform submission
  ↓
Action: Call Sub-Workflow → "Extract and Validate Email"
  → raw_text: {trigger.email_info}
  ↓
Action: Create or update contact in HubSpot
  → Email: {call_sub_workflow.email}
```

**The Benefit:** Six workflows all use the same email extraction logic. Need to change how emails are validated? Update one Sub-Workflow, and all six workflows instantly use the new logic.

---

## Real-World Example 2: Tagging Team Members in Slack

Here's a real example similar to what many teams need.

### The Problem

You get lead notifications in Slack from various sources (website forms, trade shows, partnerships). When a lead comes in from a specific region, you need to tag the sales rep responsible for that region.

You have 4 different lead sources, and each needs this tagging logic.

### The Sub-Workflow Solution

**Sub-Workflow: "Tag Sales Rep by Region"**

**Step 1 - Trigger: Start Sub-Workflow**
- Input parameters:
  - `region` (the lead's region)
  - `original_message` (the Slack message to reply to)

**Step 2 - Action: Router (or Lookup Table)**
- Route based on `{region}`
- East Coast → Set sales_rep_id = "@sarah"
- West Coast → Set sales_rep_id = "@mike"  
- Midwest → Set sales_rep_id = "@jennifer"
- South → Set sales_rep_id = "@carlos"
- Default → Set sales_rep_id = "@sales-team"

**Step 3 - Action: Text Formatter**
- Create tagged message: `{sales_rep_id} - New lead in your region!`

**Step 4 - Action: Return Response**
- `tagged_message`: Result from Step 3
- `assigned_rep`: The sales rep's name
- `status`: `success`

### Parent Workflow: "Website Lead → Slack Notification"

```
Trigger: New lead from website form
  ↓
Action: Post message to #leads channel
  → Message: "New lead: {trigger.name} from {trigger.region}"
  → Save message timestamp
  ↓
Action: Call Sub-Workflow → "Tag Sales Rep by Region"
  → region: {trigger.region}
  → original_message: {previous_step.message_ts}
  ↓
Action: Post reply in thread
  → Thread: {original_message}
  → Message: {call_sub_workflow.tagged_message}
```

**Other workflows using the same Sub-Workflow:**
- "Trade Show Leads → Slack"
- "Partner Referrals → Slack"
- "Cold Outreach Responses → Slack"

All four workflows tag the right sales rep, and if sales territories change, you update the Sub-Workflow once.

---

## Real-World Example 3: Secure Data Access

This is a powerful pattern many teams don't think about.

### The Scenario

Your HR team manages sensitive employee data in BambooHR (salaries, personal info, etc.). Your sales operations team needs to onboard new sales reps, but HR doesn't want to give them direct access to BambooHR due to the sensitive information it contains.

### The Sub-Workflow Solution

HR creates a Sub-Workflow that acts as a secure gateway.

**Sub-Workflow: "Get New Hire Info" (Managed by HR team)**

**Step 1 - Trigger: Start Sub-Workflow**
- Input parameter: `employee_email`

**Step 2 - Action: BambooHR → Search Employee**
- Search by: `{employee_email}`

**Step 3 - Action: Return Response**
- `employee_name`: `{search_result.full_name}`
- `employee_email`: `{search_result.email}`
- `start_date`: `{search_result.start_date}`
- `manager_name`: `{search_result.manager}`
- `department`: `{search_result.department}`
- **Note:** Deliberately NOT returning salary, SSN, or other sensitive fields

### Sales Ops Team Uses It

**Parent Workflow: "New Hire Onboarding" (Built by Sales Ops)**

```
Trigger: New row in "New Hires" Google Sheet
  ↓
Action: Call Sub-Workflow → "Get New Hire Info"
  → employee_email: {trigger.email}
  ↓
Action: Send welcome email via Gmail
  → To: {call_sub_workflow.employee_email}
  → Body: "Welcome {call_sub_workflow.employee_name}! Your manager {call_sub_workflow.manager_name}..."
  ↓
Action: Create Asana onboarding tasks
  → Assignee: {call_sub_workflow.manager_name}
  → Title: "Onboard {call_sub_workflow.employee_name}"
  ↓
Action: Send Slack message to manager
  → User: {call_sub_workflow.manager_name}
  → Message: "New team member {call_sub_workflow.employee_name} starts {call_sub_workflow.start_date}"
```

**The Beauty:** Sales Ops can onboard new hires without accessing BambooHR directly. HR maintains control over what data is shared. If HR needs to change what data is available, they update the Sub-Workflow once.

---

## Real-World Example 4: Multi-Source Customer Lookup

Here's another common scenario that Sub-Workflows solve elegantly.

### The Problem

Your customer data is spread across multiple systems:
- CRM (Pipedrive) has contact info
- Billing system (Stripe) has payment history
- Support system (Zendesk) has ticket history

Multiple workflows need to gather all customer info, but you don't want to build this lookup logic repeatedly.

### The Sub-Workflow Solution

**Sub-Workflow: "Get Complete Customer Profile"**

**Step 1 - Trigger: Start Sub-Workflow**
- Input parameter: `customer_email`

**Step 2 - Action: Pipedrive → Find Person**
- Search by: `{customer_email}`
- Store: CRM data

**Step 3 - Action: Stripe → Find Customer**
- Search by: `{customer_email}`
- Store: Billing data

**Step 4 - Action: Zendesk → Search Users**
- Search by: `{customer_email}`
- Store: Support data

**Step 5 - Action: Text Formatter → Format**
- Combine all found data
- Create summary: "Found in CRM, Stripe, Zendesk" or "Only found in CRM"

**Step 6 - Action: Return Response**
- `customer_name`: From CRM
- `customer_phone`: From CRM
- `customer_since`: From Stripe
- `total_spent`: From Stripe
- `open_tickets`: From Zendesk
- `found_in_systems`: The summary from Step 5
- `status`: `complete` or `partial` (if not found in all systems)

### Multiple Teams Use It

**Sales Team Workflow: "Inbound Lead Enrichment"**
```
Trigger: New inbound lead
  ↓
Action: Call Sub-Workflow → "Get Complete Customer Profile"
  ↓
Action: Update lead record with historical data
  ↓
Action: Route to sales rep with context
```

**Support Team Workflow: "VIP Customer Alert"**
```
Trigger: New support ticket
  ↓
Action: Call Sub-Workflow → "Get Complete Customer Profile"
  ↓
Filter: If {call_sub_workflow.total_spent} > $10,000
  ↓
Action: Send VIP alert to support manager
```

**Marketing Team Workflow: "Re-engagement Campaign"**
```
Trigger: Schedule (weekly)
  ↓
Action: Get list of inactive customers
  ↓
Loop: For each customer
  ↓
Action: Call Sub-Workflow → "Get Complete Customer Profile"
  ↓
Action: Personalize email based on their history
```

---

## Real-World Example 5: API Token Management

If you work with APIs, this one's a game-changer.

### The Scenario

You need to authenticate with an API that requires you to:
1. Request an access token using credentials
2. Use that token in subsequent API calls
3. Tokens expire after 1 hour

You have 12 workflows that all need to interact with this API.

### The Sub-Workflow Solution

**Sub-Workflow: "Get API Access Token"**

**Step 1 - Trigger: Start Sub-Workflow**
- Input parameters:
  - `api_endpoint` (in case you have multiple environments)
  - `request_reason` (for logging purposes)

**Step 2 - Action: Webhooks → POST Request**
- URL: `{api_endpoint}/auth/token`
- Body: Your client_id and client_secret
- Store: The response

**Step 3 - Action: Text Formatter → Extract**
- Extract: `access_token` from response

**Step 4 - Action: Date Formatter**
- Get current timestamp
- Add 55 minutes (buffer before actual expiration)
- Store: token expiration time

**Step 5 - Action: Return Response**
- `access_token`: The extracted token
- `expires_at`: Calculated expiration time
- `status`: `success` or `error`

### Parent Workflows Use It

**Any workflow that needs API access:**
```
Trigger: (Whatever triggers your workflow)
  ↓
Action: Call Sub-Workflow → "Get API Access Token"
  → api_endpoint: "https://api.yourservice.com"
  → request_reason: "Daily sync"
  ↓
Action: Webhooks → GET Request
  → URL: Your API endpoint
  → Headers: Authorization: Bearer {call_sub_workflow.access_token}
  ↓
(Continue with your workflow logic)
```

**The Benefit:** If the authentication method changes, you update one Sub-Workflow instead of 12 different workflows. Plus, you can add logging, error handling, and retry logic in one place.

---

## Pro Tips and Patterns

### Pattern 1: The Status Checker

Always return a `status` field in your Sub-Workflows:

```
Return Response:
  → status: "success" or "error" or "partial"
  → error_message: (if status = error)
  → warning_message: (if status = partial)
  → (your actual data)
```

Then in parent workflows, add a Filter after the Sub-Workflow call:

```
Filter: Only continue if {call_sub_workflow.status} = "success"
```

### Pattern 2: The Audit Trail

Return metadata about what your Sub-Workflow did:

```
Return Response:
  → processed_at: {current_timestamp}
  → records_found: 3
  → records_updated: 2
  → records_failed: 1
  → (your actual data)
```

Use this in parent workflows for logging and monitoring.

### Pattern 3: The Fail-Safe

Handle errors gracefully in your Sub-Workflows:

```
Step X: Try to fetch data from API
  ↓
Filter: Did it succeed?
  ↓ (Yes)
Path A: Return successful data
  ↓ (No)
Path B: Return Response
  → status: "error"
  → error_message: "API unavailable"
  → fallback_data: (default values)
```

This keeps parent workflows running even when something goes wrong.

### Pattern 4: The Dynamic Router

Use lookup tables or routers in Sub-Workflows:

```
Sub-Workflow: "Route to Right Team"
Input: ticket_type, priority
  ↓
Router based on ticket_type + priority:
  → Bug + High → Return team: "engineering_leads"
  → Bug + Low → Return team: "engineering"
  → Feature + Any → Return team: "product"
  → Question + High → Return team: "customer_success"
  → Default → Return team: "support"
```

One Sub-Workflow, dynamic routing logic, used everywhere.

---

## Common Mistakes to Avoid

### Mistake 1: Making Sub-Workflows Too Complex

**Don't:**
Build one "mega Sub-Workflow" that does 15 different things based on complex conditional logic.

**Do:**
Build focused Sub-Workflows that do one thing well. Create multiple Sub-Workflows if needed.

### Mistake 2: Forgetting the Return Response

**Don't:**
Forget to add the Return Response action at the end.

**Do:**
Always end with Return Response, even if you're not returning data. Use it to return a simple status.

### Mistake 3: Hardcoding Values

**Don't:**
Hardcode things like URLs, IDs, or settings in your Sub-Workflow.

**Do:**
Pass these as parameters so the Sub-Workflow is flexible and reusable.

### Mistake 4: Not Testing Edge Cases

**Don't:**
Only test with perfect, happy-path data.

**Do:**
Test with empty values, special characters, extremely long strings, and invalid data to ensure your Sub-Workflow handles everything gracefully.

### Mistake 5: Creating Circular References

**Don't:**
Have Sub-Workflow A call Sub-Workflow B, which calls Sub-Workflow A.

**Do:**
Plan your Sub-Workflow architecture to avoid loops. Draw it out if needed.

---

## When Should You Build a Sub-Workflow?

Use this decision framework:

**Build a Sub-Workflow if:**
- ✅ You use the same steps in 3+ workflows
- ✅ You might use these steps in future workflows
- ✅ The logic is complex and you want to maintain it in one place
- ✅ Multiple team members need to use the same process
- ✅ You need to update the logic frequently

**Don't build a Sub-Workflow if:**
- ❌ You only use it in one workflow
- ❌ The logic is just 1-2 simple steps
- ❌ It's highly specific to one use case and won't be reused
- ❌ It's simpler to just copy the steps

---

**Questions or examples to share?** Visit [FlowMattic Support](https://support.flowmattic.com) or join our community forum!

---

**Related Articles:**
- Understanding Sub-Workflows in FlowMattic
- Create Reusable Workflow Steps with Sub-Workflows

---

# FlowMattic Tables CSV Export Guide

Source: https://support.flowmattic.com/kb/article/101/flowmattic-tables-csv-export-guide

## Overview
The CSV Export feature in FlowMattic Tables enables you to export your table data to CSV format for use in spreadsheet applications, data analysis tools, or backup purposes. With selective column export, custom naming, and proper formatting, you have complete control over your data exports.

## Prerequisites
- **Access Requirements**: Administrator privileges in FlowMattic
- **Browser Requirements**: Modern browser with JavaScript enabled
- **Table Data**: Existing table with data to export
- **Storage Space**: Sufficient local storage for downloaded file

## Key Features
- 📊 **Full Table Export**: Export all records from your table
- 🎯 **Selective Column Export**: Choose specific columns to include
- 📝 **Custom Filenames**: Name your export files meaningfully
- ⚡ **Instant Download**: Automatic download upon completion
- 🔒 **Data Integrity**: Proper escaping and formatting
- 📈 **Excel Compatible**: Works with all major spreadsheet applications

## Step-by-Step Export Process

### Step 1: Access the Export Feature
1. Navigate to your FlowMattic table
2. Locate the **Export CSV** button in the top toolbar (gray button with download icon)
3. Click to open the export modal

![Tables ‹ FlowMattic — Export CSV.png](/storage/kb-images/67c931b132-inline.png)

### Step 2: Configure Export Settings

#### Setting the Filename
1. The filename field is pre-populated with your table name
2. Customize the filename as needed (without .csv extension)
3. Use descriptive names for easy identification

![Tables ‹ FlowMattic — Export CSV.png](/storage/kb-images/aff5714e69-inline.png)

**Filename Guidelines:**
- ✅ Allowed: Letters, numbers, spaces, hyphens, underscores
- ❌ Not allowed: Special characters like /, \, *, ?, <, >, |
- 📝 Maximum length: 100 characters
- 🔄 Extension (.csv) is added automatically

**Good filename examples:**
- `customers_2025_january`
- `product_inventory_backup`
- `sales_data_Q1`
- `user_list_export`

### Step 3: Select Columns to Export (Optional)

#### Viewing Current Selection
By default, all columns are selected for export. The export modal shows:
- **Records**: Total number of rows to be exported
- **Columns**: Number of columns currently selected
- **Estimated Size**: Approximate file size

![Tables ‹ FlowMattic — Export stats.png](/storage/kb-images/a567354605-inline.png)

#### Customizing Column Selection
1. Click the **Change** link next to the column count
2. The column selection panel appears
3. Select/deselect columns as needed

![Tables ‹ FlowMattic — WordPress 2025-09-09 at 3.01.49 PM.png](/storage/kb-images/979e39278f-inline.png)

#### Column Selection Features:
- **Individual Selection**: Click checkbox next to each column
- **Select All**: Click to select all columns at once
- **Deselect All**: Click to clear all selections
- **Apply Selection**: Confirms your column choices

**Selection Tips:**
- Export only the columns you need to reduce file size
- Consider privacy when sharing exports - exclude sensitive columns
- At least one column must be selected
- Column order in export matches table structure

### Step 4: Review Export Information
Before proceeding, review the export details:

**Export Information Displayed:**
- **All Records**: Confirms all table records will be exported
- **Processing Time**: Estimate based on data volume
- **File Format**: Standard CSV with headers
- **Download Method**: Automatic browser download

### Step 5: Execute the Export
1. Click the **Export CSV** button
2. Export processing begins immediately
3. Progress bar shows completion status

![Tables ‹ FlowMattic — Exporting CSV.png](/storage/kb-images/54bc41db29-inline.png)

**During Export:**
- Progress bar animates to show activity
- Status message: "Exporting Data..."
- Modal cannot be closed (prevents interruption)
- Browser must remain open

### Step 6: Download Completion
When export completes:
1. Status shows "Export completed! Starting download..."
2. File automatically downloads to your default download folder
3. Modal closes automatically after 2 seconds
4. Table remains accessible throughout


## Understanding Your Exported CSV

### File Structure
Your exported CSV file will have this structure:
```csv
id,customer_name,email,registration_date,status
1,"John Doe",john@example.com,2025-01-15,active
2,"Jane Smith",jane@example.com,2025-01-16,pending
3,"Bob Johnson",bob@example.com,2025-01-17,active
```

### Data Formatting Standards

#### Headers
- First row always contains column headers
- Headers match your table column names
- Headers are properly escaped if containing special characters

#### Data Rows
- Each row represents one table record
- Fields are comma-separated
- Text fields with commas are quoted
- Empty fields are represented as empty (not NULL)

#### Special Character Handling
| Character | How It's Handled | Example |
|-----------|-----------------|---------|
| Comma | Field enclosed in quotes | `"Smith, John"` |
| Quote | Doubled within quotes | `"She said ""Yes"""` |
| Newline | Preserved within quotes | `"Line 1\nLine 2"` |
| Tab | Preserved as-is | `"Value	with	tabs"` |

## Advanced Export Features

### Selective Column Export
Perfect for creating specialized exports:

**Use Cases:**
- **Privacy Compliance**: Exclude personal information
- **Department Specific**: Export only relevant columns
- **File Size Optimization**: Reduce large exports
- **Integration Ready**: Match required import formats

**Example Scenarios:**
1. **Customer List for Marketing**: 
   - Include: name, email, preferences
   - Exclude: passwords, payment info

2. **Inventory Report**:
   - Include: product_id, name, quantity, price
   - Exclude: internal notes, supplier details

3. **Public Data Share**:
   - Include: aggregated statistics
   - Exclude: individual identifiers

### Export Performance

#### File Size Estimates
| Records | Columns | Estimated Size |
|---------|---------|---------------|
| 100 | 5 | ~10 KB |
| 1,000 | 10 | ~200 KB |
| 10,000 | 15 | ~3 MB |
| 100,000 | 20 | ~40 MB |

#### Export Speed
- **Small tables** (<1,000 rows): Instant
- **Medium tables** (1,000-10,000): 1-3 seconds
- **Large tables** (10,000-100,000): 5-15 seconds
- **Very large tables** (100,000+): 15-60 seconds

## Working with Exported Data

### Opening in Excel/Google Sheets

#### Microsoft Excel
1. Double-click the CSV file, or
2. Open Excel → Data → From Text/CSV
3. Excel automatically detects delimiters
4. Verify data types are correct

#### Google Sheets
1. Open Google Sheets
2. File → Import → Upload
3. Select your CSV file
4. Choose import options:
   - Create new spreadsheet
   - Replace current sheet
   - Append to current sheet

#### Numbers in Mac
1. Open Numbers app
2. Choose the exported CSV file
3. Open the file in Numbers app to visualize all the data
4. Verify the data

![Customers - Export opened in CSV reader.png](/storage/kb-images/cb045b8bda-inline.png)

### Common Post-Export Tasks

#### Data Analysis
- Apply filters and sorting
- Create pivot tables
- Generate charts and graphs
- Perform calculations

#### Data Transformation
- Merge with other datasets
- Clean and standardize formats
- Remove duplicates
- Add calculated columns

#### Data Sharing
- Email as attachment
- Upload to cloud storage
- Import into other systems
- Create backups

## Use Cases and Examples

### Use Case 1: Regular Backups
**Scenario**: Weekly backup of customer data
**Process**:
1. Export every Friday
2. Use naming: `customers_backup_YYYY_MM_DD`
3. Store in backup folder
4. Keep last 4 weeks of backups

### Use Case 2: Data Migration
**Scenario**: Moving data to new system
**Process**:
1. Export all columns
2. Review in spreadsheet application
3. Transform as needed
4. Import to new system

### Use Case 3: Reporting
**Scenario**: Monthly sales report
**Process**:
1. Export sales table
2. Select relevant columns only
3. Open in Excel
4. Create pivot tables and charts

### Use Case 4: Data Cleaning
**Scenario**: Identify and fix data issues
**Process**:
1. Export full table
2. Open in spreadsheet
3. Use filters to find issues
4. Fix in spreadsheet
5. Re-import cleaned data

## Troubleshooting Common Issues

### Issue: Download Doesn't Start
**Possible Causes & Solutions:**
- **Browser blocking downloads**: Check browser settings
- **Pop-up blocker**: Allow pop-ups for this site
- **Download folder full**: Clear space on hard drive

### Issue: File Won't Open in Excel
**Possible Causes & Solutions:**
- **File association**: Right-click → Open with → Excel
- **Import wizard**: Use Excel's import feature
- **Encoding issues**: Open in text editor first

### Issue: Special Characters Display Incorrectly
**Possible Causes & Solutions:**
- **Encoding mismatch**: Ensure UTF-8 support in target application
- **Import settings**: Specify UTF-8 when importing
- **Regional settings**: Check system locale settings

### Issue: Missing Data in Export
**Possible Causes & Solutions:**
- **Column selection**: Verify all needed columns are selected
- **Filter active**: Check if table has active filters
- **Permissions**: Ensure you have access to all data

### Issue: Export Takes Too Long
**Possible Causes & Solutions:**
- **Large dataset**: Be patient, large exports take time
- **Browser resources**: Close other tabs
- **Network speed**: Ensure stable connection

## Best Practices

### Before Exporting
1. **Plan Your Export**: Decide which columns you need
2. **Check Data**: Ensure table data is current
3. **Clear Filters**: Remove any active filters if you want all data
4. **Consider Privacy**: Exclude sensitive columns if sharing

### During Export
1. **Don't Navigate Away**: Stay on the page
2. **Avoid Other Actions**: Don't modify table during export
3. **Monitor Progress**: Watch for completion
4. **Be Patient**: Large exports take time

### After Export
1. **Verify Download**: Check your downloads folder
2. **Open and Review**: Quickly verify data integrity
3. **Backup Important Exports**: Save to secure location
4. **Document Export**: Note date and purpose

## Security and Privacy

### Data Security
- Export happens server-side securely
- No data cached in browser
- Direct download to your computer
- No intermediate cloud storage

### Privacy Considerations
- **Before Sharing Exports**:
  - Remove sensitive columns
  - Anonymize personal data if needed
  - Check for internal notes/comments
  - Verify recipient authorization

### Compliance Tips
- **GDPR**: Export only necessary personal data
- **HIPAA**: Exclude health information when appropriate
- **PCI**: Never export full credit card numbers
- **Internal Policies**: Follow company data handling rules

## Performance Optimization

### For Large Exports
1. **Export During Off-Hours**: Reduces server load
2. **Selective Columns**: Export only needed columns
3. **Split Exports**: Consider multiple smaller exports
4. **Close Other Applications**: Free up system resources

### Browser Settings
- Enable automatic downloads
- Set adequate timeout values
- Clear browser cache regularly
- Use modern browser version

## File Management

### Organizing Exports
```
/exports
  /2025
    /january
      customers_2025_01_15.csv
      products_2025_01_15.csv
    /february
      customers_2025_02_15.csv
      products_2025_02_15.csv
```

### Naming Conventions
- Include table name
- Add date stamp
- Indicate purpose (backup, report, share)
- Use version numbers if needed

### Storage Best Practices
- Regular cleanup of old exports
- Compress large CSV files
- Use cloud backup for important exports
- Document export purposes

## Limitations and Considerations

### Technical Limitations
- **Maximum File Size**: Limited by browser and system memory
- **Concurrent Exports**: One export at a time per table
- **Format**: Only CSV format available (not Excel, JSON)
- **Real-time Data**: Export captures data at moment of export

### Data Limitations
- **No Formulas**: Calculated fields export as values
- **No Formatting**: Colors, fonts, styles not preserved
- **No Relationships**: Foreign keys export as values
- **No Metadata**: Comments and notes not included

## Quick Reference Checklist

### Pre-Export Checklist
- [ ] Table data is up to date
- [ ] Decided which columns to export
- [ ] Chosen appropriate filename
- [ ] Cleared unnecessary filters
- [ ] Have sufficient disk space

### Export Process Checklist
- [ ] Click Export CSV button
- [ ] Enter custom filename
- [ ] Select specific columns (if needed)
- [ ] Click Export button
- [ ] Wait for download to complete

### Post-Export Checklist
- [ ] File downloaded successfully
- [ ] Data opens correctly
- [ ] All expected columns present
- [ ] Row count matches expectations
- [ ] File saved to appropriate location

## Getting Help

If you need assistance with exports:

1. **Check Documentation**: Review this guide
2. **FAQ Section**: Access via Help button
3. **Test Export**: Try with small dataset first
4. **Support Contact**: Provide:
   - Table name and size
   - Selected columns
   - Error messages
   - Browser information

## Summary

The CSV Export feature provides a robust, secure, and efficient way to extract your table data for external use. With selective column export, proper formatting, and automatic download, you can quickly get your data where you need it while maintaining data integrity and security.

Remember:
- ✅ Always verify your column selection
- ✅ Use descriptive filenames
- ✅ Check exported data after download
- ✅ Store exports securely
- ✅ Clean up old exports regularly

---

*Last updated: September, 2025*
*FlowMattic Version: 5.3.0+*

---

# FlowMattic Tables CSV Import Guide

Source: https://support.flowmattic.com/kb/article/100/flowmattic-tables-csv-import-guide

## Overview
The CSV Import feature in FlowMattic Tables allows you to bulk import data from CSV files into your database tables. This powerful feature supports intelligent column mapping, batch processing for large files, and provides a preview before importing to ensure data accuracy.

## Prerequisites
- **Access Requirements**: Administrator privileges in FlowMattic
- **File Format**: CSV file with UTF-8 encoding
- **File Size**: No strict limit (large files are processed in batches)
- **Browser Requirements**: Modern browser with JavaScript enabled
- **Table Setup**: Existing table with columns defined

## What You Can Do
- 🎯 **Automatic Column Matching**: The system figures out which CSV columns go with which table columns
- 📁 **Easy File Upload**: Just drag and drop your CSV file or click to browse
- 👀 **Preview Before Import**: See exactly how your data will look before committing
- ⚡ **Handle Large Files**: Import thousands of rows without browser crashes
- 🔄 **Watch Progress Live**: See your data being added to the table as it imports
- 📝 **Smart Header Detection**: Automatically skips header rows in your CSV
- ✨ **Clear Visual Feedback**: Progress bars and indicators show you what's happening

## Step-by-Step Import Process

### Step 1: Access the Import Feature
1. Navigate to your FlowMattic table
2. Locate the **Import CSV** button in the top toolbar (green button with upload icon)
3. Click to open the import modal

![Tables ‹ FlowMattic —  Import CSV](/storage/kb-images/b680386239-inline.png)

### Step 2: Upload Your CSV File
You have two options for uploading your CSV file:

#### Option A: Drag and Drop
1. Drag your CSV file from your computer
2. Drop it onto the designated upload area
3. The file will automatically begin processing

#### Option B: Browse and Select
1. Click the **Browse Files** button
2. Navigate to your CSV file location
3. Select the file and click Open

![Tables ‹ FlowMattic — Drag and drop CSV import.png](/storage/kb-images/11271cb0c5-inline.png)

**What happens after upload:**
- File is validated for CSV format
- Headers are extracted automatically
- File size and row count are displayed
- Progress to the column mapping step

### Step 3: Map CSV Columns to Table Columns
This is the most important step where you define how your CSV data maps to your table structure.

![Tables ‹ FlowMattic — CSV import column mapping.png](/storage/kb-images/4cabbcbbda-inline.png)

#### Understanding the Mapping Interface
- **Left side**: Shows your CSV column names with sample data
- **Arrow (→)**: Visual indicator of mapping direction  
- **Right side**: Dropdown to select corresponding table column

#### Auto-Mapping Feature
The system automatically attempts to match columns based on:
1. **Exact matches**: "customer_id" → "customer_id"
2. **Similar names**: "email_address" → "email"
3. **Normalized matches**: "First-Name" → "first_name"

#### Manual Mapping Adjustments
1. Review each auto-mapped column
2. Click the dropdown to change mapping if needed
3. Select "Skip this column" for CSV columns you don't want to import

#### Important Mapping Rules
- Each table column can only be mapped to one CSV column
- Required table columns must be mapped
- Unmapped CSV columns will be skipped
- Unmapped table columns will be left empty (or use default values)

### Step 4: Configure Import Options

#### Skip Header Row Option
- ✅ **Checked (Default)**: First row is treated as headers and not imported
- ⬜ **Unchecked**: First row is imported as data

**When to uncheck:**
- Your CSV file doesn't have headers
- Headers were already removed
- First row contains actual data

![Tables ‹ FlowMattic — Skip CSV headers.png](/storage/kb-images/aaf3feed89-inline.png)

### Step 5: Preview Your Import
Before committing to the import, review the preview to ensure data accuracy.

![Tables ‹ FlowMattic — Import preview.png](/storage/kb-images/0240cc7da5-inline.png)

#### What to Check in Preview:
1. **Data Alignment**: Ensure data appears in correct columns
2. **Data Types**: Verify numbers, dates, and text are properly formatted
3. **Special Characters**: Check that special characters display correctly
4. **Empty Fields**: Confirm how empty CSV fields are handled

#### Preview Table Features:
- Shows first 5 rows of data to be imported
- Headers display in human-readable format
- Empty cells are clearly indicated
- Data is formatted as it will appear in the table

### Step 6: Execute the Import
Once you're satisfied with the preview:

1. Click the **Import Data** button
2. The import process begins with a progress indicator
3. **DO NOT close the browser window** during import

![Tables ‹ FlowMattic — Import progress - completed.png](/storage/kb-images/d34b25972c-inline.png)

#### Import Progress Information:
- **Progress Bar**: Shows overall completion percentage
- **Batch Counter**: Displays current batch (e.g., "Processing batch 3 of 10")
- **Row Counter**: Shows rows processed (e.g., "150 of 500 rows imported")
- **Real-time Updates**: Table refreshes automatically every 5 batches to show imported data
- **Time Estimate**: Approximate time remaining for large imports

### Step 7: Import Completion
Upon successful import:
- ✅ Success message displays with total rows imported
- Table shows imported data in real-time during the process
- Final refresh ensures all data is visible
- Import modal can be safely closed
- Any errors are reported with specific row numbers

## Data Formatting Guidelines

### CSV File Requirements
```csv
id,customer_name,email,registration_date,status
1,"John Doe",john@example.com,2025-01-15,active
2,"Jane Smith",jane@example.com,2025-01-16,pending
```

### Supported Data Types
| Table Column Type | CSV Format | Example |
|------------------|------------|---------|
| Text | Plain text, quoted if contains commas | "John, Jr." |
| Number | Numeric values without quotes | 123.45 |
| Date | YYYY-MM-DD or MM/DD/YYYY | 2025-01-15 |
| Boolean | true/false, yes/no, 1/0 | true |
| Email | Valid email format | user@example.com |
| URL | Valid URL format | https://example.com |

### Special Characters Handling
- **Commas**: Enclose field in double quotes: `"Smith, John"`
- **Quotes**: Escape with double quotes: `"He said ""Hello"""`
- **Newlines**: Enclose field in quotes: `"Line 1\nLine 2"`
- **Unicode**: Ensure file is UTF-8 encoded

## Advanced Features

### Importing Large Files
Don't worry about large CSV files - the system handles them automatically:

- **Automatic Processing**: Large files are broken into smaller chunks and processed piece by piece
- **No Browser Crashes**: Your browser won't freeze or crash even with huge files
- **Progress Updates**: You'll see your table update regularly as chunks are processed
- **Error Protection**: If something goes wrong with one chunk, the previously imported data is safe
- **Sit Back and Relax**: Everything happens automatically - you just need to keep your browser open

### Watching Your Import Progress
As your CSV file is being imported, you can actually watch your data appear in the table in real-time! Here's what you'll see:

#### What Happens During Import
- **Your table updates automatically**: Every few seconds during the import, your table will refresh to show the newly added records
- **Visual indicator**: When the table is refreshing, you'll see a small "Refreshing Table" badge appear next to the import title with a spinning icon
- **No interruption**: The import continues normally while you can see the progress in your actual table

#### Why This is Helpful
- **Peace of mind**: You can see that your data is actually being imported correctly
- **Catch issues early**: If something looks wrong with your data, you'll notice it during the import rather than at the end
- **Track progress**: Watch as your table grows with each batch of imported records
- **Stay engaged**: Instead of waiting blindly, you can see exactly what's happening

This means you don't have to wait until the very end of the import to see if everything worked correctly!

### How Smart Column Matching Works
The system automatically tries to match your CSV columns to your table columns by looking for similarities:

1. **Perfect matches first**: If your CSV has a column called "email" and your table has an "email" column, they'll be matched automatically
2. **Similar names**: Columns like "customer_name" in your CSV might match to "Customer Name" in your table
3. **Partial matches**: A CSV column "first_name" could match to a table column called "name"
4. **Flexible formatting**: The system ignores differences in spaces, hyphens, and underscores

This saves you time by doing most of the column matching work automatically, but you can always change the matches manually if needed.

## Common Issues and Solutions

### Issue: "Invalid CSV Format" Error
**Cause**: File is not properly formatted as CSV
**Solution**: 
- Ensure file has .csv extension
- Save Excel files as CSV (not XLS/XLSX)
- Check for proper comma separation

### Issue: Data Appears in Wrong Columns
**Cause**: Incorrect column mapping
**Solution**:
- Return to mapping step
- Manually adjust column assignments
- Verify sample data in mapping interface

### Issue: Special Characters Display Incorrectly
**Cause**: Encoding issues
**Solution**:
- Save CSV file with UTF-8 encoding
- Use text editor to verify encoding
- Remove or replace problematic characters

### Issue: Import Stops or Fails
**Cause**: Network issues or browser timeout
**Solution**:
- Check internet connection
- Don't close browser during import
- For very large files, split into smaller CSVs

### Issue: Duplicate Column Mapping
**Cause**: Multiple CSV columns mapping to same table column
**Solution**:
- System prevents this automatically in latest version
- Each table column can only be mapped once
- Review and adjust mappings manually if needed

## Best Practices

### Before Importing
1. **Backup Your Data**: Always backup existing table data
2. **Clean Your CSV**: Remove unnecessary columns and rows
3. **Validate Format**: Open in text editor to verify structure
4. **Test Small**: Try with a few rows first

### During Import
1. **Stay on Page**: Don't navigate away during import
2. **Monitor Progress**: Watch progress bar and batch counter
3. **Observe Real-time Updates**: Watch imported data appear in table
4. **Watch for Refresh Badge**: Notice when table is updating automatically
5. **Check for Errors**: Monitor for any error messages or failed batches

### After Import
1. **Verify Data**: Check a sample of imported records
2. **Check Totals**: Confirm row count matches expectations
3. **Test Functionality**: Ensure imported data works with your workflows
4. **Document Import**: Note date, file, and any issues

## Performance Tips

### Optimizing Large Imports
- **Split Large Files**: Divide files over 10,000 rows
- **Remove Unused Columns**: Import only necessary data
- **Clean Data First**: Fix formatting issues before import
- **Use Off-Peak Hours**: Import during low-traffic periods

### File Preparation Checklist
- [ ] CSV saved in UTF-8 encoding
- [ ] Headers in first row (if applicable)
- [ ] No empty rows in middle of data
- [ ] Special characters properly escaped
- [ ] Date formats consistent
- [ ] Numeric fields don't contain text

## Security Considerations
- Files are processed server-side securely
- No data is stored in browser cache
- Temporary files are deleted after import
- All data is sanitized before database insertion
- User permissions are validated

## Limitations
- **File Types**: Only CSV files supported (not Excel, JSON, XML)
- **Rollback**: No automatic undo after successful import
- **Concurrent Imports**: Only one import at a time per table
- **Batch Size**: Fixed at 50 rows per batch for optimal performance
- **Browser Dependency**: Requires keeping browser tab open during import

## Troubleshooting Checklist
If your import isn't working as expected:

1. ✓ Is the file in CSV format?
2. ✓ Are all required table columns mapped?
3. ✓ Is the browser window staying open?
4. ✓ Is the internet connection stable?
5. ✓ Are special characters properly escaped?
6. ✓ Is the file encoding UTF-8?
7. ✓ Are date formats consistent?
8. ✓ Have you checked the preview?

## Getting Help
If you encounter issues not covered in this guide:
1. Check the FlowMattic documentation
2. Review the FAQ section in the Help modal
3. Contact FlowMattic support with:
   - Table name and structure
   - Sample of your CSV file
   - Error messages received
   - Browser and version used

---

*Last updated: 9 September, 2025*
*FlowMattic Version: 5.3.0+*

---

# FlowMattic Tables: premium field types, Summarize, and Views

Source: https://support.flowmattic.com/kb/article/206/flowmattic-tables-field-types-and-grid-features

FlowMattic Tables is more than rows and columns — every column has a **type**, and the grid renders each type the way a modern data tool would: people get avatars, tags get colored pills, files get previews, and formulas compute live. This article walks through every field type and the grid features built around them, so you can see at a glance what makes FlowMattic Tables different from the free WP Tables screen.

![A FlowMattic Table with Person, Dropdown, Tags, Rating, Calculate, and Percent columns rendered in the grid](https://assets.infidesk.support/products/flowmattic/kb-images/tables/11-table-hero.png)

## WP Tables vs. FlowMattic Tables — the difference at a glance

FlowMattic includes two data screens, and it's easy to mix them up:

- **WP Tables** (free, included with FlowMattic) — custom tables stored **inside your WordPress database**. They support the standard column types: Text, Long Text, Rating, Dropdown, Link, Email, Number, Date, Date & Time, Checkbox, Image, and Button.
- **FlowMattic Tables** (premium add-on) — a **managed database hosted on our servers**, isolated from your WordPress database. It supports everything WP Tables does **plus the premium types below**, along with Summarize footers, saved Views, CSV import with automatic type detection, scheduled exports, and point-in-time recovery.

If a column type in the **Add column** dialog only appears for FlowMattic Tables, it's one of the premium types.

## Premium field types

Open any FlowMattic Table and click **Add column** to see the full list:

![The Add column dialog showing the full column type list](https://assets.infidesk.support/products/flowmattic/kb-images/tables/07-add-column.png)

### Person

Stores a person as first name, last name, and email. The grid renders a colored avatar with the person's initials next to their name — the **email drives the avatar**, so the same person always gets the same color. In workflows you can fill Person fields from trigger data without writing JSON; the action's typed fields take first name, last name, and email separately.

### Tags

A multi-value field rendered as pills, each with a colored dot. Define the allowed tags (and their colors) in the column options. A row can hold any number of tags. In workflows you can pass tags as a simple comma-separated list — `Urgent, Design` — and FlowMattic converts it to the right format at execution.

### Attachment

Holds a list of files. Images render as mini thumbnails; other files get a file icon. Each entry is a clickable link, and long lists collapse to "+2 more files". Perfect for storing invoices, contracts, or images produced by your workflows.

### Currency

Stores amounts in **minor units** (cents, pence) so the math is always exact, and displays them formatted for the column's currency code — `4999` with code USD renders as `$49.99`. Summarize totals respect the currency formatting too.

### Calculate (formula)

A read-only column computed from other columns in the same row. Formulas reference fields in braces and support `+ - * / ( )` and the functions `ROUND(x, digits)`, `ABS(x)`, `MIN(…)`, and `MAX(…)`:

```
ROUND({price} * {qty} * (1 - {discount}), 2)
```

The result recomputes live as you edit the referenced cells, and Calculate columns can be summarized (Sum, Average, Min, Max) like any numeric column.

### Relation

Links a row to a record in **another FlowMattic Table**. The cell shows the related row's ID plus a display field you choose (for example, show the customer's name from your Customers table on each order). Use it to keep orders, contacts, and companies in separate tables that still connect.

### AI Text

A text column with a per-column **AI prompt template**. Reference other fields in the prompt — for example `Summarize this feedback: {feedback}` — then click the ✦ **Generate** button in any cell and FlowMattic fills it using AI. Great for summaries, category suggestions, or draft replies sitting right next to your data.

### Percent

A number from 0–100 rendered as a progress bar with the value beside it. The bar is color-coded: amber below 40, blue up to 70, green above — so status reads at a glance.

### Phone, URL, and Color

- **Phone** renders as a click-to-call `tel:` link.
- **URL** renders as a clean clickable link (FlowMattic adds `https://` for you if it's missing).
- **Color** shows a color swatch next to the hex value — handy for brand or label data.

### Created By / Modified By

Automatic, read-only attribution columns. **Created By** records the WordPress user who added each row; **Modified By** updates to whoever last edited it — whether the change came from the grid or from a workflow run by that user. The grid renders the WP user's avatar and name.

## Summarize — totals in the footer

Every column's ⋮ menu has a **Summarize** section. Numeric columns (Number, Currency, Rating, Percent, Calculate) offer **Sum, Average, Min, and Max**; every column offers **Count**, which counts non-empty cells.

![The column menu with the Summarize options — Sum, Average, Min, Max, Count](https://assets.infidesk.support/products/flowmattic/kb-images/tables/12-column-menu-summarize.png)

Chosen summaries appear as chips in the grid footer — for example `AVG Rating 3.92`, `SUM Total 538.08` — and update live as you edit, filter, or add rows. Currency columns format their totals in the column's currency.

## Views — save a way of looking at your data

A **View** captures the grid exactly as you have it: the active filter, the sort, which columns are hidden, and the page size. Set the grid up the way you like, open **Views**, type a name, and click **Save current**.

![The Views menu with saved views and the Save current input](https://assets.infidesk.support/products/flowmattic/kb-images/tables/13-views-menu.png)

Views are saved with the table, so the whole team sees them. One click applies a view; the × next to a view deletes it. Typical uses: "Urgent only" (filtered by a tag), "Pipeline review" (sorted by value, noise columns hidden), or a compact 50-rows-per-page view for triage.

## The rest of the grid

A few more features you get on every FlowMattic Table:

- **Inline editing** — double-click any cell, edit, and hit Save changes. Each type gets the right editor: a star picker for ratings, a date picker for dates, a color picker for colors.
- **Sort, filter, and search** — per-column sort and filter live in each column's ⋮ menu; the search box scans the whole table.
- **Columns** — show or hide any column from the Columns menu; autofit one or all columns from the ⋮ menu.
- **Export** — download your table from the Export menu — once a day on Starter, on demand on Pro and Business; the dashboard also runs scheduled exports depending on your plan.
- **Summary bar** — the footer always shows the live record count alongside your Summarize chips.

## Use them from workflows

All of these types are first-class in workflow actions. **Insert Row**, **Update Row**, and **Update Cell** show typed fields per column — separate first/last/email inputs for Person, tag checkboxes for Tags, a color picker for Color — and every field also accepts dynamic data from previous steps. See [Use FlowMattic Tables in workflows](/kb/use-flowmattic-tables-in-workflows) for the full walkthrough.

---

# FlowMattic Tables REST API — Developer Guide

Source: https://support.flowmattic.com/kb/article/220/flowmattic-tables-rest-api

The FlowMattic Tables REST API lets developers read and write your [FlowMattic Tables](https://flowmattic.com/flowmattic-tables/) data programmatically — from a mobile app, a serverless function, another site, or any HTTP client. It exposes row-level CRUD plus read-only table metadata, secured by scoped, revocable API keys that are separate from your other FlowMattic keys.

Calls made through the API count toward your FlowMattic Tables reads and writes, and can optionally be logged on your own site for auditing.

> **Availability:** FlowMattic **7.0.1+**, with FlowMattic Tables connected on the site. If the managed service is not connected, every endpoint returns `503`.

---

## 1. Generate an API key

Open **FlowMattic → FlowMattic Tables**, then click **API Keys** in the page header. This screen manages your keys, shows your connection details, and controls request logging.

![FlowMattic Tables API Keys screen](https://assets.infidesk.support/products/flowmattic/kb-images/tables-api/api-keys.png)

Click **New API key** and configure the key:

![Create API key dialog](https://assets.infidesk.support/products/flowmattic/kb-images/tables-api/create-key-modal.png)

- **Label** — a name to recognize the key later (e.g. *Mobile app*).
- **Operations** — any combination of **Read**, **Create**, **Update**, **Delete**. The key can only perform the operations you tick.
- **Tables** — **All tables**, or **Only specific tables** (pick from your tables, or type comma‑separated names). The key can only touch the tables in its scope.

Click **Generate key**. The full key (format `fmtk_…`) is shown **once** — copy it immediately and store it somewhere safe. FlowMattic only keeps a hashed copy, so it can never show the key again. If a key leaks, **revoke** it from the list and issue a new one; revocation takes effect immediately.

---

## 2. Authentication

Every request needs your key as a **Bearer token**.

**Base URL**

```
https://your-site.com/wp-json/flowmattic/v1/tables-api/
```

**Auth header**

```
Authorization: Bearer fmtk_your_key_here
```

If your client can't set an `Authorization` header, you may instead send the key in an `X-FlowMattic-Tables-Key` header.

---

## 3. Endpoints at a glance

| Method | Path | Scope | Purpose |
| --- | --- | --- | --- |
| `GET` | `/tables` | read | List all tables (with schema + record counts) |
| `GET` | `/tables/{table}` | read | Get one table's schema |
| `GET` | `/tables/{table}/rows` | read | List rows (filter, sort, paginate) |
| `GET` | `/tables/{table}/rows/{id}` | read | Get a single row by id |
| `POST` | `/tables/{table}/rows` | create | Create one or many rows |
| `PATCH` | `/tables/{table}/rows/{id}` | update | Update a row |
| `DELETE` | `/tables/{table}/rows/{id}` | delete | Delete a row |
| `POST` | `/tables/{table}/rows/bulk-delete` | delete | Delete many rows by id |

`{table}` is the table **slug** (lowercase, e.g. `orders`), and `{id}` is the numeric row id. A request whose key lacks the listed scope returns `403`.

---

## 4. Endpoint reference

### List tables — `GET /tables`

```bash
curl -H "Authorization: Bearer $KEY" \
  https://your-site.com/wp-json/flowmattic/v1/tables-api/tables
```

```json
{
  "tables": [
    {
      "name": "orders",
      "displayName": "Orders",
      "fields": [
        { "name": "email", "displayName": "Email", "type": "email", "required": true, "indexed": false, "default": null },
        { "name": "order_id", "displayName": "Order ID", "type": "text", "required": false, "indexed": false, "default": null },
        { "name": "order_total", "displayName": "Order Total", "type": "text", "required": false, "indexed": false, "default": null }
      ],
      "records": 0
    }
  ]
}
```

### Get a table's schema — `GET /tables/{table}`

```bash
curl -H "Authorization: Bearer $KEY" \
  https://your-site.com/wp-json/flowmattic/v1/tables-api/tables/orders
```

```json
{
  "name": "orders",
  "displayName": "Orders",
  "fields": [
    { "name": "email", "type": "email", "required": true },
    { "name": "order_id", "type": "text", "required": false },
    { "name": "order_total", "type": "text", "required": false },
    { "name": "items", "type": "long_text", "required": false },
    { "name": "order_date", "type": "datetime", "required": false }
  ],
  "records": 0
}
```

### List rows — `GET /tables/{table}/rows`

```bash
curl -H "Authorization: Bearer $KEY" \
  "https://your-site.com/wp-json/flowmattic/v1/tables-api/tables/orders/rows?limit=2&sort=id&order=asc"
```

```json
{
  "rows": [
    { "id": 1, "email": "ada@example.com", "order_id": "ORD-1001", "order_total": "149.00" },
    { "id": 2, "email": "grace@example.com", "order_id": "ORD-1002", "order_total": "59.00" }
  ],
  "next_cursor": "eyJ2IjpudWxsLCJpZCI6Mn0=",
  "meta": { "rows_read": 2 }
}
```

See [§5](#5-filtering-sorting-and-pagination) for query options.

### Get one row — `GET /tables/{table}/rows/{id}`

```bash
curl -H "Authorization: Bearer $KEY" \
  https://your-site.com/wp-json/flowmattic/v1/tables-api/tables/orders/rows/1
```

```json
{
  "rows": [
    { "id": 1, "email": "ada@example.com", "order_id": "ORD-1001", "order_total": "149.00",
      "created_at": "2026-07-22T12:39:56.801Z", "updated_at": "2026-07-22T12:39:56.801Z" }
  ],
  "meta": { "rows_read": 1 }
}
```

### Create rows — `POST /tables/{table}/rows`

Send a single object, or `{ "rows": [ … ] }` to insert many at once (up to 1000). Required fields must be present. Returns **201**.

```bash
curl -X POST -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \
  https://your-site.com/wp-json/flowmattic/v1/tables-api/tables/orders/rows \
  -d '{"email":"ada@example.com","order_id":"ORD-1001","order_total":"149.00"}'
```

```json
{ "ids": [1], "count": 1, "rows": [ { "id": 1 } ] }
```

### Update a row — `PATCH /tables/{table}/rows/{id}`

Send only the fields you want to change.

```bash
curl -X PATCH -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \
  https://your-site.com/wp-json/flowmattic/v1/tables-api/tables/orders/rows/1 \
  -d '{"order_total":"199.00"}'
```

```json
{ "id": 1, "updated": true }
```

### Delete a row — `DELETE /tables/{table}/rows/{id}`

```bash
curl -X DELETE -H "Authorization: Bearer $KEY" \
  https://your-site.com/wp-json/flowmattic/v1/tables-api/tables/orders/rows/1
```

```json
{ "id": 1, "deleted": true }
```

### Delete many — `POST /tables/{table}/rows/bulk-delete`

```bash
curl -X POST -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \
  https://your-site.com/wp-json/flowmattic/v1/tables-api/tables/orders/rows/bulk-delete \
  -d '{"ids":[2,3]}'
```

```json
{ "deleted": 2 }
```

---

## 5. Filtering, sorting, and pagination

`GET /tables/{table}/rows` accepts these query parameters:

| Parameter | Description |
| --- | --- |
| `limit` | Rows to return (default gateway page size, **max 500**). |
| `cursor` | Pass the `next_cursor` from the previous response to fetch the next page. |
| `sort` | Field to sort by (e.g. `sort=id`). |
| `order` | `asc` or `desc`. |
| `{field}` | Exact‑match filter, e.g. `email=ada@example.com`. |
| `{field}__gte` / `{field}__lte` | Range filters, e.g. `amount__gte=4000`. |
| `{field}__like` | Partial match, e.g. `order_id__like=ORD-10`. |

**Examples**

```
GET /tables/orders/rows?amount__gte=4000
GET /tables/orders/rows?order_id__like=ORD-10&sort=order_date&order=desc
```

**Pagination.** Each list response includes a `next_cursor`. When it is non‑null, pass it back as `?cursor=…` to get the next page; a `null` cursor means you've reached the end.

```bash
# page 1
curl -H "Authorization: Bearer $KEY" ".../tables/orders/rows?limit=100"
# page 2 — feed the returned next_cursor
curl -H "Authorization: Bearer $KEY" ".../tables/orders/rows?limit=100&cursor=eyJ2Ijp…"
```

---

## 6. Errors

Errors return a JSON body and a matching HTTP status.

| Status | Code | Meaning |
| --- | --- | --- |
| `400` | `invalid_request` | Bad payload — missing required field, unknown field, or invalid query. |
| `401` | `fm_missing_key` / `fm_invalid_key` | No key sent, or the key is invalid/revoked. |
| `403` | `fm_forbidden_scope` | The key isn't scoped for that operation or table. |
| `404` | `not_found` / `rest_no_route` | Table doesn't exist, or the route/id is wrong. |
| `429` | `fm_rate_limited` | Too many requests — slow down (see §7). |
| `503` | `fm_tables_not_connected` | FlowMattic Tables isn't connected on this site. |
| `502` | — | The managed service returned an unexpected error. |

**Examples**

```json
// 401 — no key
{ "code": "fm_missing_key", "message": "Missing API key.", "data": { "status": 401 } }

// 403 — read-only key attempting a write
{ "code": "fm_forbidden_scope", "message": "This key is not scoped for that operation or table.", "data": { "status": 403 } }

// 400 — missing required field
{ "error": "invalid_request", "message": "Field \"email\" is required." }

// 404 — unknown table
{ "error": "not_found", "message": "Table \"no_such_table\" does not exist." }
```

---

## 7. Rate limits

Each key is limited to **120 requests per minute** (counted per key + IP). Over the limit returns `429`. Site owners can adjust the limit with the `flowmattic_tables_api_rate_limit` filter (set to `0` to disable).

---

## 8. Usage and metering

API calls count toward your FlowMattic Tables plan just like dashboard and workflow activity:

- **Reads** — every `GET` reads rows from your table.
- **Writes** — `POST`, `PATCH`, and `DELETE` each meter as writes.

The total number of API calls is shown on the **API Keys** screen (this month and all‑time), so reads and writes made over REST appear in your normal Tables usage — there's no separate quota.

---

## 9. Request logging (optional)

FlowMattic can keep an on‑site log of every API request for auditing. It's **off by default**. Turn on **Log REST API requests** on the API Keys screen; an **API Logs** button then appears in the FlowMattic Tables header.

![FlowMattic Tables API request log](https://assets.infidesk.support/products/flowmattic/kb-images/tables-api/api-logs.png)

Each entry records the time, method, route, table, response status, duration, and caller IP. Logs are stored on your own site and automatically pruned after **30 days**. Turn logging off to stop capturing and hide the viewer; use **Clear logs** to wipe existing entries.

---

## 10. Quick examples

**cURL**

```bash
KEY="fmtk_your_key_here"
BASE="https://your-site.com/wp-json/flowmattic/v1/tables-api"

# create a row
curl -X POST "$BASE/tables/orders/rows" \
  -H "Authorization: Bearer $KEY" -H "Content-Type: application/json" \
  -d '{"email":"ada@example.com","order_id":"ORD-1001","order_total":"149.00"}'
```

**JavaScript (fetch)**

```js
const BASE = "https://your-site.com/wp-json/flowmattic/v1/tables-api";
const KEY  = "fmtk_your_key_here";

async function createOrder(order) {
  const res = await fetch(`${BASE}/tables/orders/rows`, {
    method: "POST",
    headers: {
      "Authorization": `Bearer ${KEY}`,
      "Content-Type": "application/json",
    },
    body: JSON.stringify(order),
  });
  if (!res.ok) throw new Error(`Tables API ${res.status}`);
  return res.json();
}

await createOrder({ email: "ada@example.com", order_id: "ORD-1001", order_total: "149.00" });
```

**PHP**

```php
$base = 'https://your-site.com/wp-json/flowmattic/v1/tables-api';
$key  = 'fmtk_your_key_here';

$ch = curl_init("$base/tables/orders/rows");
curl_setopt_array($ch, [
    CURLOPT_POST           => true,
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER     => [
        "Authorization: Bearer $key",
        'Content-Type: application/json',
    ],
    CURLOPT_POSTFIELDS     => json_encode([
        'email'       => 'ada@example.com',
        'order_id'    => 'ORD-1001',
        'order_total' => '149.00',
    ]),
]);
$response = json_decode(curl_exec($ch), true);
curl_close($ch);
```

---

## 11. Security best practices

- **Scope to the minimum.** Give a key only the operations and tables it needs — a reporting integration should be **read‑only**.
- **Keep keys secret.** Never ship a key in front‑end JavaScript or a mobile app binary where users can extract it. Call the API from a server you control.
- **Rotate and revoke.** Keys are shown once and stored hashed; if one is exposed, revoke it and issue a new one. Revocation is immediate.
- **Use HTTPS.** Always call the API over `https://` so the Bearer token isn't sent in the clear.
- **Audit with logging.** Enable request logging when you want a record of who called what and when.

---

**Related:** [Getting started with FlowMattic Tables](https://flowmattic.com/integration/flowmattic-tables/) · [Using Tables in workflows](https://flowmattic.com/integration/flowmattic-tables/)

---

# FlowMattic Workflow Sharing - Complete Guide

Source: https://support.flowmattic.com/kb/article/104/flowmattic-workflow-sharing---complete-guide

## Overview

FlowMattic's Workflow Sharing feature allows you to share your automation workflows with others using a simple URL. This makes it easy to collaborate with team members, share templates with the community, or transfer workflows between different FlowMattic installations.

## What is Workflow Sharing?

Workflow Sharing is a feature that lets you:
- **Export** your workflows as shareable URLs
- **Import** workflows from URLs shared by others
- **Collaborate** with team members by sharing automation templates
- **Save time** by reusing proven workflows

Think of it like sharing a Google Doc link - anyone with the link can access and import your workflow into their own FlowMattic installation.

## How to Share a Workflow

### Method 1: From the Workflows List

1. Navigate to **FlowMattic → Workflows** in your WordPress admin panel
2. Find the workflow you want to share
3. Click the **three-dot menu** (⋮) next to the workflow name
4. Select **"Share Workflow"** from the dropdown menu

![Workflows ‹ FlowMattic — Share from workflow listing page.png](/storage/kb-images/8ea1245910-inline.png)

5. A modal window will appear with your unique share URL
6. Click the **"Copy"** button to copy the URL to your clipboard

![Workflows ‹ FlowMattic — WordPress 2025-09-09 at 3.37.28 PM.png](/storage/kb-images/98b0b03189-inline.png)

7. Share this URL with anyone who needs to import your workflow

### Method 2: From the Workflow Builder

1. Open your workflow in the **Workflow Builder**
2. Look for the **Share** icon in the top-right corner (next to the Help icon)

![Workflow Builder ‹ FlowMattic — workflow share button.png](/storage/kb-images/31d2ec1077-inline.png)

3. Click the Share icon
4. Copy the generated URL from the modal window

## How to Import a Shared Workflow

### Step 1: Access the Import Feature

1. Go to **FlowMattic → Workflows**
2. Click the **"Import Workflow"** button at the top of the page

![Workflows ‹ FlowMattic — WordPress 2025-09-09 at 3.39.40 PM.png](/storage/kb-images/53abae808e-inline.png)

### Step 2: Choose Import Method

You'll see two options in the import modal:

![Workflows ‹ FlowMattic — import workflow.png](/storage/kb-images/da8cdd3a06-inline.png)

#### Option A: Import from File
- Click or drag-and-drop a JSON file into the upload area
- This method is for workflow files exported from FlowMattic

#### Option B: Import from Shared Link
- Paste the shared URL into the input field
- The URL should start with your site domain followed by `/wp-json/flowmattic/v1/workflow-share/`

### Step 3: Complete the Import

1. After entering a valid URL or uploading a file, the **"Import Workflow"** button will become active
2. Click **"Import Workflow"**
3. Wait for the import to complete (you'll see a "Importing..." message)
4. Once successful, you'll see a success message

![Workflows ‹ FlowMattic — import successful.png](/storage/kb-images/26f673960f-inline.png)

### Step 4: Configure Your Imported Workflow

After importing, the workflow will:
- Be saved as a **Draft** (inactive) so you can review it first
- Have **"_SHARED"** added to its name for easy identification
- Require you to configure any app connections and credentials

![Workflows ‹ FlowMattic — WordPress 2025-09-09 at 3.45.50 PM.png](/storage/kb-images/66624182ff-inline.png)

## What Gets Shared

### ✅ What IS Included:
- **Workflow structure** - All steps and their order
- **Step configurations** - Settings for each action and trigger
- **Conditions and filters** - Logic rules and conditional paths
- **Field mappings** - How data flows between steps
- **Basic workflow settings** - Name, description, etc.

### ❌ What is NOT Included:
- **Captured data** - No test data or actual records
- **API credentials** - No passwords or API keys
- **Personal information** - No email addresses or user data
- **Webhook URLs** - New unique URLs are generated
- **Execution history** - No logs or previous run data
- **Active status** - Workflow imports as draft/inactive

## Security & Privacy

### How We Keep Your Data Safe

1. **No Sensitive Data**: Share URLs never contain passwords, API keys, or personal information. Any user importing the workflow will have to connect their APIs in Connect first and then update the workflow with appropriate Connect account in order to make it work.
2. **Unique IDs**: Each share URL uses a unique encoded identifier
3. **Read-Only Access**: Share URLs only allow reading, not modifying your original workflow
4. **Draft Mode**: Imported workflows start inactive, requiring manual review
5. **New Webhook URLs**: Each import generates fresh webhook URLs to prevent conflicts

### What Recipients Need to Know

- You'll need to **reconnect all apps** with your own credentials
- **Review all steps** before activating the workflow
- **Test thoroughly** with your own data before going live
- **Customize** the workflow to match your specific needs

## Frequently Asked Questions

### General Questions

**Q: Can anyone with the URL access my workflow?**
A: Yes, anyone with the URL can view and import the workflow structure. However, they cannot access your data, credentials, or modify your original workflow.

**Q: What happens if I delete my shared workflow?**
A: If you delete the original workflow, the share URL will stop working. Anyone who already imported it will keep their copy, but new imports will fail with an "Invalid workflow" error.

**Q: Can I revoke a share URL?**
A: Currently, share URLs remain active as long as the workflow exists. To revoke access, you would need to delete the workflow or create a copy with a new share URL.

**Q: Will changes to my workflow update the shared version?**
A: Yes, the share URL always provides the current version of your workflow. Recipients who import after you make changes will get the updated version.

**Q: What happens if someone shares my shared workflow?**
A: They can share the URL with others, who will import from your original workflow. Each import creates an independent copy that won't affect your workflow.

### Security Questions

**Q: Is it safe to share workflows that connect to sensitive systems?**
A: Yes, because no credentials or sensitive data are included. Recipients must provide their own API keys and passwords.

**Q: Can someone hack my system through a shared workflow?**
A: No, share URLs are read-only and don't provide any access to your WordPress installation or FlowMattic account.

**Q: What if I accidentally included sensitive information in a step description?**
A: Review your workflow before sharing. Step descriptions and names are included in shares, so avoid putting passwords or sensitive data in these fields.

### Technical Questions

**Q: Why does my imported workflow show as "Draft"?**
A: This is a safety feature. All imported workflows start as drafts so you can review and configure them before activation.

**Q: Why are my webhook URLs different after import?**
A: FlowMattic generates new unique webhook URLs for each import to prevent conflicts and maintain security.

**Q: Can I import a workflow from a different FlowMattic version?**
A: Yes, but compatibility depends on the features used. Workflows using newer features may not work correctly on older FlowMattic versions.

**Q: What's the maximum workflow size I can share?**
A: There's no specific size limit, but extremely complex workflows with hundreds of steps may take longer to import.

**Q: Can I share workflows between different WordPress sites?**
A: Yes! That's one of the main benefits. You can share workflows between any WordPress sites running FlowMattic.

## Troubleshooting

### Common Issues and Solutions

**"Invalid workflow" error when importing**
- **Cause**: The workflow may have been deleted or the URL is incorrect
- **Solution**: Verify the URL with the person who shared it

**"Failed to import workflow" error**
- **Cause**: Network timeout or server issues
- **Solution**: 
  - Try again after a few moments
  - Check your internet connection
  - Contact support if the issue persists

**"Security check failed" error**
- **Cause**: Session timeout or browser security settings
- **Solution**: 
  - Refresh the page and try again
  - Clear browser cache and cookies
  - Try a different browser

**Imported workflow isn't working**
- **Cause**: Missing app connections or incompatible settings
- **Solution**:
  - Check all app connections are configured
  - Verify API credentials are entered
  - Test each step individually
  - Check for any error messages in step configurations

**Can't see the Share button**
- **Cause**: Permissions issue or outdated FlowMattic version
- **Solution**:
  - Ensure you have admin permissions
  - Update FlowMattic to the latest version
  - Clear browser cache

## Best Practices

### When Sharing Workflows

1. **Clean up test data**: Remove any test values from fields before sharing
2. **Add descriptions**: Include clear descriptions for complex steps
3. **Document requirements**: Note which apps and plans are needed
4. **Test first**: Ensure the workflow works correctly before sharing
5. **Use generic values**: Replace specific values with placeholders like `{YOUR_API_KEY}`. You can make use of the Variables feature of FlowMattic for this, which also allows you to use the same API key in multiple places in your workflow with variables.

### When Importing Workflows

1. **Review before activating**: Always check all steps before turning on the workflow
2. **Test with sample data**: Run tests before using with real data
3. **Backup existing workflows**: If replacing a workflow, save a backup first
4. **Check compatibility**: Ensure you have required apps and features
5. **Customize for your needs**: Adapt the workflow to match your specific requirements

### For Teams

1. **Create a workflow library**: Share common workflows with your team
2. **Version control**: Include version numbers in workflow names
3. **Documentation**: Create a shared document listing all shared workflows
4. **Standardize naming**: Use consistent naming conventions
5. **Regular updates**: Keep shared templates current with best practices

## Advanced Tips

### Creating Workflow Templates

If you frequently share workflows, consider:
- Creating "template" versions with placeholder values
- Adding detailed step descriptions explaining customization options
- Including a "README" step at the beginning with setup instructions
- Using consistent naming like "TEMPLATE: [Workflow Purpose]"

### Managing Multiple Versions

When maintaining workflows across multiple sites:
- Include version numbers in workflow names (e.g., "Customer Onboarding v2.1")
- Document changes in workflow descriptions
- Keep a master copy on a development site
- Test updates before sharing new versions

## Need More Help?

If you encounter issues not covered in this guide:

1. **Check FlowMattic Documentation**: Visit the official docs at [support.flowmattic.com/kb](https://support.flowmattic.com/kb)
2. **Community Forum**: Ask questions in the FlowMattic community
3. **Support Ticket**: You can submit a support ticket

---

*FlowMattic Version: 5.3.0+*

---

# FlowMattic WP-CLI: Integrations

Source: https://support.flowmattic.com/kb/article/223/flowmattic-wp-cli-integrations

Manage FlowMattic's installed integration apps and their updates from the terminal with `wp flowmattic integrations` — useful for auditing what needs updating and applying updates during a deploy without opening the admin.

> **Requirements:** [WP-CLI](https://wp-cli.org/) installed and FlowMattic active.

---

## `list` — list integrations and update status

```
wp flowmattic integrations list [--updates-only] [--format=<table|json|csv>]
```

| Option | Description |
| --- | --- |
| `--updates-only` | Show only integrations that have an update available. |
| `--format` | `table` (default), `json`, `csv`. |

```
$ wp flowmattic integrations list --updates-only
slug         name         installed   available   status
lancepilot   Lancepilot   1.1.0       1.0.0       Update available
mautic       Mautic       1.1.0       1.1.1       Update available
youtube      YouTube      2.0.0       1.0         Update available
dukaan_app   Dukaan App   2.0         1.0         Update available
```

When everything is current: `Success: All integrations are up to date.`

> This command supports `table`, `json`, and `csv` only — not `count` or `ids`.

---

## `update` — update integrations

```
wp flowmattic integrations update [<slug>...] [--all]
```

Pass one or more integration **slugs** (from the `list` output), or `--all` to update everything that has an update available.

```
# update specific apps
$ wp flowmattic integrations update airtable slack
Updating: airtable, slack
Success: airtable updated from v1.0 to v1.1.
Success: slack updated from v2.0 to v2.1.

Summary: 2 updated, 0 failed, 0 skipped.
Success: Done.
```

```
# update everything with an available update
wp flowmattic integrations update --all
```

Each app reports its own line: updated (`Success: <slug> updated from vX to vY.`), skipped (`Skipped <slug>: <reason>`), or failed (`Failed <slug>: <reason>`), followed by a summary. If you pass neither slugs nor `--all`, you'll get: `Error: Please specify integration slug(s) or use --all to update all.`

---

## Automation recipe — update integrations after a release

```
# audit first
wp flowmattic integrations list --updates-only
# then apply
wp flowmattic integrations update --all
```

---

## Notes

- Slugs come straight from the `list` output's first column (e.g. `airtable`, `lancepilot`).
- `update` writes to the site — run it where you'd normally apply plugin/integration updates.
- Run `wp flowmattic integrations <command> --help` for the full synopsis on your install.

---

**Related WP-CLI guides:** [Workflows](https://support.flowmattic.com/portal/flowmattic/kb/article/221/flowmattic-wp-cli-workflows) · [Task History](https://support.flowmattic.com/portal/flowmattic/kb/article/222/flowmattic-wp-cli-tasks) · [Patches](https://support.flowmattic.com/portal/flowmattic/kb/article/224/flowmattic-wp-cli-patches) · [Settings (Core Modules)](https://support.flowmattic.com/portal/flowmattic/kb/article/226/flowmattic-wp-cli-settings)

---

# FlowMattic WP-CLI: Patches

Source: https://support.flowmattic.com/kb/article/224/flowmattic-wp-cli-patches

FlowMattic can ship targeted patches for the installed version — small fixes delivered between full releases. `wp flowmattic patches` lets you review and apply them from the terminal, so you can roll them out during a deploy without opening the admin patcher.

> **Requirements:** [WP-CLI](https://wp-cli.org/) installed and FlowMattic active.

---

## `status` — one-line summary

```
wp flowmattic patches status
```

```
$ wp flowmattic patches status
FlowMattic 7.0.1 — 0 patches total: 0 applied, 0 pending.
Success: Everything is up to date.
```

When patches are waiting, it ends with a hint instead: `Run \`wp flowmattic patches apply\` to install the pending patches.`

---

## `list` — list patches

```
wp flowmattic patches list [--pending] [--applied] [--format=<format>]
```

| Option | Description |
| --- | --- |
| `--pending` | Only patches not yet applied. |
| `--applied` | Only patches already applied. |
| `--format` | `table` (default), `json`, `csv`, `yaml`, `count`, `ids`. |

Columns are `id`, `version`, `title`, and `status` (`applied` | `pending`).

```
$ wp flowmattic patches list --pending
id   version   title                                    status
1    7.0.1     Harden webhook signature verification    pending
2    7.0.1     Fix timezone drift in scheduled runs     pending
```

If nothing matches the filter: `No patches matched.`

---

## `apply` — apply pending patches

Applies every pending patch, in order. Use `--dry-run` to preview, and `--yes` to skip the confirmation. **Plugin files are overwritten**, so review with a dry run first on production.

```
wp flowmattic patches apply [--yes] [--dry-run]
```

```
# preview — writes nothing
$ wp flowmattic patches apply --dry-run
2 pending patches for FlowMattic 7.0.1:
  #1  Harden webhook signature verification
  #2  Fix timezone drift in scheduled runs
(dry-run) No files written.
```

```
# apply for real, unattended (e.g. after a deploy)
$ wp flowmattic patches apply --yes
✓ Patch #1 applied — Harden webhook signature verification
✓ Patch #2 applied — Fix timezone drift in scheduled runs
Success: Applied 2 patches.
```

When there's nothing to do: `Success: No pending patches — nothing to do.` If a patch fails, the run stops and reports which one: `Error: Patch #N (<title>) failed: <reason>. Aborting remaining patches.`

---

## Automation recipe — apply patches after pulling a release

```
wp flowmattic patches apply --yes
```

Pair it with a dry run in CI to see what a deploy would change before it runs unattended.

---

## Notes

- `apply` **overwrites plugin files** — always `--dry-run` first when in doubt, and apply in order (the command enforces it and aborts on the first failure).
- Without `--yes`, `apply` prompts: *Apply N patches in this order? Plugin files will be overwritten.*
- Run `wp flowmattic patches <command> --help` for the full synopsis on your install.

---

**Related WP-CLI guides:** [Workflows](https://support.flowmattic.com/portal/flowmattic/kb/article/221/flowmattic-wp-cli-workflows) · [Task History](https://support.flowmattic.com/portal/flowmattic/kb/article/222/flowmattic-wp-cli-tasks) · [Integrations](https://support.flowmattic.com/portal/flowmattic/kb/article/223/flowmattic-wp-cli-integrations) · [Settings (Core Modules)](https://support.flowmattic.com/portal/flowmattic/kb/article/226/flowmattic-wp-cli-settings)

---

# FlowMattic WP-CLI: Settings (Core Modules)

Source: https://support.flowmattic.com/kb/article/226/flowmattic-wp-cli-settings

FlowMattic's **Core Modules** — Forms, Bookings, Tables, and the rest — can each be turned on or off from **Settings → Core Modules**. `wp flowmattic settings` does the same from the terminal, so you can trim an install down to just the modules you use, or toggle a module during maintenance, from a deploy script or SSH.

Turning a module **off** fully removes it: its admin menu and pages, its REST and AJAX endpoints, and its public pages all stop responding for everyone until it's re-enabled.

> **Requirements:** [WP-CLI](https://wp-cli.org/) installed and FlowMattic active.

---

## The modules

| Slug | Module |
| --- | --- |
| `forms` | Forms |
| `bookings` | Bookings |
| `tables` | WP Tables |
| `databases` | FlowMattic Tables |
| `email-templates` | Email Templates |
| `pdf-templates` | PDF Templates |
| `image-templates` | Image Templates |
| `ai-assistants` | AI Assistants |
| `mcp-server` | MCP Server |

Use the slug (left column) with the commands below.

---

## `modules` — list modules and status

```
wp flowmattic settings modules [--format=<format>]
```

`--format`: `table` (default), `json`, `csv`, `yaml`, `count`, `ids`.

```
$ wp flowmattic settings modules
module            label               status
forms             Forms               enabled
bookings          Bookings            enabled
tables            WP Tables           enabled
databases         FlowMattic Tables   enabled
email-templates   Email Templates     enabled
pdf-templates     PDF Templates       enabled
image-templates   Image Templates     enabled
ai-assistants     AI Assistants       enabled
mcp-server        MCP Server          enabled
```

---

## `enable` — enable modules

```
wp flowmattic settings enable <module>...
```

Pass one or more slugs.

```
$ wp flowmattic settings enable bookings
Success: bookings enabled.

$ wp flowmattic settings enable pdf-templates image-templates
Success: pdf-templates, image-templates enabled.
```

Enabling something already on is a safe no-op: `Success: No change — bookings already enabled.`

---

## `disable` — disable modules

```
wp flowmattic settings disable <module>... [--yes]
```

Because a disabled module disappears completely (menu, admin pages, REST + AJAX, public pages), `disable` asks to confirm — pass `--yes` to skip the prompt in scripts.

```
$ wp flowmattic settings disable image-templates
Disable image-templates? Its menu, admin pages, REST + AJAX endpoints and public pages will stop responding until re-enabled. [y/n] y
Success: image-templates disabled.

$ wp flowmattic settings disable forms bookings --yes
Success: forms, bookings disabled.
```

An unknown slug stops the command with a hint: `Error: Unknown module: reports. Run \`wp flowmattic settings modules\` to list valid slugs.`

---

## `status` — one module's status

Prints just `enabled` or `disabled` — handy for shell conditionals.

```
$ wp flowmattic settings status bookings
enabled
```

```
if [ "$(wp flowmattic settings status ai-assistants)" = "disabled" ]; then
  wp flowmattic settings enable ai-assistants
fi
```

---

## Automation recipe — a lean, purpose-built install

Provision a site that only needs Forms and Bookings, disabling the rest in one shot:

```
wp flowmattic settings disable tables databases email-templates pdf-templates image-templates ai-assistants mcp-server --yes
```

Re-enable everything just as easily:

```
for m in $(wp flowmattic settings modules --format=ids); do wp flowmattic settings enable "$m"; done
```

---

## Notes

- Changes take effect on the **next request** — the command writes the same setting the admin **Save Modules** button does, so state is identical either way.
- `disable` is guarded by a confirmation prompt; pass `--yes` to run unattended.
- Toggling modules never deletes data — a disabled module's data stays put and returns when you re-enable it.
- Run `wp flowmattic settings <command> --help` for the full synopsis on your install.

---

**Related WP-CLI guides:** [Workflows](https://support.flowmattic.com/portal/flowmattic/kb/article/221/flowmattic-wp-cli-workflows) · [Task History](https://support.flowmattic.com/portal/flowmattic/kb/article/222/flowmattic-wp-cli-tasks) · [Integrations](https://support.flowmattic.com/portal/flowmattic/kb/article/223/flowmattic-wp-cli-integrations) · [Patches](https://support.flowmattic.com/portal/flowmattic/kb/article/224/flowmattic-wp-cli-patches)

---

# FlowMattic WP-CLI: Task History

Source: https://support.flowmattic.com/kb/article/222/flowmattic-wp-cli-tasks

Every FlowMattic workflow run is recorded in the `flowmattic_tasks` table. On busy sites that grows quickly, so `wp flowmattic tasks` gives you a terminal way to measure it, inspect recent runs, and keep it trimmed — the purge command is the one to schedule.

> **Requirements:** [WP-CLI](https://wp-cli.org/) installed and FlowMattic active. A **workflow ID** is the short string from the admin URL or `wp flowmattic workflows list` (e.g. `hitltest01`).

---

## `count` — count task-history rows

```
wp flowmattic tasks count [--workflow=<workflow_id>]
```

Without `--workflow`, returns the grand total across all workflows; with it, the count for that one workflow.

```
$ wp flowmattic tasks count
56269

$ wp flowmattic tasks count --workflow=hitltest01
4
```

---

## `list` — list a workflow's runs

```
wp flowmattic tasks list --workflow=<workflow_id> [--limit=<n>] [--format=<format>]
```

| Option | Description |
| --- | --- |
| `--workflow` | **Required.** The workflow to list executions for. |
| `--limit` | Max rows (default **25**). |
| `--format` | `table` (default), `json`, `csv`, `yaml`, `ids`, `count`. |

```
$ wp flowmattic tasks list --workflow=hitltest01 --limit=3
id       task_id                  task_time
113243   sixSiwVR2i_412622513     2026-07-14 00:05:58
113208   wgThymJARG_3131345393    2026-07-13 23:32:17
113206   FM70iX5ssL_3138674417    2026-07-13 23:31:26

$ wp flowmattic tasks list --workflow=hitltest01 --limit=2 --format=json
[{"id":"113243","task_id":"sixSiwVR2i_412622513","task_time":"2026-07-14 00:05:58"},{"id":"113208","task_id":"wgThymJARG_3131345393","task_time":"2026-07-13 23:32:17"}]
```

Omitting `--workflow` returns an error: `Error: --workflow=<workflow_id> is required.`

---

## `clear` — wipe one workflow's history

Deletes all task rows for a workflow (the workflow itself is left intact). Mirrors the admin **Empty task history** action, and prompts unless `--yes` is passed.

```
wp flowmattic tasks clear --workflow=<workflow_id> [--yes]
```

```
$ wp flowmattic tasks clear --workflow=hitltest01
About to delete 4 task history rows for workflow hitltest01.
Clear task history? [y/n] y
Success: Cleared 4 task history rows.
```

If there's nothing to remove: `Success: No task history to clear — nothing to do.`

---

## `purge` — delete old history across all workflows

Deletes task rows older than N days everywhere. This is the command to schedule so the table never grows without bound.

```
wp flowmattic tasks purge --older-than=<days> [--yes]
```

```
$ wp flowmattic tasks purge --older-than=30
About to delete task history older than 30 days. Current total: 56269 rows.
Purge old task history? [y/n] y
Success: Purge complete. Total dropped from 56269 to 41230 rows (~15039 removed).
```

If nothing is old enough: `Success: Purge complete. Total: 56269 rows (no rows older than 30 days).`
`--older-than` must be a positive integer, or you'll get: `Error: --older-than must be a positive integer (number of days).`

---

## Automation recipe — nightly cleanup

Schedule this (system cron or a wp-cron wrapper) to keep the last 30 days and nothing more. `--yes` skips the prompt so it runs unattended:

```
wp flowmattic tasks purge --older-than=30 --yes
```

---

## Notes

- `clear` and `purge` are **destructive** — pass `--yes` to run without the confirmation prompt in cron/CI.
- `clear` targets one workflow; `purge` spans **all** workflows by age.
- Run `wp flowmattic tasks <command> --help` for the full synopsis on your install.

---

**Related WP-CLI guides:** [Workflows](https://support.flowmattic.com/portal/flowmattic/kb/article/221/flowmattic-wp-cli-workflows) · [Integrations](https://support.flowmattic.com/portal/flowmattic/kb/article/223/flowmattic-wp-cli-integrations) · [Patches](https://support.flowmattic.com/portal/flowmattic/kb/article/224/flowmattic-wp-cli-patches) · [Settings (Core Modules)](https://support.flowmattic.com/portal/flowmattic/kb/article/226/flowmattic-wp-cli-settings)

---

# FlowMattic WP-CLI: Workflows

Source: https://support.flowmattic.com/kb/article/221/flowmattic-wp-cli-workflows

Manage your FlowMattic workflows from the terminal with `wp flowmattic workflows`. Workflows live in FlowMattic's own `flowmattic_workflows` table (not as WordPress posts), so these commands are the CLI way to list, inspect, and toggle them — handy for deploys, staging syncs, and automation.

> **Requirements:** [WP-CLI](https://wp-cli.org/) installed and FlowMattic active. A **workflow ID** is the short alphanumeric string shown in the admin URL and in `list` output (e.g. `hitltest01`) — not a numeric post ID.

---

## `list` — list workflows

```
wp flowmattic workflows list [--status=<on|off>] [--limit=<n>] [--format=<format>]
```

| Option | Description |
| --- | --- |
| `--status` | Filter to `on` or `off`. |
| `--limit` | Max rows to return (default **100**). Caps every listing format. |
| `--format` | `table` (default), `json`, `csv`, `yaml`, `ids`, `count`. |

```
$ wp flowmattic workflows list --limit=5
workflow_id   name                          status   trigger    actions
aqagnfd6ts    MCP demo — webhook to email   off      webhook    1
oiWwMKX9KG    VIP Order Notification…       off      webhook    8
hitltest01    HITL Test Workflow            on       webhook    2
AWFGdAHpjU    Clean Name Test               on       bookings   1
Yj2eu1KNcb    Testing new workflow…         off      rss_feed   2
```

`--format=count` returns the **true total** number of matches (it is not capped by `--limit`), which makes it perfect for quick tallies:

```
$ wp flowmattic workflows list --format=count
290
$ wp flowmattic workflows list --status=on --format=count
116
```

`--format=ids` prints a space-separated list of workflow IDs (capped by `--limit`) — ideal for piping:

```
$ wp flowmattic workflows list --status=on --limit=3 --format=ids
hitltest01 AWFGdAHpjU pW6Vn84P3m
```

---

## `get` — inspect one workflow

```
wp flowmattic workflows get <workflow_id> [--format=<table|json|yaml>]
```

Adds `owner` and `task_count` to the row.

```
$ wp flowmattic workflows get hitltest01
workflow_id   name                 status   trigger   actions   owner               task_count
hitltest01    HITL Test Workflow   on       webhook   2         infiwebs@gmail.com  4

$ wp flowmattic workflows get hitltest01 --format=json
[{"workflow_id":"hitltest01","name":"HITL Test Workflow","status":"on","trigger":"webhook","actions":2,"owner":"infiwebs@gmail.com","task_count":4}]
```

---

## `status` — print on/off

Prints just `on` or `off` on stdout — built for shell conditionals.

```
$ wp flowmattic workflows status hitltest01
on
```

```
if [ "$(wp flowmattic workflows status hitltest01)" = "on" ]; then
  echo "Workflow is live"
fi
```

---

## `enable` / `disable` / `toggle`

Change a workflow's status through the same code path as the admin toggle.

```
wp flowmattic workflows enable  <workflow_id>
wp flowmattic workflows disable <workflow_id>
wp flowmattic workflows toggle  <workflow_id>
```

```
$ wp flowmattic workflows enable aqagnfd6ts
Success: Workflow aqagnfd6ts: off → on.

$ wp flowmattic workflows toggle aqagnfd6ts
Success: Workflow aqagnfd6ts: on → off.
```

---

## `delete` — remove a workflow

Deletes the workflow **and all of its task history**. Prompts for confirmation unless `--yes` is passed.

```
wp flowmattic workflows delete <workflow_id> [--yes]
```

```
$ wp flowmattic workflows delete aqagnfd6ts
Workflow: MCP demo — webhook to email (aqagnfd6ts)
This will also delete 12 task history rows.
Delete this workflow and its task history? [y/n] y
Success: Deleted workflow aqagnfd6ts and 12 task rows.
```

---

## Automation recipe — freeze workflows during a deploy

Disable everything that's currently on, deploy, then restore exactly what was on:

```
ON=$(wp flowmattic workflows list --status=on --limit=100000 --format=ids)
for id in $ON; do wp flowmattic workflows disable "$id"; done
# … run your deploy …
for id in $ON; do wp flowmattic workflows enable "$id"; done
```

---

## Notes

- **`--limit` caps every listing format** (table/csv/json/yaml/ids) and defaults to 100 — raise it (e.g. `--limit=100000`) to list everything. `--format=count` ignores the limit and reports the true total.
- **Destructive commands** (`delete`) prompt for confirmation; pass `--yes` to run unattended in cron/CI.
- Run `wp flowmattic workflows <command> --help` for the full synopsis on your install.

---

**Related WP-CLI guides:** [Task History](https://support.flowmattic.com/portal/flowmattic/kb/article/222/flowmattic-wp-cli-tasks) · [Integrations](https://support.flowmattic.com/portal/flowmattic/kb/article/223/flowmattic-wp-cli-integrations) · [Patches](https://support.flowmattic.com/portal/flowmattic/kb/article/224/flowmattic-wp-cli-patches) · [Settings (Core Modules)](https://support.flowmattic.com/portal/flowmattic/kb/article/226/flowmattic-wp-cli-settings)

---

# Fonts, photos, or QR codes are missing from a generated image

Source: https://support.flowmattic.com/kb/article/190/fonts-photos-or-qr-codes-are-missing-from-a-generated-image

## Symptom

The image renders, but part of it is missing or wrong — a photo area is blank, a font looks like a plain default, or a QR code did not appear.

## Cause and fix

### A photo or avatar is blank

Image and avatar elements load their picture from a **Source** — either a literal URL or a `{{token}}` that resolves to a URL. If the Source does not point at a reachable image, the element renders empty.

**Fix:**

- If the Source is a literal URL, open it in a browser to confirm it loads and is publicly reachable. A URL behind a login, on an internal network, or returning an error will not render.
- If the Source is a token, confirm the workflow maps that token to a full, public image URL, and that the URL includes the scheme (`https://`).
- If the element has **Hide if data is empty** enabled and its token resolved empty, the element is intentionally omitted from the render.

![An image element's Element tab with the Source field set to a {{token}}](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-image-template-img-source-field.png)

### The font looks wrong

Image rendering supports the builder's fonts through Cloudflare Browser Rendering. Fonts come from the built-in **Font family** catalog on the **Element** tab; there is no font upload.

**Fix:** select the text element and choose a font from the **Font family** dropdown on the **Element** tab.

### The QR code is missing

A QR Code element renders only when its **URL / Value** is set. If it is a token that the workflow left empty, there is nothing to encode.

**Fix:** confirm the QR Code element's **URL / Value** is set to a token, and that the workflow maps that token to a non-empty URL or string. See *Create QR-coded images*.

### Nothing renders at all

If the whole image fails rather than one element, the cause is usually Cloudflare credentials rather than any single element. See *Images are not rendering or the Image Builder step fails*.

## Prevention

Use the template's **Download Image** test render after any change. It renders with your sample values, so a blank photo, a substituted font, or a missing QR shows up immediately — before the template is used in a live workflow.

---

# Form Builder

Source: https://support.flowmattic.com/kb/article/184/form-builder

Form Builder is FlowMattic's native form designer. You build a form visually, publish it via a link, shortcode, block, or embed, and every submission is stored in WordPress and fires a workflow trigger. It is for users who want a form that connects to workflows without a separate form plugin. If you already use Fluent Forms, Gravity Forms, WPForms, or Forminator, those keep working through their own integrations — this is an alternative, not a replacement.

## How it works

You design a form in the visual editor under **FlowMattic → Forms**, then publish it. Each submission does two things: it stores a response in WordPress, and it fires a **New Form Submission** trigger that any workflow can act on. Because follow-up actions run as workflow steps, you can apply conditions, formatting, and AI processing to a submission.

## The editor

The editor has three areas: the **Form Fields** panel on the left, the canvas in the centre, and a properties panel on the right with **Form**, **Field**, **Design**, **Logic**, and **Settings** tabs. You drag fields onto the canvas, click a field to edit its properties in the **Field** tab, and use the **Form** and **Settings** tabs to control the form's display, header, and access rules.

## Field types

The field library includes Short Text, Long Text, Email, Number, Phone, Multiple Choice, Checkboxes, Dropdown, Multi-select, Date, Time, File Upload, Rating, Opinion Scale, NPS, Signature, Address, Heading, Section, Page Break, Hidden Field, and Calculation. Each field has a **Field key** — that key is what your workflow sees as `{{key}}`.

## Display modes and logic

A form's **Display method** can be **Single page** or **Conversational** (one question per page). Conditional logic rules can show or hide fields based on earlier answers.

## Publishing

Once saved and published, a form is reachable at `/flowmattic-form/{slug}/`. You can also embed it with the `[flowmattic_form id="..."]` shortcode, a Gutenberg block, or a JavaScript embed snippet (inline, popup, slide-in, or bubble).

## Submissions

Responses are stored in WordPress and viewable in the **Responses** viewer, where you can search entries and export them to CSV. A form can also save every submission to a FlowMattic Table.

![The Form Builder editor with a contact form open — the Form Fields panel on the left, the form on the canvas, and the properties panel on the right](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-form-builder-form-editor-overview.png)

---

# Form field values are blank or wrong in my workflow

Source: https://support.flowmattic.com/kb/article/185/form-field-values-are-blank-or-wrong-in-my-workflow

## Symptom

The workflow runs on submission, but a field arrives blank, or the wrong value lands in the wrong place in a later step.

## Cause and fix

### A field key was renamed after the workflow was built

Your workflow maps fields by their **Field key** — a field keyed `email` is `{{email}}`. If you rename a field's key on the form after building the workflow, the old token no longer matches and that value arrives blank.

**Fix:** decide on stable keys before wiring a workflow. If you must rename a key, open the workflow, click **Re-capture Response**, and update every action that mapped the old token.

### The action was mapped before capturing a submission

If you mapped action fields before capturing a real submission, the tokens may point at nothing.

**Fix:** submit a test entry, click **Capture Response**, then re-map the action fields against the freshly captured data using the variable picker.

### Two fields share the same key

If two fields accidentally have the same **Field key**, their values collide and one overwrites the other.

**Fix:** open the form and give every field a unique **Field key**.

### The value is mapped to the wrong token

A value landing in the wrong place usually means the action maps a different token than intended — easy to do when several fields have similar names.

**Fix:** in the action, re-open the variable picker and confirm each field maps to the correct `{{key}}`.

![A workflow action with the variable picker open, showing the captured form fields and their keys](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-form-builder-wf-form-fields.png)

## Prevention

Set clear, unique, stable keys on every field before building any workflow. The key is the contract between the form and the workflow, so keeping keys stable keeps the mappings correct.

---

# FTP / SFTP Integration in FlowMattic

Source: https://support.flowmattic.com/kb/article/129/ftp--sftp-integration-in-flowmattic

Connect your FTP, FTPS, or SFTP server to FlowMattic to upload, download, manage, and monitor files on remote servers — all from within your automated workflows.

---

## Overview

The FTP/SFTP application enables file management operations on remote servers as part of your workflow automation. It supports three protocols:

| Protocol | Port | Security | Description |
|----------|------|----------|-------------|
| **FTP** | 21 | None | Standard File Transfer Protocol |
| **FTPS** | 21 | SSL/TLS | FTP over SSL/TLS encryption |
| **SFTP** | 22 | SSH | SSH File Transfer Protocol (most secure) |

---

## Connection Setup

### Step 1: Add a New Connection

1. Go to **FlowMattic > Connects** in your WordPress dashboard.
2. Click **Add New Connection**.
3. Search for **FTP** and select **FTP / SFTP**.

![FTP Connect.png](/storage/kb-images/137a9a3042-inline.png)

### Step 2: Configure Connection Settings

Fill in the connection fields based on your server's protocol:

| Field | Required | Description |
|-------|----------|-------------|
| **Protocol** | Yes | Select FTP, FTPS, or SFTP. |
| **Host** | Yes | Server hostname or IP address (e.g., `ftp.example.com`). |
| **Port** | No | Defaults to `21` for FTP/FTPS, `22` for SFTP. Leave empty to use defaults. |
| **Username** | Yes | Login username for the server. |
| **Password** | Yes | Login password (or key passphrase for SFTP with SSH key). |
| **Private Key** | No | SSH private key content (SFTP only). Leave empty for password authentication. |
| **Passive Mode** | No | Recommended: **Yes**. Applies to FTP/FTPS only. Not relevant for SFTP. |

![Connects ‹ FlowMattic — WordPress 2026-03-01 at 1.06.54 AM.png](/storage/kb-images/69dbd9a4be-inline.png)

### Connection Examples

**Standard FTP:**
- Protocol: FTP
- Host: `ftp.example.com`
- Port: *(leave empty for default 21)*
- Username: `ftpuser`
- Password: `yourpassword`
- Passive Mode: Yes

**SFTP with Password:**
- Protocol: SFTP
- Host: `sftp.example.com`
- Port: *(leave empty for default 22)*
- Username: `sftpuser`
- Password: `yourpassword`

**SFTP with SSH Key:**
- Protocol: SFTP
- Host: `sftp.example.com`
- Port: *(leave empty for default 22)*
- Username: `ubuntu`
- Password: *(key passphrase, if your key is encrypted)*
- Private Key: *(paste your private key content)*

**FTPS (Secure FTP):**
- Protocol: FTPS
- Host: `secure-ftp.example.com`
- Port: *(leave empty for default 21)*
- Username: `secureuser`
- Password: `securepassword`
- Passive Mode: Yes

### Step 3: Test and Save

Click **Test Connection & Save** to verify the connection. FlowMattic will validate:
- Server connectivity on the specified host and port.
- Username and password credentials.
- Required PHP extensions are installed.


> **Note:** Your server must have the required PHP extensions installed:
> - **FTP/FTPS:** PHP `ftp` extension (usually built-in)
> - **FTPS:** PHP `openssl` extension
> - **SFTP:** PHP `ssh2` extension

---

## Triggers

The FTP/SFTP app includes two polling-based triggers that monitor folders for changes.

### New File in a Folder

Triggers when a new file is added to a monitored folder on the FTP/SFTP server.

**Configuration:**

| Field | Required | Description |
|-------|----------|-------------|
| Folder Path | Yes | Full path of the folder to monitor (e.g., `/uploads`). Defaults to `/` (root). |

**Trigger Output Data:**

| Field | Description |
|-------|-------------|
| `file_name` | Name of the newly detected file |
| `file_path` | Full path of the file on the server |
| `file_size` | Size of the file in bytes |
| `modified_time` | Last modification timestamp |
| `folder_path` | The monitored folder path |
| `trigger_event` | `new_file` |
| `total_files` | Total number of files in the folder |

![FTP Triggers.png](/storage/kb-images/eaae4601ed-inline.png)

### File Modified in a Folder

Triggers when an existing file in the monitored folder is modified (size or timestamp changes).

**Configuration:**

| Field | Required | Description |
|-------|----------|-------------|
| Folder Path | Yes | Full path of the folder to monitor (e.g., `/uploads`). Defaults to `/` (root). |

**Trigger Output Data:**

| Field | Description |
|-------|-------------|
| `file_name` | Name of the modified file |
| `file_path` | Full path of the file |
| `file_size` | Current file size in bytes |
| `previous_size` | Previous file size before modification |
| `modified_time` | Current modification timestamp |
| `previous_modified` | Previous modification timestamp |
| `folder_path` | The monitored folder path |
| `trigger_event` | `file_modified` |

![ftp file modified trigger.png](/storage/kb-images/10b4d570a0-inline.png)

### How Polling Works

1. **Initial capture:** FlowMattic creates a baseline snapshot of all files in the monitored folder.
2. **Subsequent polls:** On each check, FlowMattic compares the current file state against the baseline.
3. **Detection:** New files or modified files (changed size/timestamp) trigger the workflow.
4. **Baseline update:** After a trigger fires, the baseline is updated to reflect the current state.

> **Note:** Only files are monitored — directories are skipped. Polling frequency depends on your WordPress cron schedule.

---

## Actions

The FTP/SFTP app provides **8 file management actions**.

![ftp actions.png](/storage/kb-images/7a30b9b3d7-inline.png)

### Upload a File

Upload a file to the remote FTP/SFTP server from a URL or a local server path.

**Configuration:**

| Field | Required | Description |
|-------|----------|-------------|
| FTP Connect | Yes | Select your FTP/SFTP connection. |
| Source URL | No | URL of a file to download and upload (e.g., `https://example.com/file.pdf`). |
| Source File Path (Server) | No | Local file path on your WordPress server (e.g., `wp-content/uploads/2024/01/file.pdf`). |
| Remote File Path | Yes | Destination path on the FTP server (e.g., `/uploads/file.pdf`). |

> **Note:** Provide either a Source URL or a Source File Path — not both. Parent directories on the remote server are created automatically if they don't exist.

**Output:**

| Field | Description |
|-------|-------------|
| `status` | `success` or `error` |
| `message` | Result message |
| `remote_path` | Full path of the uploaded file on the server |

![Workflow Builder ‹ FlowMattic — WordPress 2026-03-01 at 1.10.10 AM.png](/storage/kb-images/7cf82e30bd-inline.png)

---

### Download a File

Download a file from the remote FTP/SFTP server to your WordPress site.

**Configuration:**

| Field | Required | Description |
|-------|----------|-------------|
| FTP Connect | Yes | Select your FTP/SFTP connection. |
| Remote File Path | Yes | Full path of the file on the FTP server (e.g., `/reports/monthly.csv`). |
| Local Save Path | No | Where to save the file locally. Leave empty to save to WordPress uploads folder. |

**Output:**

| Field | Description |
|-------|-------------|
| `status` | `success` or `error` |
| `message` | Result message |
| `local_path` | Full path where the file was saved |
| `file_url` | URL of the downloaded file (if saved to uploads) |
| `attachment_id` | WordPress Media Library attachment ID |
| `file_size` | Size of the downloaded file in bytes |
| `remote_path` | Original FTP path |

> **Tip:** When saved to the WordPress uploads folder, the file is automatically registered in the Media Library with proper MIME type detection.


---

### Delete a File or Folder

Delete a file or an empty folder on the remote server.

**Configuration:**

| Field | Required | Description |
|-------|----------|-------------|
| FTP Connect | Yes | Select your FTP/SFTP connection. |
| Remote Path | Yes | Full path of the file or folder to delete. |
| Is it a folder? | Yes | Select **Yes** for folders, **No** for files. |

**Output:**

| Field | Description |
|-------|-------------|
| `status` | `success` or `error` |
| `message` | Result message |
| `path` | The deleted path |

> **Important:** Folders must be empty before they can be deleted. Delete all files inside the folder first.

---

### List Folder Content

List all files and folders inside a directory on the remote server.

**Configuration:**

| Field | Required | Description |
|-------|----------|-------------|
| FTP Connect | Yes | Select your FTP/SFTP connection. |
| Folder Path | No | Path of the folder to list. Defaults to `/` (root). |

**Output:**

| Field | Description |
|-------|-------------|
| `status` | `success` |
| `path` | The folder path listed |
| `item_count` | Number of items in the folder |
| `items` | Array of items (see below) |

Each item in the `items` array contains:

| Field | Description |
|-------|-------------|
| `name` | File or folder name |
| `path` | Full path |
| `type` | `file` or `directory` |
| `size` | Size in bytes |
| `modified` | Last modification timestamp |
| `permissions` | File permissions |


---

### Rename / Move a File or Folder

Rename a file or folder, or move it to a different directory.

**Configuration:**

| Field | Required | Description |
|-------|----------|-------------|
| FTP Connect | Yes | Select your FTP/SFTP connection. |
| Current Path | Yes | Full path of the current file/folder. |
| New Path | Yes | New path/name. Use a different directory to move. |

**Output:**

| Field | Description |
|-------|-------------|
| `status` | `success` or `error` |
| `message` | Result message |
| `old_path` | Original path |
| `new_path` | New path |

**Examples:**
- **Rename:** `/uploads/old-name.pdf` → `/uploads/new-name.pdf`
- **Move:** `/uploads/file.pdf` → `/archive/file.pdf`
- **Move and Rename:** `/uploads/report.csv` → `/archive/2024-report.csv`

---

### Create a Folder

Create a new folder on the remote server.

**Configuration:**

| Field | Required | Description |
|-------|----------|-------------|
| FTP Connect | Yes | Select your FTP/SFTP connection. |
| Folder Path | Yes | Full path for the new folder (e.g., `/uploads/new-folder`). |

**Output:**

| Field | Description |
|-------|-------------|
| `status` | `success` or `error` |
| `message` | Result message |
| `path` | The created folder path |

> **Note:** SFTP supports recursive folder creation (parent directories are created automatically). For FTP, parent directories must already exist.

---

### Check if File Exists

Check whether a file or folder exists on the remote server.

**Configuration:**

| Field | Required | Description |
|-------|----------|-------------|
| FTP Connect | Yes | Select your FTP/SFTP connection. |
| Remote Path | Yes | Full path of the file or folder to check. |

**Output:**

| Field | Description |
|-------|-------------|
| `status` | `success` |
| `exists` | `true` or `false` |
| `type` | `file`, `directory`, or `unknown` |
| `path` | The checked path |

> **Use Case:** Use with a Branch step to conditionally upload, download, or delete files based on whether they exist.

---

### Get File Info

Retrieve detailed information about a file on the remote server.

**Configuration:**

| Field | Required | Description |
|-------|----------|-------------|
| FTP Connect | Yes | Select your FTP/SFTP connection. |
| Remote File Path | Yes | Full path of the file. |

**Output:**

| Field | Description |
|-------|-------------|
| `status` | `success` or `error` |
| `path` | Full file path |
| `name` | File name |
| `size` | File size in bytes |
| `type` | `file` or `directory` |
| `modified` | Last modification timestamp |
| `accessed` | Last access timestamp (SFTP only) |
| `permissions` | File permissions |

---

## Workflow Examples

### Example 1: Auto-Process Uploaded Files

Automatically download and process new files uploaded to an FTP folder.

1. **Trigger: New File in a Folder** — Monitor `/incoming` on the FTP server.
2. **FTP > Download File** — Download `{Trigger1.file_path}` to WordPress.
3. **Email** — Send notification with the download URL.

### Example 2: Backup WordPress Exports

Upload WordPress export files to a remote SFTP server for backup.

1. **Schedule Trigger** — Run daily.
2. **HTTP Request** — Call WordPress export endpoint.
3. **FTP > Upload File** — Upload the export file to `/backups/` on the SFTP server.
4. **Slack** — Notify the team that backup is complete.

### Example 3: File Sync Between Servers

Move files from one folder to another after processing.

1. **Trigger: New File in a Folder** — Monitor `/to-process`.
2. **FTP > Download File** — Download the file.
3. *(Process the file with other workflow steps)*
4. **FTP > Rename / Move** — Move from `/to-process/file.csv` to `/processed/file.csv`.

### Example 4: Conditional File Management

Check if a file exists before uploading, to avoid duplicates.

1. **Webhook Trigger** — Receive file upload request.
2. **FTP > Check File Exists** — Check if `/uploads/{Trigger1.filename}` exists.
3. **Branch** — If `{FTP1.exists}` is `true`, skip upload. Otherwise, continue.
4. **FTP > Upload File** — Upload the file.

---

## Troubleshooting

### Connection Issues

**"Connection failed"**
- Verify the host, port, and protocol are correct.
- Ensure your server firewall allows connections on the specified port.
- For FTP/FTPS, try enabling **Passive Mode**.

**"Login failed"**
- Double-check the username and password.
- For SFTP with SSH key, ensure the private key content is pasted correctly.

**"PHP extension not installed"**
- FTP/FTPS requires the PHP `ftp` extension.
- FTPS additionally requires the PHP `openssl` extension.
- SFTP requires the PHP `ssh2` extension.
- Contact your hosting provider to enable the required extension.

### Action Errors

**"Folder not empty" when deleting**
- You must delete all files inside a folder before deleting the folder itself.
- Use List Folder Content to see what's inside, then delete files first.

**"File not found" on download**
- Verify the remote file path is correct and the file exists.
- Use Check File Exists to verify before downloading.

**Upload fails with no error**
- Check that the remote directory exists or that auto-creation is working.
- Verify the FTP user has write permissions to the target directory.

### SFTP Authentication

**SSH key authentication fails:**
1. Ensure the private key is in the correct format (OpenSSH or PEM).
2. If the key has a passphrase, enter it in the Password field.
3. FlowMattic will automatically fall back to password authentication if key-based auth fails.

---

## Summary

| Feature | Details |
|---------|---------|
| **Supported Protocols** | FTP, FTPS (SSL/TLS), SFTP (SSH) |
| **Connection** | Host, port, username, password, SSH key |
| **Triggers** | 2 (New File, File Modified) |
| **Actions** | 8 (Upload, Download, Delete, List, Rename/Move, Create Folder, Check Exists, Get Info) |
| **Trigger Type** | Polling-based (cron-dependent) |
| **Media Library Integration** | Downloaded files auto-registered in WordPress Media Library |
| **Auto Directory Creation** | Yes (upload and SFTP folder creation) |
| **Authentication** | Password, SSH key (with passphrase), or both |

---

# General

Source: https://support.flowmattic.com/kb/article/1/general

FlowMattic is a WordPress plugin that helps you automate your workflows and save valuable time for more productive work. You can do it right within your WordPress dashboard. FlowMattic is built to be a no-code required plugin, that means, you can create workflows without needing to write a single line of code. A workflow is a process of doing things automatically with number of steps using different actions you want to perform. Workflow can be a combination of multiple application steps.

Let's check an example. Say, you have a contact form on your site, and it is submitted to your email. Then, you copy the submitted data to your Google Spreadsheet for easy access to your team members. Now, FlowMattic plays a vital role here of automating these things. What you need to do is - create a workflow with the contact form submission as a trigger, which will start the workflow execution after the form submission is made. The next step will use the Google Spreadsheet application to insert the data into your preferred Google Sheet. Once you are done with it, just publish the workflow and sit back! FlowMattic will handle every form submission and add it to your Google Sheet automatically. This will save your valuable time and you can spend it to focus on more important tasks in your life or business :)

The above workflow is just an example. FlowMattic can help you integrate 100s of WordPress plugins, 3rd party applications, and websites with your WordPress site and do automation for your daily tasks.&nbsp;

Get started with FlowMattic today! FlowMattic has an inexpensive pricing structure that no other plugin or platform can offer! We are updating the plugin every day with new features and new apps.

---

# Generate an image from a template in a workflow

Source: https://support.flowmattic.com/kb/article/188/generate-an-image-from-a-template-in-a-workflow

Once an image template is saved with its tokens, the **Image Builder** action renders it into a PNG inside any workflow. This guide covers the action's options.

## Step 1 — Add the Image Builder action

1. Open your workflow and add an action step.
2. Search for **Image Builder** and choose **Generate Image from Template**.

![Adding the Image Builder → Generate Image from Template action to a workflow](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-image-template-wf-generate-image-action.png)

## Step 2 — Pick your template

Select your saved template in the **Image Template** dropdown (`— Select a saved Image template —`). The action reads the template's saved sample data to build one field per token.

## Step 3 — Map your data

Set **Dynamic Data Mode** to one of:

- **Parameters — one field per token (recommended)** — one labelled field per token, each with a captured-data picker. This is the clearest way to map values.
- **JSON — paste the full data object** — a single **Data JSON** field for a complete data object, for use when an earlier step already produced one (for example an API response). Use the **Load sample data from the template** link to prefill it.

In Parameters mode, fill each token field with data from earlier steps.

![The Generate Image from Template action in Parameters mode, with one field per token](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-image-template-wf-image-parameters.png)

## Step 4 — Set the output filename

Enter an optional **Output Filename** such as `og-{post_slug}.png` (placeholder `og-{post_title}.png`). It can include captured data, and `.png` is appended automatically.

## Step 5 — Choose where to save

Set **Save to** to one of:

- **Media Library (default uploads / YYYY / MM folder)** — creates a reusable WordPress attachment.
- **Media Library — custom folder** — the same, under a **Custom Folder Path** you define (which can include captured data, e.g. `clients/{client_id}/og`).
- **Raw file (uploads/flowmattic-images/, no media library entry)** — written to disk and returned as a URL only.

Choose a Media Library option when a later step needs to email or upload the image; choose Raw when you only need the file on disk.

## Step 6 — Save and use the output

Save the step. When the workflow runs, it returns the rendered image's URL, file path, and attachment ID for later steps — for example to set a post's Open Graph image, attach the file to an email, or upload it to cloud storage.

## Note on dimensions

The image is always rendered at the template's own pixel dimensions. You set the size when you design the template; the workflow action does not change it. A render typically takes a few seconds because it runs through Cloudflare Browser Rendering.

---

# Generate an Image from Your Own HTML

Source: https://support.flowmattic.com/kb/article/248/generate-image-from-html

The Image Builder's template actions fill a designed template with data. **Generate Image from HTML** is the free-form alternative: give it any HTML and CSS and get back a PNG or JPEG — perfect for social share images, Open Graph images, score cards or certificates composed on the fly.

## Configure the action

Add an **Image Builder** step and choose **Generate Image from HTML**:

![Generate Image from HTML configured as a social share image](https://assets.infidesk.support/products/flowmattic/kb-images/release-72-apps/imgh-01-configure.png)

- **HTML** — a full document or a fragment; fragments are wrapped automatically so fixed dimensions and backgrounds render predictably. Map captured data anywhere inside.
- **Width / Height (px)** — the canvas, up to 4000×4000. The default **1200×630** is exactly the Open Graph / social card size.
- **Capture Full Page** — instead of the fixed canvas, the image grows to fit the full rendered content height.
- **Image Format** — PNG, or JPEG with a quality setting (default 85).
- **Output Filename** and **Save to** — Media Library or a custom uploads folder.

## It renders through a real browser — Cloudflare is required

Images are rendered through **Cloudflare Browser Rendering** (headless Chrome), so whatever CSS you write — flexbox, grid, gradients, web fonts — comes out pixel-perfect. That also means this action **requires Cloudflare credentials**, added once under **FlowMattic → Settings → Cloudflare**; unlike Generate PDF from HTML, there is no built-in fallback, and the step reports a clear error if credentials are missing.

## Good to know

- **Open Graph images in one step:** keep the default 1200×630, drop your post title into the HTML with a dynamic tag, and set the result as the post's social image.
- **The response** includes the file URL and attachment ID, ready to set as a featured image, attach to an email, or return from a webhook.
- **Template-based images** (the *Generate Image* action with an Image Template) remain the better fit when the design is fixed and reused — this action is for HTML you compose per run.

---

# Generate a PDF from a template in a workflow

Source: https://support.flowmattic.com/kb/article/189/generate-a-pdf-from-a-template-in-a-workflow

Once you have a saved PDF template, the **PDF Builder** action renders it into a finished file inside any workflow. This guide covers the action's options: how to map data, where the file is saved, and what the step returns.

## Step 1 — Add the PDF Builder action

1. Open the workflow you want to add the PDF to.
2. Add an action step and search for **PDF Builder**.
3. Choose **Generate PDF from Template**.

![Adding the PDF Builder → Generate PDF from Template action to a workflow](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-pdf-template-builder-wf-generate-pdf-action.png)

## Step 2 — Pick your template

Select your template in the **PDF Template** dropdown. As soon as you pick one, the action reads the parent-level keys of that template's sample data and generates one field per key under **Parameters**.

## Step 3 — Choose a data mode and map your data

The action has two **Dynamic Data Mode** options:

- **Parameters** (recommended) — FlowMattic shows one labelled field per top-level key in your template's sample data. Fill each field with data captured from earlier steps using the database icon to pick variables. This is the clearest way to map data and is why setting your template's sample data first matters.
- **JSON** — a single field where you paste a complete JSON object. Use this when an earlier step (a Code step, an API response, or a JSON Parser) already assembled the full object.

In Parameters mode, values are coerced automatically: `1200` becomes an integer, `true` and `false` become booleans, and a value beginning with `{` or `[` is parsed as JSON. To send a literal string like `"1200"`, use JSON mode and quote it.

Any key you leave empty falls back to the value stored in the template's sample data.

![The Generate PDF from Template action in Parameters mode, with the template selected and one field per parent-level key](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-pdf-template-builder-wf-pdf-parameters.png)

## Step 4 — Set the output filename

Enter an **Output Filename** such as `invoice-{invoice.number}.pdf`. You can include captured data in the name so each run produces a predictably named file. If you leave it blank, FlowMattic generates a name automatically.

## Step 5 — Choose where to save the file

Set **Save to** to one of:

- **Media Library** — creates a WordPress attachment you can reuse in later steps.
- **Media Library with a custom folder** — the same, filed under a folder path you define (the path can include captured data, e.g. `clients/{client_id}/invoices`).
- **Raw file** — written to `uploads/flowmattic-pdfs/` and returned as a URL only, with no attachment post.

Pick a Media Library option when a later step needs to attach or upload the file; pick Raw when you only need the file on disk.

## Step 6 — Save the step and use the output

Save the action. When the workflow runs, the step returns these values for the next steps to use:

- `url` — the file's public URL
- `path` — the absolute server path
- `attachment_id` — the Media Library attachment ID (Media Library modes only)
- `file_size` — the size in bytes
- `filename` — the final file name

For example, add an **Email** action after this step and attach the PDF using the `url` the PDF Builder step returned.

---

# Generate a PDF from Your Own HTML

Source: https://support.flowmattic.com/kb/article/247/generate-pdf-from-html

The PDF Builder's template actions are great when a designer-made template does the job. The **Generate PDF from HTML** action is for the times you want full control: you bring the HTML and CSS — often generated by an AI step or assembled from captured data — and FlowMattic turns it into a PDF file.

## Configure the action

Add a **PDF Builder** step and choose **Generate PDF from HTML**:

![Generate PDF from HTML with the rendering engine choice](https://assets.infidesk.support/products/flowmattic/kb-images/release-72-apps/pdfh-01-configure.png)

- **HTML** — a full HTML document or just a fragment (fragments are wrapped automatically with a UTF-8 charset). Inline CSS and `<style>` blocks both work, and dynamic tags can be mapped anywhere inside.
- **Page Size / Orientation / Page Margin** — A4, Letter and friends, portrait or landscape, margin in millimetres.
- **Output Filename** and **Save to** — the Media Library or a custom folder in your uploads directory.

## The rendering engine — why there are two

**This is the setting that changes what your PDF looks like.**

- **Cloudflare Browser Rendering** renders your HTML through headless Chrome, so it looks exactly as it would in a browser — flexbox, CSS grid, gradients, web fonts, modern CSS in general. It needs Cloudflare credentials, added once under **FlowMattic → Settings → Cloudflare** (an account with the Browser Rendering API available).
- **The built-in engine** runs entirely on your server with no external service — but it supports a smaller, classic CSS subset. Simple documents look identical; heavily styled layouts built on flexbox or grid will not.
- **Automatic** (the default) prefers Cloudflare when credentials are configured and falls back to the built-in engine when they aren't.

The practical rule: **if your HTML uses modern layout CSS, configure Cloudflare and pick it explicitly** — that turns "usually looks right" into "always looks right". If your documents are simple enough for the built-in engine, pick it explicitly and there is no external dependency at all.

## Good to know

- **The response** carries the file URL, path and attachment details, ready to attach to an email, store in a table or send onward.
- **Pair it with AI:** have an AI step write the invoice or report HTML from your data, then feed its output straight into this action's HTML field.
- **Template-based PDFs** (the *Generate PDF* action with a PDF Template) remain the better choice when the layout is fixed and only the data changes.

---

# Generate Barcodes in Your Workflows

Source: https://support.flowmattic.com/kb/article/246/generate-barcodes

The **Barcode Generator** app renders classic 1D barcodes as PNG images — on your own server, with no external service. Feed it an order number, a SKU or a tracking code and use the result on packing slips, tickets, PDFs or emails.

## Configure the barcode

Add a **Barcode Generator** step with its single action, **Generate Barcode**:

![The Generate Barcode configuration](https://assets.infidesk.support/products/flowmattic/kb-images/release-72-apps/bar-01-configure.png)

- **Barcode Content** — the value to encode. Map it from any previous step.
- **Barcode Type** — the symbology. 29 are supported, searchable in the dropdown: the Code 128 family (recommended for general use — B for letters and digits, C for compact digits-only), Code 39 and its variants, Code 93, Code 11, Codabar, retail codes (EAN-13, EAN-8, UPC-A, UPC-E, the EAN-2/EAN-5 supplements, ISBN, ISSN), Interleaved and Standard 2 of 5, MSI, and the postal set (POSTNET, PLANET, USPS Intelligent Mail, Royal Mail RM4SCC, Dutch KIX).
- **Bar Width / Bar Height** — the drawing scale in pixels.
- **Show Value Below Barcode** — print the human-readable value under the bars.
- **Bar / Background Colour** — hex colours, for matching branded documents.
- **Output** — save to the **Media Library** (you get an attachment ID, URL and path) or return a **base64 data URI** to embed straight into HTML, an email or a PDF template.

## Test it

Click **Test Action** and the barcode is generated immediately — the response carries the file URL, attachment ID and dimensions:

![A successful barcode test with the file URL in the response](https://assets.infidesk.support/products/flowmattic/kb-images/release-72-apps/bar-02-test.png)

And the resulting PNG:

![The generated EAN-13 barcode](https://assets.infidesk.support/products/flowmattic/kb-images/release-72-apps/bar-03-result.png)

## A value that doesn't fit is rejected — on purpose

Several symbologies accept only specific input: EAN-13 wants 12 or 13 digits, UPC-A 11 or 12, EAN-8 seven or eight, the 2-of-5 family digits only. If the content cannot be encoded in the chosen symbology, the step **rejects it with a clear error instead of padding or truncating your value** — a barcode that silently encodes something other than what you sent would scan as the wrong product, order or parcel. Fix the value (or pick a freer symbology like Code 128 B) and run again.

## Good to know

- **Code 128 B is the safe default** for arbitrary order numbers and SKUs — letters, digits and symbols, compact and universally scannable.
- **Check digits:** for EAN/UPC/ISBN, send the value with or without its final check digit — 12 digits are accepted and the check digit computed. The "+ check digit" variants of Code 39, I25, S25 and MSI append one for you.
- **ISBN/ISSN hyphens are removed automatically** — paste the number as printed.
- **QR codes are 2D** and not part of this app's 1D set.

---

# Generate Images in Workflows (Image Builder)

Source: https://support.flowmattic.com/kb/article/158/generate-images-in-workflows-image-builder

The **Image Builder** integration is a core FlowMattic action that turns one of your saved Image templates into a finished PNG inside a workflow. It takes the template you designed in the Image Template Builder, fills in its `{{tokens}}` with data from earlier steps, renders the design pixel-for-pixel using Cloudflare Browser Rendering (real headless Chrome), and saves the image so later steps can attach it, upload it, or post it. The single action it provides is **Generate Image from Template**.

Before using it, design and save at least one template under **FlowMattic → Image Templates**, and add your Cloudflare credentials (see Requirements at the end).

## Adding the action

In your workflow, add an **Action** step, choose the **Image Builder** app, and select the **Generate Image from Template** action. The configuration fields appear below.

![A workflow action step with Image Builder selected and the "Generate Image from Template" action chosen, showing the configuration fields.](https://assets.infidesk.support/kb/inline/2026/07/jcvgXn7IZM8ufaQFRkylqQumbr7fIeDQgMHzbGUH.png)

## Image Template (required)

The **Image Template** dropdown lists every template you have saved. Pick the one you want to render. If you don't see your template, create one first — the panel links to **FlowMattic → Image Templates**. The note also explains the key dependency: *"The builder's saved sample data defines the parameters available below."* In other words, the tokens you gave sample values to when saving the template are exactly the data fields you'll fill in here.

## Dynamic Data Mode

The **Dynamic Data Mode** dropdown chooses how you supply the data that fills the template's tokens. There are two modes:

- **Parameters — one field per token (recommended)** — FlowMattic auto-generates a separate input for every token saved on the template.
- **JSON — paste the full data object** — a single textarea where you provide the entire data payload as a JSON object. Choose this when you already have the complete object from an earlier step.

### Parameters mode

When you pick a template, FlowMattic reads its saved sample data and **automatically detects the parameters**, listing one field per token under **Parameters**. Each row shows a friendly label, the raw token key in code style (for example `post_title`), and a textarea where you type a value or insert captured data from earlier steps using the database icon.

If a token's sample value was a list or object (an array), the field is marked with a **JSON** badge and labeled a structured field — paste a JSON array or object there. Any parameter you leave blank falls back to the template's saved sample value, so partial input never leaves a token unresolved.

If the dropdown shows no parameters, the template has no saved sample data yet. Open the template, add tokens with sample values in the **Data** panel and save, or switch to JSON mode.

![The action in Parameters mode after a template is selected, showing the auto-generated parameter fields, each with its label and token key](https://assets.infidesk.support/kb/inline/2026/07/E2PlmlAetlO5bH1huKiMMcQAQ7vs9oE7OQ3DObkO.png).

### JSON mode

In JSON mode you get a single **Data JSON** textarea. Paste a JSON object whose keys match your template's tokens, for example `{"post_title": "Hello", "post_author": "Sarah"}`. Keys you omit fall back to the template's saved sample values. A **Load sample data from the template** link fills the textarea with the template's saved sample object as a starting point, and the database icon lets you drop in captured data from an earlier step.

![The action in JSON mode showing the Data JSON textarea and the "Load sample data from the template" link](https://assets.infidesk.support/kb/inline/2026/07/igHRknrvdU09gfg00fU56YMnhmvU5xtdqWG0TIli.png).

## Output Filename

The **Output Filename** field is optional. Leave it blank and FlowMattic names the file using the template name plus a timestamp. You can also build a dynamic name from earlier-step data, such as `og-{post_title}.png`. The `.png` extension is added automatically if you omit it.

## Save to (destination)

The **Save to** dropdown controls where the rendered PNG is stored. There are three destinations:

- **Media Library (default uploads / YYYY / MM folder)** — adds the image to the WordPress Media Library in the standard month-based uploads folder, creating an attachment.
- **Media Library — custom folder** — also creates a Media Library attachment, but stores the file in a folder you specify.
- **Raw file (uploads/flowmattic-images/, no media library entry)** — writes the PNG straight to disk under `wp-content/uploads/flowmattic-images/` without creating a Media Library entry.

The two Media Library options create an attachment post (with an **attachment ID**) that you can reuse in later steps — as an email attachment, a Slack upload, an S3 push, and so on. Raw mode simply drops the file on disk and returns its URL.

### Custom Folder Path

When you choose **Media Library — custom folder**, a **Custom Folder Path** field appears. Enter a path relative to `wp-content/uploads/` (for example `flowmattic/og-images`). The folder is created automatically if it doesn't exist, and the path supports captured data, so you can route images per record, such as `clients/{client_id}/og`.

![The "Save to" dropdown expanded showing the three destination options, with the Custom Folder Path field visible](https://assets.infidesk.support/kb/inline/2026/07/vEg5WSiNuXiEkO0b2PF3LSlxQ8euvN3guL0J0BBd.png).

## What the action returns

After it runs, the action outputs values you can map into later steps, including the image **url**, the file **path**, the **attachment_id** (for Media Library destinations), the **file_size**, the rendered **width** and **height**, the **filename**, the **destination**, and the **template_name**. FlowMattic also increments the template's "Images Generated" count each time the action runs.

## How rendering works

When the workflow runs, FlowMattic loads your saved template, builds its HTML, and resolves the data in a careful order: QR Code elements are generated first (so their token values are encoded safely), then all remaining `{{tokens}}` are replaced with your supplied values, falling back to the template's saved sample data for anything missing. The completed HTML — at the template's exact stored width and height — is sent to **Cloudflare Browser Rendering**, Cloudflare's headless-Chrome screenshot service, which produces a true browser-quality PNG. This is what makes gradients, web fonts, shadows, and QR codes render pixel-perfect rather than approximated. The resulting PNG bytes are then saved to your chosen destination.

The render uses the template's stored dimensions; there is no size override on the action, so set your canvas size in the Image Template Builder.

## Requirements

This action depends on **Cloudflare Browser Rendering**. You must add your **Cloudflare Account ID** and a **Cloudflare API Token** under **FlowMattic → Settings → Cloudflare Browser Rendering**. Without credentials, the action returns an error asking you to configure them. If a Media Library save ever fails, the action falls back to saving the raw file so the workflow still produces a usable image URL.

---

# Generate PDFs in Workflows (PDF Builder)

Source: https://support.flowmattic.com/kb/article/160/generate-pdfs-in-workflows-pdf-builder

PDF Builder is a built-in (core) FlowMattic integration that turns one of your saved PDF templates into a finished PDF during a workflow run. You pick a template, supply the dynamic data that fills its tokens, choose where to save the file, and the action outputs the PDF's URL, file path, and Media Library attachment ID so later steps can email it, upload it, or attach it to a record. Templates are designed under **FlowMattic → PDF Templates** with the PDF Template Builder; this integration is how a workflow actually renders them.

## Before you start

You need at least one saved PDF template. Build one under **FlowMattic → PDF Templates** and save it with sample data — the **top-level keys of that sample data become the parameters** this action lets you fill in. If a template has no saved sample data, you can still use JSON mode (described below).

## Adding the action

In your workflow, add an action step and choose the **PDF Builder** app, then the **Generate PDF from Template** action. (The PDF Builder app also includes **Create PDF Template with AI** and **Delete PDF Template** actions, but the rest of this guide covers Generate PDF from Template.)

![The workflow action picker with the PDF Builder app selected and "Generate PDF from Template" chosen](https://assets.infidesk.support/kb/inline/2026/07/K9NOd2Jr5RrSxuG41QrAn9laWcV4T8BJQwsCFkXb.png).

## The action fields

### PDF Template (required)

The first dropdown lists every saved PDF template. Pick the one you want to render. If you don't see your template, create one under **FlowMattic → PDF Templates** — the link is shown right under the field. The template you choose determines which parameters appear below.

### Dynamic Data Mode

This controls *how* you supply the data that fills the template's `{{tokens}}`. There are two modes:

- **Parameters — one field per parent-level key (recommended)**: FlowMattic auto-generates one input for each top-level key in the template's saved sample data. This is the easiest way to map workflow data into the template.
- **JSON — paste the full data object**: gives you a single large textarea for the whole data payload. Choose this when you already have a complete JSON object from an earlier step.

![The Dynamic Data Mode dropdown showing the Parameters and JSON options.](https://assets.infidesk.support/kb/inline/2026/07/cUnMdt9PhQIsDB7QXV39fGf8FtbbIw9ie5cDXqKs.png)

### Parameters (Parameters mode)

When you select a template in Parameters mode, FlowMattic loads its saved sample data and creates one field per top-level key. For example, a template whose data has `invoice`, `company`, `client`, `line_items`, and `totals` produces five fields, each labelled in a friendly form ("Line Items") with the raw key shown beside it.

- Fields whose value is an object or array are marked with a **JSON** badge — paste a JSON object/array there (or use the database/captured-data icon to insert an array from an earlier step).
- Simple fields take a plain value. Numbers, `true`/`false`, and JSON-looking text are interpreted automatically; everything else is treated as a string.
- Each field's placeholder shows the template's saved sample value so you know the expected shape.
- Any parameter you leave blank falls back to the template's saved sample data, so partially filled inputs won't break untouched tokens.

Use the database icon on any field to insert captured data from previous steps (trigger fields, earlier action outputs, etc.).

![The Parameters section showing auto-generated fields, with a structured field carrying a JSON badge and a multi-line textarea](https://assets.infidesk.support/kb/inline/2026/07/qSlnQSTbI5DrNi3NcpJunFVpAC7JXVEQy14Fb7W2.png).

### Data JSON (JSON mode)

In JSON mode you get a single **Data JSON** textarea. Paste a full JSON object matching the shape of the template's sample data. Keys you omit fall back to the template's saved defaults. Use the database icon to insert workflow variables — their resolved values are merged into the JSON at run time. The **Load sample data from the template** link fills the textarea with the template's saved sample so you can edit from a known-good starting point.

![ The Data JSON textarea in JSON mode with the "Load sample data from the template" link below it.](https://assets.infidesk.support/kb/inline/2026/07/ru2ELFD5cuxHMKfHQxvDOkrhRmsSez43F4LkNyiH.png)

### Output Filename

Optional. The name for the generated file. It supports captured data (for example `invoice-{invoice.number}.pdf`). If you leave it blank, the template name plus a timestamp is used. The `.pdf` extension is added automatically if you don't include it.

### Save to (destination)

Where the rendered PDF is stored. Three options:

- **Media Library (default uploads / YYYY / MM folder)**: saves the file as a normal WordPress attachment in the standard month-based uploads folder. This creates an attachment post you can reuse in later steps (email attachments, S3 upload, CRM linking, etc.).
- **Media Library — custom folder**: saves it as an attachment, but into a folder you specify.
- **Raw file (uploads/flowmattic-pdfs/, no media library entry)**: drops the file on disk in `uploads/flowmattic-pdfs/` without creating an attachment post.

![The "Save to" dropdown showing the three destination options.](https://assets.infidesk.support/kb/inline/2026/07/Atx9ktsGwGujlki7BmTnM2m9uOHImpVKhKgJiiPe.png)
### Custom Folder Path

Shown only when **Save to** is set to **Media Library — custom folder**. Enter a path relative to `wp-content/uploads/` (for example `flowmattic/invoices`). The folder is created automatically if it doesn't exist, and the field supports captured data so you can route by record — for example `clients/{client_id}/invoices`.

## What the action outputs

After the step runs, it returns data you can use in later steps, including:

- **url** — the public URL of the generated PDF.
- **path** — the file path on the server.
- **attachment_id** — the Media Library attachment ID (0 for the raw-file destination).
- **file_size**, **filename**, **template_id**, **template_name**, **destination**, and **data_mode**.

A common pattern is to follow this step with a "Send Email" action that attaches the PDF using the returned **url** or **attachment_id**.

## How the data is assembled (good to know)

Whichever mode you use, your supplied data is layered on top of the template's saved sample data, so any tokens you don't provide still resolve to sensible defaults:

- **JSON mode**: your pasted object is merged recursively over the saved sample data.
- **Parameters mode**: each parameter you fill replaces that top-level key; blank parameters keep the template default.

This means you only need to send the fields that actually change per run.

## Tips and troubleshooting

- **No parameter fields appear**: the chosen template has no saved sample data. Open it in the builder, add sample JSON in the Data panel, and save — or switch to JSON mode and pass the whole object.
- **"The JSON data is not valid"**: in JSON mode, the payload must be a valid JSON object, e.g. `{ "invoice": { "number": "INV-1" } }`. Fix the syntax and retry.
- **Template not found**: the template was deleted or its ID changed. Re-select a valid template.
- **For pixel-accurate output**: configure Cloudflare Browser Rendering under **FlowMattic → Settings** so the rendered PDF matches the builder's preview exactly.

Every time the action runs successfully, the template's "PDFs Generated" count on the **PDF Templates** page increases, so you can see how often each template is used.

---

# Generate with AI in the Email Template Builder

Source: https://support.flowmattic.com/kb/article/161/generate-with-ai-in-the-email-template-builder

Generate with AI lets you describe an email in plain language and have FlowMattic draft the whole thing for you: the layout blocks, the subject line, the pre-header (preview text), and sample dynamic data for any merge tags it uses. You can launch it from three places, and it always uses one of your saved AI provider connections to do the work.

## What Generate with AI produces

When you submit a description (the builder calls it a "brief"), FlowMattic sends it to your chosen AI model and gets back a single, complete email template. Specifically it creates:

- **Email blocks** — a full layout built from the builder's real block types: **Heading**, **Text**, **Html**, **Button**, **Image**, **Divider**, **Spacer**, **ColumnsContainer**, **Container**, and **Loop** (a repeating section). It also sets the overall page (the **EmailLayout**): backdrop color, canvas color, text color, and font family. The AI is guided to keep emails focused — typically 5 to 12 blocks.
- **Subject** — a subject line for the email, which can include merge tags (for example, `Welcome to {{company}}, {{first_name}}!`).
- **Pre-header** — the short preview text that some inboxes show next to the subject.
- **Sample dynamic data** — for every merge tag the email uses (like `{{first_name}}` or `{{company}}`), FlowMattic adds a concrete sample value so you can preview the email with realistic content. If the AI includes a **Loop** block, it also generates a small sample array (a couple of example rows) for that loop to repeat over.

Everything the AI returns is validated and cleaned on the server before it reaches you. Blocks of unknown types are dropped, broken references between blocks are repaired, colors are checked, and any merge tag without a sample value gets an empty placeholder added so nothing renders as raw `{{tag}}` text.

![The email builder canvas right after an AI generation, showing the generated blocks plus the subject and pre-header filled in](https://assets.infidesk.support/kb/inline/2026/07/F8NVxuSLP3GqS1oGE7TEvdVE5hC5nJg0NshqHFXC.png)

## Requirements: an AI provider Connect

Generate with AI does not use a built-in key — it runs through the same AI provider connections used by FlowMattic's AI Agent. Before you can generate, you need at least one saved **Connect** for a supported AI provider. The supported providers are: **OpenAI**, **Anthropic**, **Google**, **Groq**, **Mistral**, **xAI (Grok)**, **Perplexity**, **DeepSeek**, **OpenRouter**, and **Straico**.

You create these connections under **FlowMattic → Connects** with your own provider API key. If you have no matching connection, the dropdowns will be empty and you won't be able to generate.

On the **Email Templates** listing page, the **Generate with AI** button is also disabled until your FlowMattic **license key is registered** (it appears greyed out with a "needs registration" state).

![FlowMattic Connects screen showing a saved AI provider connection (for example an OpenAI connect)](https://assets.infidesk.support/kb/inline/2026/07/9Ame6tXjwrrgGATDgcJicCFnnzCTpNIsJuR0Cphb.png)

## Entry point 1: The builder sidebar

When you are editing a template inside the Email Template Builder, the left sidebar has a **Template Actions** section. Click **Generate with AI** (described there as "Rewrite the email from a prompt"). This opens the Generate with AI dialog.

Because you are editing an existing design, applying an AI result here **replaces your current design**. If the email already has content, FlowMattic shows a confirmation: "Replace the current design with the AI-generated email? Unsaved changes will be lost." Choose OK to apply.

After it applies, the generated email loads straight into the builder and a message appears: "AI email applied. Review it, then click Save." The new design is not saved automatically from here — review it and click **Save** yourself.

![The builder sidebar Template Actions section with the Generate with AI button highlighted](https://assets.infidesk.support/kb/inline/2026/07/UV4exXg3htf7J1rWyetC0xPm3pc0CdsN8wrexUaO.png)

## Entry point 2: The Switch Template picker

Still inside the builder, the sidebar's **Switch Template** action opens a gallery of starter layouts. The first card in that gallery is a purple **Generate with AI** card labeled "Recommended" with the subtitle "Describe it — get a draft." Clicking it closes the picker and opens the same Generate with AI dialog described above, including the same "replace your current design" confirmation when applying.

![The Switch Template gallery with the Recommended "Generate with AI" card as the first tile](https://assets.infidesk.support/kb/inline/2026/07/gyT8dX6JNwUIGg6aWwP4xA3sJigp9njdDSlz3Grk.png)

## Entry point 3: The Email Templates listing page

From the WordPress admin, go to **FlowMattic → Email Templates**. There are two ways to start here:

- The **Generate with AI** button in the page header (top right, next to **Create New Template**).
- Inside the **Create New Template** modal, the first starter card is an AI card marked **Recommended** ("Generate with AI — Describe the email — get a draft in seconds"). Clicking it closes the create modal and opens the AI generator.

If you have no templates yet, the empty state also has a **Generate with AI** button.

This launches the listing page's generator modal, titled **Generate an email template with AI**. Unlike the in-builder dialog, this one creates a brand-new saved template (it does not touch an existing design), and when it finishes it takes you straight into the editor for the new template.

![The Email Templates listing page header showing the Generate with AI button next to Create New Template](https://assets.infidesk.support/kb/inline/2026/07/PZFAuVxTeTKwumzShKIqRgw8iBLIWYkP1TJ2v1Uq.png)

## The Generate with AI dialog (in builder and Switch Template)

This is the lighter of the two forms. It has:

- **Provider** — pick which AI provider to use from your supported, saved connections.
- **Connection** — pick the specific saved Connect for that provider. If a provider has no matching connection, the list falls back to your other (unlabeled) connections so you can still choose one.
- **Describe the email** — the prompt box. Type what you want, for example "A welcome email for new subscribers with a discount code and a shop-now button." Your description must be at least 10 characters.
- **Or start from an example** — a list of one-click example prompts (welcome email, weekly product newsletter, product launch, order receipt, event invitation). Clicking one fills the description box; you can edit it before generating.

Click **Generate email** to run it. While it works, the dialog shows a progress indicator cycling through phases (Planning layout, Writing copy, Wiring merge tags, Finalizing). You can press **Cancel generation** to stop it. Generation also times out automatically after about 90 seconds so it never hangs.

Your chosen provider and connection are remembered as your defaults for next time.

![The Generate with AI dialog showing the Provider and Connection dropdowns, the description box, and the example list](https://assets.infidesk.support/kb/inline/2026/07/rQ4x5suYz4HKankq9m9legjOWRV5QMQLzLErO65t.png)

## The "Generate an email template with AI" modal (listing page)

The listing page modal has a few more options:

- **Template name** *(optional)* — a name for the new template. If you leave it blank, the AI picks a name for you.
- **Describe your email template** — the prompt box (the brief). Minimum 10 characters.
- **Or start from a template** — quick-fill prompt chips: **Welcome Email**, **Weekly Newsletter**, **Order Receipt**, and **Event Invitation**. Clicking a chip fills the description with a detailed starter prompt you can then edit.
- **AI provider** — choose a supported provider.
- **Connect** — choose the saved connection for that provider. This dropdown stays disabled until you pick a provider, and (like the builder dialog) falls back to your unlabeled connections if none are tagged for the chosen provider.
- **Model** *(provider default)* — optionally choose a specific model; "Provider default" uses the recommended model for that provider. Tick **Use a custom model name** to type an exact model ID instead (for example `gpt-4o-mini`).

Once you have a provider and connection chosen, the picker collapses into a one-line summary at the bottom of the modal with a **Change** link to reopen it.

Click **Generate email template** to run. A progress panel shows your prompt and steps through phases (Reading your description, Choosing layout and sections, Composing the email, Validating blocks, Finalizing template), with a **Cancel generation** option and an automatic timeout of about 120 seconds. When it succeeds, the new template is saved and you are redirected into the editor to refine it.

![The Generate an email template with AI modal showing Template name, description, template chips, and the AI provider / Connect / Model picker](https://assets.infidesk.support/kb/inline/2026/07/RA1JGYnEQEknwgoQN9yjc9fVAUxdgFU9vhqNUPnz.png)

## Refining and sending the result

The AI output is a starting point, not a final send. After generating:

1. Review and edit the generated **blocks**, **subject**, and **pre-header** in the builder like any normal template.
2. Check the generated **sample dynamic data** under the builder's **Data** tab, and adjust the sample values or merge tags as needed.
3. Use **Send Test Email** from the sidebar to preview the result in your own inbox with the sample data filled in.
4. Click **Save** when you are happy with it.

Generated templates are sent the same way as any other email template — through a workflow. Build a workflow, add the **Email SMTP** step, choose the **Send Template Email** action, and pick your template; the merge tags are then filled in from your real workflow data at send time.

![email-ai-sample-data-tab](https://assets.infidesk.support/kb/inline/2026/07/t3Gmi3GT1z5tz85upH31DeDlYFXUFDBllF7PmYeh.png)

---

# Generate with AI in the Workflow Builder

Source: https://support.flowmattic.com/kb/article/213/generate-with-ai-in-the-workflow-builder

Generate with AI turns a plain-language description into a complete, working workflow — trigger, steps, routers and branches — ready for you to review and refine.

You will find it on the **Workflows** listing page, and in the create-workflow dialog when you start a new one.

![The Generate workflow with AI dialog, with a description box, starter template chips, and the selected AI provider shown at the bottom](https://assets.infidesk.support/products/flowmattic/kb-images/v70/213-generate-with-ai.png)

## Before you start: an AI provider Connect

Generate with AI uses your own AI provider API key, held in a FlowMattic Connect. There is no FlowMattic AI credit — your provider bills you directly.

Ten providers are supported: **OpenAI, Anthropic, Google, Groq, Mistral, xAI, Perplexity, DeepSeek, OpenRouter and Straico.** Set one up under **FlowMattic → Connects** first; the generator will ask you to pick which connection to use.

## Writing a good brief

Your description must be at least ten characters, but a one-liner will not get you far. The generator does best when you tell it three things: **what starts the workflow, what should happen, and where the data goes.**

Weak brief:

> send emails to customers

Strong brief:

> When a WooCommerce order is marked complete, look the customer up in HubSpot. If their lifetime value is over $500, send them the VIP thank-you email; otherwise send the standard one.

That second version gives the generator a trigger, a lookup, a branching condition and two outcomes — so it can build the router instead of guessing you wanted one.

## Three things to expect

### Your new workflow is switched OFF

**Every AI-generated workflow is saved disabled.** This is deliberate — you get to read what it built before anything runs against live data. If you generate a workflow and then wonder why nothing is happening, this is almost always the reason. Review the steps, then toggle it on.

### Some triggers cannot be generated

Four trigger types are deliberately excluded, because auto-configuring them reliably is not yet possible:

- **Schedule**
- **Plugin Actions**
- **RSS Feed**
- **MCP Trigger**

So a brief like *"run this every morning at 9am"* will **not** produce a Schedule trigger. The generator builds the rest of the workflow and you add the trigger yourself afterwards — open the workflow, change the trigger, and configure the schedule.

### It sometimes picks the wrong action

The generator searches the integration catalogue and chooses what best fits your brief. Occasionally it picks a plausible-but-wrong action — a "create" where you wanted an "update", for instance.

Two things help:

- **Be specific in the brief.** Name the app and, where you can, the action: "use the HubSpot *Update Contact* action".
- **Use a stronger model.** Smaller, faster models are noticeably more prone to settling on the wrong action. If you are seeing this repeatedly, switch the AI defaults to a more capable model — it makes a real difference.

Either way, always read the generated steps before switching the workflow on.

## What happens after you submit

FlowMattic sends your brief to the model, which looks through the available trigger and action apps, checks each app's events, assembles the workflow and validates it. That whole exchange is capped, so a very sprawling brief may come back partially built rather than running indefinitely — another reason to keep briefs focused.

The workflow is named from the first few words of your brief, so it is worth starting the description with something recognisable. You can rename it afterwards.

## If generation fails

- **"Describe the workflow in a little more detail"** — the brief is under ten characters.
- **A provider error** — the message names the provider and model it tried, for example *Anthropic (claude-sonnet-…)*. That tells you which Connect was used. Check the key is valid and has credit with that provider.
- **The result could not be built into a valid workflow** — FlowMattic retries once automatically before reporting this. If it persists, simplify the brief or try a stronger model. Very long, multi-part briefs are the usual cause; splitting the work into two workflows often succeeds where one large one fails.

## Related

- [Jaadu vs Generate with AI: which one should you use?](/kb/jaadu-vs-generate-with-ai)
- [Jaadu: the AI copilot in FlowMattic](/kb/jaadu-the-ai-copilot-in-flowmattic)
- [Generate with AI in the Email Template Builder](/kb/generate-with-ai-in-the-email-template-builder)

---

# Getting started with FlowMattic Managed Tables

Source: https://support.flowmattic.com/kb/article/249/getting-started-with-flowmattic-managed-tables

FlowMattic Tables gives your site its own **managed database** — isolated to your site, provisioned in about a minute, and usable from every workflow. There are no servers to run and no overage bills: hit a plan limit and FlowMattic tells you; it never charges extra.

This guide walks you from a fresh install to your first working table.

## What you get

- A private, managed database for your site — records live outside your WordPress database, so heavy data never slows your site down.
- A spreadsheet-style grid with typed columns — text, numbers, dates, and premium types like **Person**, **Tags**, **Files**, **Currency**, **Relation**, and **AI text**.
- Workflow actions to insert, update, find, and delete rows — plus triggers that fire when rows change.
- Automatic exports and point-in-time recovery, depending on your plan.

## Step 1 — Open FlowMattic Tables and pick a plan

Go to **FlowMattic → FlowMattic Tables**. Until your site is connected, the page shows the available plans:

![FlowMattic Tables plans — Starter, Pro, and Business](https://assets.infidesk.support/products/flowmattic/kb-images/tables/01-empty-state.png)

- **Starter** — 100,000 records, 250,000 writes per month, 1 export per day.
- **Pro** — 500,000 records, 2,000,000 writes per month, on-demand exports, 30-day point-in-time recovery.
- **Business** — 2,000,000 records, 10,000,000 writes per month, nightly automatic exports, self-serve point-in-time restore.

Reads are always unlimited on every plan. Switch the billing toggle to **Annual** to get two months free:

![Annual billing — two months free](https://assets.infidesk.support/products/flowmattic/kb-images/tables/02-pricing-annual.png)

Every plan starts with a **7-day free trial** at full capacity — you are not charged until the trial ends, and you can cancel from the billing portal anytime. Click **Start free trial** on a plan and complete checkout. Your database is provisioned automatically — you never paste an API key. Within a minute the page switches to your dashboard.

## Step 2 — Meet your dashboard

Once connected, the dashboard shows your plan, live usage (records, writes, reads), your export schedule, and every table in your database:

![The connected FlowMattic Tables dashboard](https://assets.infidesk.support/products/flowmattic/kb-images/tables/03-dashboard.png)

## Step 3 — Create your first table

Click **Create table**. Give the table a name (letters, numbers, underscores — spaces become underscores) and define your fields. Every table automatically gets `id`, `created_at`, and `updated_at` columns.

![Create table — fields with types, including a dropdown with option chips](https://assets.infidesk.support/products/flowmattic/kb-images/tables/04-create-table.png)

Choosing **Dropdown** (or **Tags**) for a field reveals its option chips right under the row. Click **Edit options** to configure them — each option gets a label and a color:

![Dropdown options editor — label and color per option](https://assets.infidesk.support/products/flowmattic/kb-images/tables/05-dropdown-options.png)

> **Tip:** If you skip the options editor, FlowMattic seeds the column with three example options so it works immediately — you can rename them any time from the table view.

## Step 4 — Work with your data in the grid

Open any table to get the full grid: sort, filter, and search from the column menus, and **double-click any cell to edit it inline**. Typed columns render the way you'd expect — status pills with colors, star ratings, progress bars, people with avatars, file lists, clickable links:

![The table grid — typed columns with inline editing](https://assets.infidesk.support/products/flowmattic/kb-images/tables/06-table-grid.png)

## Step 5 — Add columns, including premium types

Use **Add column** to grow your table. Alongside the standard types, FlowMattic Tables includes premium column types: **Currency**, **Person**, **Tags**, **Files**, **Calculate** (formulas), **Relation** (link rows across tables), **AI text**, **Percent**, **Phone**, **URL**, **Color**, and automatic **Created by / Modified by** user attribution:

![Add column — premium types like Person](https://assets.infidesk.support/products/flowmattic/kb-images/tables/07-add-column.png)

> **Note:** Created by and Modified by are stamped automatically by FlowMattic and can't be edited — they're an audit trail of who added and last changed each row.

## Next steps

- [Import a CSV into FlowMattic Tables](/flowmattic/kb/import-a-csv-into-flowmattic-tables)
- [Use FlowMattic Tables in your workflows](/flowmattic/kb/use-flowmattic-tables-in-workflows)

---

# Getting started with FlowMattic Tables

Source: https://support.flowmattic.com/kb/article/207/getting-started-with-flowmattic-tables

FlowMattic Tables gives your site its own **managed database** — isolated to your site, provisioned in about a minute, and usable from every workflow. There are no servers to run and no overage bills: hit a plan limit and FlowMattic tells you; it never charges extra.

This guide walks you from a fresh install to your first working table.

## What you get

- A private, managed database for your site — records live outside your WordPress database, so heavy data never slows your site down.
- A spreadsheet-style grid with typed columns — text, numbers, dates, and premium types like **Person**, **Tags**, **Files**, **Currency**, **Relation**, and **AI text**.
- Workflow actions to insert, update, find, and delete rows — plus triggers that fire when rows change.
- Automatic exports and point-in-time recovery, depending on your plan.

## Step 1 — Open FlowMattic Tables and pick a plan

Go to **FlowMattic → FlowMattic Tables**. Until your site is connected, the page shows the available plans:

![FlowMattic Tables plans — Starter, Pro, and Business](https://assets.infidesk.support/products/flowmattic/kb-images/tables/01-empty-state-v2.png)

- **Starter** — 100,000 records, 250,000 writes per month, 1 export per day.
- **Pro** — 500,000 records, 2,000,000 writes per month, on-demand exports, 30-day point-in-time recovery.
- **Business** — 2,000,000 records, 10,000,000 writes per month, nightly automatic exports plus on demand, self-serve point-in-time restore.

Every plan also allows up to **500 tables** with up to **100 fields per table**. Reads are always unlimited on every plan. Switch the billing toggle to **Annual** to save — two months free on Starter and Pro, $69 off Business:

![Annual billing](https://assets.infidesk.support/products/flowmattic/kb-images/tables/02-pricing-annual-v2.png)

Click **Get started** on a plan and complete checkout. Your database is provisioned automatically — you never paste an API key. Within a minute the page switches to your dashboard.

## Step 2 — Meet your dashboard

Once connected, the dashboard shows your plan, live usage (records, writes, reads), your export schedule, and every table in your database:

![The connected FlowMattic Tables dashboard](https://assets.infidesk.support/products/flowmattic/kb-images/tables/03-dashboard.png)

## Step 3 — Create your first table

Click **Create table**. Give the table a name (letters, numbers, underscores — spaces become underscores) and define your fields. Every table automatically gets `id`, `created_at`, and `updated_at` columns.

![Create table — fields with types, including a dropdown with option chips](https://assets.infidesk.support/products/flowmattic/kb-images/tables/04-create-table.png)

Choosing **Dropdown** (or **Tags**) for a field reveals its option chips right under the row. Click **Edit options** to configure them — each option gets a label and a color:

![Dropdown options editor — label and color per option](https://assets.infidesk.support/products/flowmattic/kb-images/tables/05-dropdown-options.png)

> **Tip:** If you skip the options editor, FlowMattic seeds the column with three example options so it works immediately — you can rename them any time from the table view.

## Step 4 — Work with your data in the grid

Open any table to get the full grid: sort, filter, and search from the column menus, and **double-click any cell to edit it inline**. Typed columns render the way you'd expect — status pills with colors, star ratings, progress bars, people with avatars, file lists, clickable links:

![The table grid — typed columns with inline editing](https://assets.infidesk.support/products/flowmattic/kb-images/tables/06-table-grid.png)

## Step 5 — Add columns, including premium types

Use **Add column** to grow your table. Alongside the standard types, FlowMattic Tables includes premium column types: **Currency**, **Person**, **Tags**, **Files**, **Calculate** (formulas), **Relation** (link rows across tables), **AI text**, **Percent**, **Phone**, **URL**, **Color**, and automatic **Created by / Modified by** user attribution:

![Add column — premium types like Person](https://assets.infidesk.support/products/flowmattic/kb-images/tables/07-add-column.png)

> **Note:** Created by and Modified by are stamped automatically by FlowMattic and can't be edited — they're an audit trail of who added and last changed each row.

## Next steps

- [Import a CSV into FlowMattic Tables](/kb/import-a-csv-into-flowmattic-tables)
- [Use FlowMattic Tables in your workflows](/kb/use-flowmattic-tables-in-workflows)

---

# Give your AI Agent memory with WP Tables

Source: https://support.flowmattic.com/kb/article/238/give-your-ai-agent-memory-with-wp-tables

By default an AI Agent step is stateless. Every execution starts with no idea what was said before, so a customer who asks "and when does it arrive?" gets an agent that has never heard of their order.

**WP Tables memory** fixes that. The agent writes each exchange into a table in your WordPress database and reads it back on the next run, so a conversation can continue across separate workflow executions — and unlike the other memory options, you can open the table and see exactly what the agent remembers.

This guide covers the table you need to create, the settings, and the one mistake that makes memory look broken when it is working perfectly.

## Which memory type to use

The AI Agent offers four options under **Memory Type**:

| Type | Stored in | Survives across executions | Use when |
|---|---|---|---|
| No Memory (Stateless) | — | No | Each run is independent |
| Window Buffer Memory | WordPress transients | Only until the transient expires | Short-lived chats, no setup |
| **WP Tables** | A table in your database | **Yes, permanently** | Real conversations you want to keep and inspect |
| WordPress Options | The `wp_options` table | Yes | Small volumes only |

WP Tables is the right choice when conversations matter — support chats, multi-step assistants, anything you may want to audit later. It is the only option where the history is queryable.

> **A note on the name.** This memory type stores data in **WP Tables**, which live in your own WordPress database. It is not the managed FlowMattic Tables service. The Database dropdown lets you pick your local WordPress database or any external database you have connected.

## Step 1 — Create the memory table

Go to **FlowMattic → WP Tables** and create a table. Name it whatever you like — *AI Agent Memory* is a sensible choice.

It needs exactly four columns, all of type **Text**:

| Column name | Holds |
|---|---|
| `session_id` | Groups messages into one conversation |
| `role` | Either `user` or `assistant` |
| `content` | The message itself |
| `timestamp` | When the message was stored |

![The AI Agent Memory table in WP Tables showing the four columns with a sample conversation](https://assets.infidesk.support/products/flowmattic/kb-images/agent-memory/table-columns.png)

Three things worth knowing:

**The column names must match exactly.** `role`, `content` and `timestamp` are fixed — FlowMattic writes to those names and nothing else. Only the session column can be renamed, and if you rename it you must enter the new name in the step settings.

**FlowMattic slugifies your column labels.** Typing `Session Id` as the label produces a `session_id` column, which is what you want. Typing `Session ID Column` would produce `session_id_column`, which is not. Check the column key if you are unsure.

**Do not add an ID column.** FlowMattic adds an auto-incrementing `id` to every table it creates, and the agent relies on it to read messages back in order. You get it for free.

## Step 2 — Add memory to your agent

Open your workflow and find the **AI Agent** step. Below the step you will see three connectors: **Chat Model**, **Memory** and **Tools**. Click **Memory**.

![The AI Agent step on the canvas with the Chat Model, Memory and Tools connectors beneath it](https://assets.infidesk.support/products/flowmattic/kb-images/agent-memory/agent-node.png)

Fill in the panel:

![The Memory configuration panel with WP Tables selected](https://assets.infidesk.support/products/flowmattic/kb-images/agent-memory/memory-config.png)

- **Memory Type** — choose **WP Tables**.
- **Database** — **Local** for your WordPress database, or an external database you have connected.
- **Table Name** — pick the table you just created. Use the refresh button beside it if the table does not appear.
- **Session ID Column** — leave as `session_id` unless you named the column something else.
- **Max History Length** — see below. Default is 20.
- **Session Identifier** — the important one. See the next step.

Select **Save & Close**.

## Step 3 — Set the Session Identifier

**This is the setting that decides whether memory works at all.**

The session identifier is what ties messages together into one conversation. Leave it empty and FlowMattic generates a fresh one on every execution — so the agent writes rows perfectly, then never reads them back, because the next run is looking under a different identifier. The table fills up, the agent behaves as though it has no memory, and nothing appears to be wrong.

Set it to something stable for the conversation you are tracking:

- **A value from the trigger** — `{{Webhook.session_id}}`, `{{Webhook.chat_id}}`, `{{Webhook.email}}`. Best for chat widgets and messaging integrations, where the sender already has an identifier.
- **A customer or order identifier** — `{{Webhook.customer_id}}`. Good for support workflows, so a customer's history follows them across separate tickets.
- **A static value** — a single ongoing conversation, useful for testing.

Pick something that is stable for the same conversation and different for different ones. An email address works well; a timestamp does not.

## How Max History Length actually behaves

The field says "maximum number of messages", but it counts **exchanges**, not messages. Each exchange is one user message plus one assistant reply.

So the default of **20 loads 40 messages** — the last 20 exchanges. If you set it to 5 you get 10 messages.

This matters for cost. Every remembered message is re-sent to the model on every run, so a long history makes each call slower and more expensive. Start at 10 and raise it only if the agent visibly loses the thread.

## What gets stored

One row per message, two per exchange:

| id | session_id | role | content | timestamp |
|---|---|---|---|---|
| 1 | demo-cust-4821 | user | Hi, I ordered a desk lamp last week. Where is it? | 2026-08-04 11:02:14 |
| 2 | demo-cust-4821 | assistant | Order #4821 shipped on Tuesday and is due Thursday. | 2026-08-04 11:02:16 |
| 3 | demo-cust-4821 | user | Can I change the delivery address? | 2026-08-04 11:03:01 |
| 4 | demo-cust-4821 | assistant | Not once it has shipped, but I can request a redirect. | 2026-08-04 11:03:04 |

Because it is an ordinary table, you can read it, filter it, export it, or build a workflow that acts on it — for example, deleting rows older than 90 days.

FlowMattic will not write the same exchange twice. If a workflow re-runs with an identical user message and assistant reply in the same session, the duplicate is skipped rather than appended.

## Housekeeping

The table grows with every exchange and nothing prunes it automatically. **Max History Length** limits how much is *read*, not how much is *kept*.

For a busy agent, add a scheduled workflow that clears old rows — a Schedule trigger plus a WP Tables step deleting rows where `timestamp` is older than your retention window. Conversation content often counts as personal data, so keep only what you need.

## Troubleshooting

**The agent does not remember anything, but rows are being written**
The Session Identifier is empty or changes between runs. This is by far the most common cause. Set it to a stable value from your trigger data.

**Nothing is written to the table at all**
Check that Memory Type is **WP Tables**, that a table is selected, and that the workflow actually reached the agent step. Memory is skipped entirely when no session identifier can be resolved.

**Some messages appear, but the agent still forgets older ones**
Working as intended — Max History Length is limiting how far back it reads. Raise it.

**Rows are written but the agent errors when reading**
Usually a column name mismatch. Confirm the table has `role`, `content` and `timestamp` spelled exactly that way, and that the Session ID Column setting matches your actual column key.

**Two different customers see each other's history**
Their session identifiers collide. Make sure the value is unique per conversation — a customer ID or email, not a workflow name or static string.

## A working example

A support chat that remembers each customer:

1. **Webhook** trigger receives `email` and `message` from your chat widget.
2. **AI Agent** step with Memory configured:
   - Memory Type: WP Tables
   - Table: AI Agent Memory
   - Session Identifier: `{{Webhook.email}}`
   - Max History Length: 10
3. **Webhook Response** returns the agent's reply to the widget.

Each customer's history is keyed to their email, so their second message arrives with the previous ten exchanges already in context — and you can open the table at any time to see exactly what the agent knows.

---

# How FlowMattic Workflows Run Asynchronously in the Background?

Source: https://support.flowmattic.com/kb/article/108/how-flowmattic-workflows-run-asynchronously-in-the-background

When you create a workflow in FlowMattic, you might wonder: *Does this slow down my website or checkout process?* The answer is: **mostly asynchronous**, but it depends on the type of trigger being used.

FlowMattic is designed to execute workflows in the background for optimal performance. However, some WordPress plugin–based triggers may briefly run synchronously before completing. Let’s break this down.

---

## What Does Asynchronous Execution Mean?

* **Asynchronous**: Tasks are triggered and handled in the background without blocking the main process.
* **Synchronous**: Tasks are executed step by step within the same process, potentially delaying the original action.

By default, FlowMattic aims to run workflows asynchronously — but WordPress’s own hook system can sometimes make things run in the same PHP session.

---

## Case 1: WooCommerce Order Paid Trigger (Asynchronous)

Example workflow:

* **Trigger**: WooCommerce Order Paid
* **Actions**:

  * Add customer to FluentCRM
  * Send order details to Google Sheets
  * Notify your team on Slack

In this case, FlowMattic continues executing the workflow step by step right after WooCommerce fires the action of order paid. This does not add any delay to the order processing while the workflow continues its execution.

---

## Case 2: WordPress Plugin–Based Triggers (Partially Synchronous)

Some triggers rely on **WordPress action hooks** that expect a response before the page load or request is completed. For example:

* **Trigger**: Form submission from a plugin (e.g., WPForms, Contact Form 7)
* **Actions**:

  * Add data to Google Sheets
  * Send a webhook to an external service

Here’s what happens:

* The workflow runs in the same PHP session as the form submission.
* This means the form processing waits a few seconds until the workflow finishes.
* Typically, this adds only a **2–5 second delay** and then the session completes.

### How to Make These Workflows Fully Asynchronous

If you want the workflow to run completely in the background:

* Add a **“Delay” step of 1 minute** right after the trigger.
* This ensures the trigger is captured immediately, then the workflow continues in the background queue without blocking the main process.

---

## Case 3: Incoming Webhook Trigger (Fully Asynchronous)

When FlowMattic receives data from an external app via a webhook:

* The webhook immediately acknowledges receipt to the external service.
* The full workflow runs in the background, independent of the sending system.

This ensures fast acknowledgment and smooth execution for your automations.

---

## Why This Matters

* ✅ **Improved Performance**: Most workflows run in the background, so your site stays fast.
* ✅ **Scalability**: Handles many triggers without slowing down WordPress.
* ✅ **Flexibility**: Even in synchronous cases, you can configure a simple delay to make them asynchronous.

---

## Technical Notes

* Workflows use **WordPress background processes** (via WP Cron or system cron).
* Plugin-based triggers may briefly run synchronously but are short-lived (per PHP session).
* Adding a **Delay** step right after the trigger is the best practice for ensuring async execution.

---

## FAQ

**Q1. Why does my form take a few seconds longer to submit when a workflow is running?**
This happens because some WordPress plugin triggers run synchronously. The form waits until the workflow completes in that PHP session, usually only a **2–5 second delay**. To avoid this, add a **1-minute Delay step** after the trigger.

**Q2. Will asynchronous workflows slow down my WooCommerce checkout?**
No. WooCommerce order triggers are handled asynchronously, so your checkout remains smooth and fast. The workflow runs in the background while WooCommerce processes the order normally.

**Q3. If I use Webhooks, will the sending service have to wait until the workflow finishes?**
No. Webhooks are fully asynchronous. FlowMattic immediately acknowledges receipt, and the rest of the workflow runs in the background.

**Q4. Do I need to set up Cron for asynchronous workflows to work reliably?**
Yes. For the best performance, we recommend setting up a proper **server-level system cron**. WordPress’s built-in WP-Cron works too, but a system cron ensures more reliable background task execution.

**Q5. Can I control how long workflows take to run?**
Workflow speed depends on the number of steps and the response time of external apps. Even in asynchronous mode, heavy workflows may take a few extra seconds, but this won’t affect your website visitors or sending apps.

---

## Summary

FlowMattic workflows are **asynchronous by design**, but some WordPress plugin triggers can run synchronously for a few seconds due to how WordPress hooks work. If you want to avoid even that small delay, simply add a **1-minute Delay step after the trigger** to shift the rest of the workflow fully into the background.

Whether triggered by **WooCommerce**, **webhooks**, or other apps, FlowMattic ensures your automations run reliably and efficiently.

---

# How to Add MCP Tools in FlowMattic MCP Server

Source: https://support.flowmattic.com/kb/article/91/how-to-add-mcp-tools-in-flowmattic-mcp-server

MCP (Model Context Protocol) tools are the building blocks that enable AI assistants to interact with your WordPress site and external services. This comprehensive guide will walk you through creating different types of tools in your FlowMattic MCP server.

## Overview

FlowMattic MCP Server supports five main types of tools, each designed for specific use cases:

- **PHP Function Tools**: Execute custom WordPress functions via the admin interface
- **Workflow Tools**: Trigger FlowMattic workflows
- **API Endpoint Tools**: Make HTTP requests to external services
- **Database Query Tools**: Run SQL queries against your database
- **Developer Tools**: Programmatically added by plugins and themes

## Getting Started

### Prerequisites

Before creating MCP tools, ensure:
- FlowMattic plugin is installed and activated
- Your MCP server is active (green status indicator)
- You have the necessary permissions to manage MCP tools
- For developer tools: Basic PHP knowledge and plugin/theme development experience

### Accessing the Tool Creation Interface

1. Navigate to **FlowMattic > MCP Server** in your WordPress admin
2. Click the **"Add New Tool"** button in the header or tools section
3. The tool creation modal will open

![MCP Server ‹ FlowMattic — WordPress 2025-07-27 at 5.21.07 AM.png](/storage/kb-images/2994828f5f-inline.png)


## Creating PHP Function Tools

PHP Function tools execute custom WordPress functions when called by MCP clients through the admin interface.

### When to Use PHP Functions
- Custom business logic that doesn't require a full plugin
- WordPress data retrieval for specific use cases
- User management operations
- Custom calculations or processing
- Quick prototyping of functionality

### Step-by-Step Creation

1. **Set Basic Information**
   - Enter a descriptive **Tool Name** (e.g., "Get User Details", "Calculate Tax")
   - Select **"PHP Function"** as the execution method
   - Add a clear **Description** explaining the function's purpose and expected output

![MCP Server ‹ FlowMattic — WordPress 2025-07-27 at 5.22.53 AM.png](/storage/kb-images/7c08d74fcf-inline.png)

2. **Configure PHP Function Settings**
   - **Function Name**: Enter the exact name of your PHP function (must be callable)
   - **Parameters Request Type**: Choose how parameters are passed:
     - **Individual Parameters**: Each parameter passed separately to function
     - **Array**: All parameters passed as a single associative array

3. **Define Input Parameters**
   - Click **"Add Parameter"** to define each input the function expects
   - Use lowercase with underscores (e.g., `user_id`, `search_term`, `start_date`)
   - Parameter names are automatically formatted as you type
   - Add all parameters your function requires

4. **Save the Tool**
   - Click **"Save Tool"** to create your PHP function tool
   - The tool will appear in your tools list immediately
   - Test the tool to ensure it works correctly

### PHP Function Example

```php
// Example function that gets user data
function get_user_details_by_id($user_id) {
    // Validate input
    if (empty($user_id) || !is_numeric($user_id)) {
        return array('error' => 'Invalid user ID provided');
    }
    
    $user = get_userdata($user_id);
    
    if (!$user) {
        return array('error' => 'User not found');
    }
    
    return array(
        'success' => true,
        'data' => array(
            'id' => $user->ID,
            'username' => $user->user_login,
            'email' => $user->user_email,
            'display_name' => $user->display_name,
            'role' => $user->roles[0] ?? 'subscriber'
        )
    );
}

// Array-based function example
function process_user_data($input_array) {
    $user_id = $input_array['user_id'] ?? '';
    $action = $input_array['action'] ?? '';
    
    // Process based on action
    switch ($action) {
        case 'get_posts':
            return get_user_posts($user_id);
        case 'get_meta':
            return get_user_metadata($user_id);
        default:
            return array('error' => 'Invalid action specified');
    }
}
```

### Parameter Handling

**Individual Parameters** (default):
- Function receives: `get_user_details_by_id("123")`
- Use when function expects separate arguments
- Most common for simple functions

**Array Parameters**:
- Function receives: `get_user_details_by_id(array("user_id" => "123"))`
- Use when function expects a single array parameter
- Better for complex functions with many optional parameters

### Function Requirements
- Function must be globally accessible (defined in active theme or plugin)
- Should include proper error handling and validation
- Must return data (arrays are automatically JSON-encoded)
- Should follow WordPress coding standards

## Creating Workflow Tools

Workflow tools execute FlowMattic workflows when triggered by MCP clients.

### When to Use Workflows
- Complex automation sequences
- Multi-step processes involving multiple services
- Integration with external platforms
- Email notifications and alerts
- Data synchronization tasks

### Step-by-Step Creation

1. **Set Basic Information**
   - Enter a descriptive **Tool Name** (e.g., "Send Notification Email", "Sync Customer Data")
   - Select **"Workflow"** as the execution method
   - Describe what the workflow accomplishes and expected outcomes

![MCP Server ‹ FlowMattic — WordPress 2025-07-27 at 5.24.46 AM.png](/storage/kb-images/9a854ef283-inline.png)

2. **Select Target Workflow**
   - Choose from the **"Workflow to Execute"** dropdown
   - Only published and active workflows appear in the list
   - Workflows must be properly configured and tested beforehand

3. **Configure Parameters**
   - Add parameters that will be passed to the workflow as trigger data
   - Parameters are available in the workflow using dynamic data tags
   - Use descriptive parameter names that match workflow expectations

4. **Save the Tool**
   - Click **"Save Tool"** to create the workflow tool
   - Test the tool to ensure the workflow executes correctly
   - Monitor workflow execution logs for any issues

### Workflow Best Practices

- **Pre-test Workflows**: Ensure workflows are fully functional before creating MCP tools
- **Error Handling**: Include error steps in workflows for graceful failure handling
- **Clear Documentation**: Document workflow purpose and expected parameters
- **Version Control**: Keep track of workflow changes that might affect MCP tools
- **Performance**: Optimize workflows for quick execution when called via MCP

## Creating API Endpoint Tools

API Endpoint tools make HTTP requests to external services, perfect for integrating with third-party APIs.

### When to Use API Endpoints
- Third-party service integration (CRM, marketing tools, etc.)
- External data retrieval (weather, stock prices, etc.)
- Webhook notifications to external systems
- REST API interactions
- Microservice communication

### Step-by-Step Creation

1. **Set Basic Information**
   - Enter a descriptive **Tool Name** (e.g., "Get Weather Data", "Create CRM Contact")
   - Select **"API Endpoint"** as the execution method
   - Describe the API's purpose, expected response, and any limitations

![Zight 2025-07-27 at 5.25.40 AM.png](/storage/kb-images/c7f9db358b-inline.png)

2. **Configure API Settings**
   - **API Endpoint**: Enter the complete URL (e.g., `https://api.example.com/v1/weather`)
   - **HTTP Method**: Select GET, POST, PUT, or DELETE based on API requirements
   - **Choose Connect**: Select authentication method
   - **Headers**: Add JSON-formatted headers if required by the API
   - **Webhook URL**: Optional FlowMattic webhook URL for async processing

3. **Authentication Setup**
   - **None**: No authentication required (public APIs)
   - **FlowMattic Connect**: Use pre-configured authentication
     - Select from existing connects (OAuth2, API keys, Basic Auth, etc.)
     - FlowMattic handles token management and refresh automatically
     - Ideal for APIs requiring complex authentication

4. **Configure Headers (Optional)**
   ```json
   {
     "Authorization": "Bearer your-static-token-here",
     "Content-Type": "application/json",
     "User-Agent": "FlowMattic-MCP/1.0",
     "Accept": "application/json"
   }
   ```

5. **Add Input Parameters**
   - Define parameters that will be sent with the API request
   - Parameters can be included in URL path, query string, or request body
   - Use parameter names that match API documentation
   - Consider optional vs required parameters

6. **Save the Tool**
   - Click **"Save Tool"** to create the API endpoint tool
   - Test with your MCP client to verify functionality
   - Monitor API response times and error rates

### API Tool Examples

**GET Request Example**: Weather API
```
Endpoint: https://api.openweathermap.org/data/2.5/weather
Method: GET
Parameters: city, api_key, units
Headers: None required
```

**POST Request Example**: Create User in CRM
```
Endpoint: https://api.crm.com/v1/contacts
Method: POST
Parameters: name, email, phone, company
Headers: {"Authorization": "Bearer token", "Content-Type": "application/json"}
```

**PUT Request Example**: Update Product
```
Endpoint: https://api.ecommerce.com/products/{product_id}
Method: PUT
Parameters: product_id, name, price, description
Authentication: FlowMattic Connect (OAuth2)
```

### API Best Practices
- **Rate Limiting**: Be aware of API rate limits and implement appropriate delays
- **Error Handling**: Handle API errors gracefully and return meaningful messages
- **Data Validation**: Validate parameters before sending to external APIs
- **Security**: Never expose API keys in tool descriptions or names
- **Documentation**: Keep API documentation handy for troubleshooting

## Creating Database Query Tools

Database Query tools execute SQL queries directly against your WordPress database.

### When to Use Database Queries
- Complex data retrieval that WP_Query can't handle efficiently
- Reporting and analytics requiring JOIN operations
- Custom search functionality across multiple tables
- Data aggregation and statistical analysis
- Performance-critical queries

⚠️ **Security Warning**: Database queries can be powerful but potentially dangerous. Use with extreme caution and proper validation.

### Step-by-Step Creation

1. **Set Basic Information**
   - Enter a descriptive **Tool Name** (e.g., "Search Posts by Content", "User Activity Report")
   - Select **"Database Query"** as the execution method
   - Clearly describe what data the query retrieves and any limitations

![MCP Server ‹ FlowMattic — WordPress 2025-07-27 at 5.27.04 AM.png](/storage/kb-images/3d19bdd1dc-inline.png)

2. **Write Your SQL Query**
   - Enter your SQL query in the provided text area
   - Use parameterized queries for security (required)
   - Test queries in phpMyAdmin or similar tool first
   - Include appropriate LIMIT clauses

3. **Use Dynamic Parameters**
   - Use `:parameter_name` syntax for dynamic values
   - Example: `SELECT * FROM wp_posts WHERE post_content LIKE '%:search_term%'`
   - Parameters are automatically sanitized and replaced at runtime
   - Never concatenate user input directly into queries

4. **Define Input Parameters**
   - Add parameters that correspond to your query placeholders
   - Ensure parameter names match exactly (without the colon)
   - Provide clear descriptions for each parameter

5. **Save the Tool**
   - Click **"Save Tool"** to create the database query tool
   - Test thoroughly with safe queries first
   - Monitor query performance and execution time

### Database Query Examples

**Basic Search Query**:
```sql
SELECT ID, post_title, post_excerpt, post_date 
FROM wp_posts 
WHERE post_status = 'publish' 
  AND post_type = 'post'
  AND (post_title LIKE '%:search_term%' OR post_content LIKE '%:search_term%')
ORDER BY post_date DESC
LIMIT 20
```

**User Posts with Meta Query**:
```sql
SELECT p.ID, p.post_title, p.post_date, u.display_name,
       GROUP_CONCAT(pm.meta_value) as tags
FROM wp_posts p
JOIN wp_users u ON p.post_author = u.ID
LEFT JOIN wp_postmeta pm ON p.ID = pm.post_id AND pm.meta_key = 'tags'
WHERE p.post_author = :user_id
  AND p.post_status = 'publish'
  AND p.post_date >= ':start_date'
GROUP BY p.ID
ORDER BY p.post_date DESC
LIMIT :limit_count
```

**Analytics Query**:
```sql
SELECT 
    DATE(post_date) as publish_date,
    COUNT(*) as posts_count,
    AVG(CHAR_LENGTH(post_content)) as avg_content_length
FROM wp_posts 
WHERE post_status = 'publish' 
  AND post_type = 'post'
  AND post_date >= ':start_date'
  AND post_date <= ':end_date'
GROUP BY DATE(post_date)
ORDER BY publish_date DESC
```

### Database Security Best Practices

- **Always Use Parameters**: Never concatenate user input into queries
- **Limit Scope**: Use WHERE clauses to restrict data access
- **Avoid SELECT \***: Specify only needed columns
- **Use LIMIT**: Prevent large result sets that could impact performance
- **Read-Only Access**: Avoid UPDATE, DELETE, or INSERT operations
- **Test Safely**: Test all queries in development environment first
- **Monitor Performance**: Track query execution time and optimize slow queries

## Understanding Developer Tools (Plugin/Theme Integration)

Developer tools are programmatically added by WordPress plugins and themes, rather than created through the admin interface. These tools appear automatically in your MCP server when plugins register them using FlowMattic's developer API.

### How Developer Tools Appear in Admin

**Visual Identification**: Developer tools are distinguished in the admin interface by:
- **Plugin Badge**: Shows the source plugin/theme name
- **Read-Only Status**: Cannot be edited or deleted through admin interface
- **Source Attribution**: Clearly marked as originating from external code

![MCP Server ‹ FlowMattic — WordPress 2025-07-27 at 5.27.48 AM.png](/storage/kb-images/0966d658f8-inline.png)

**Available Actions**: For developer tools, you can only:
- **View Tool History**: See execution logs and performance metrics
- **Monitor Usage**: Track how often the tool is called
- **Review Configuration**: See tool details (but cannot modify)

### How Developer Tools Work
- Tools are registered using PHP code in plugins/themes
- No admin interface interaction required for creation
- Tools appear automatically when plugins are activated
- Managed entirely through the originating plugin/theme code
- Support both simple and complex functionality

### Tool Management
- **Updates**: Tool modifications must be made in the plugin/theme code
- **Removal**: Tools are removed when the plugin is deactivated/removed
- **Debugging**: Use tool history to monitor performance and errors

### When Plugins Use Developer Tools
- Expose plugin-specific functionality to AI assistants
- Provide theme-related automation capabilities
- Integrate complex business logic with MCP clients
- Enable advanced WordPress operations through AI

### For Developers
If you're a plugin or theme developer interested in adding MCP tools to your code, see the comprehensive [FlowMattic MCP Server: Developer Integration Guide](https://support.flowmattic.com/kb/article/89/) for complete implementation details, code examples, and best practices.

## Parameter Configuration

### Parameter Naming Rules
- Use lowercase letters, numbers, and underscores only
- Start with a letter, not a number
- Be descriptive but concise
- Use consistent naming across related tools
- Examples: `user_id`, `search_term`, `start_date`, `limit_count`

### Parameter Validation
- **Client-side**: Basic validation happens automatically in MCP clients
- **Server-side**: Always validate and sanitize in your functions/workflows
- **Required vs Optional**: Clearly document which parameters are required

```php
function validate_parameters( $params ) {
    $errors = array();
    
    // Required parameter check
    if ( empty( $params['user_id'] ) ) {
        $errors[] = 'user_id is required';
    }
    
    // Type validation
    if ( isset( $params['limit'] ) && ! is_numeric( $params['limit'] ) ) {
        $errors[] = 'limit must be a number';
    }
    
    // Range validation
    if ( isset( $params['page'] ) && ( $params['page'] < 1 || $params['page'] > 100 ) ) {
        $errors[] = 'page must be between 1 and 100';
    }
    
    return $errors;
}
```

## Testing Your Tools

### Pre-Deployment Testing

1. **Function Testing**: Test PHP functions independently
```php
// Test in WordPress admin or via WP-CLI
$result = your_function_name( 'test_value' );
var_dump( $result );
```

2. **Parameter Testing**: Verify parameter handling
```php
// Test different parameter combinations
$test_cases = array(
    array( 'user_id' => '1' ),
    array( 'user_id' => 'invalid' ),
    array(), // Missing parameters
);

foreach ( $test_cases as $params ) {
    $result = your_function( $params );
    echo "Input: " . json_encode( $params ) . "\n";
    echo "Output: " . json_encode( $result ) . "\n\n";
}
```

3. **Error Handling Testing**: Test edge cases and error conditions

### MCP Client Testing

1. **Connect MCP Client**: Use Claude Desktop, VS Code, or another client
2. **Tool Discovery**: Verify tools appear in the client
3. **Execution Testing**: Test tools with various inputs
4. **Performance Testing**: Monitor response times
5. **Error Testing**: Test with invalid inputs

### Common Testing Scenarios

**Valid Input Test**:
```
Ask Claude: "Use the Get User Details tool to get information for user ID 1"
Expected: Valid user data returned
```

**Invalid Input Test**:
```
Ask Claude: "Use the Get User Details tool with user ID 'invalid'"
Expected: Clear error message about invalid user ID
```

**Missing Parameter Test**:
```
Ask Claude: "Use the Get User Details tool without providing a user ID"
Expected: Error message about missing required parameter
```

**Performance Test**:
```
Ask Claude: "Get details for users 1, 2, 3, 4, and 5 using the user details tool"
Expected: Reasonable response time for multiple calls
```

### Debugging Common Issues

**Tool Not Appearing in Client**:
- ✅ Verify server is active (green status)
- ✅ Check tool was saved successfully
- ✅ Refresh MCP client connection
- ✅ Check for JavaScript console errors

**Function Not Found Errors**:
- ✅ Ensure PHP function exists and is accessible
- ✅ Check function name spelling exactly
- ✅ Verify function is defined in active theme/plugin
- ✅ Test function independently in WordPress

**Parameter Errors**:
- ✅ Verify parameter names match exactly
- ✅ Check parameter formatting (lowercase_underscore)
- ✅ Ensure required parameters are provided
- ✅ Test parameter type conversion

**Performance Issues**:
- ✅ Monitor execution time in tool history
- ✅ Optimize database queries with EXPLAIN
- ✅ Add caching where appropriate
- ✅ Limit result set sizes

**Authentication Errors** (API tools):
- ✅ Verify API credentials are correct
- ✅ Check FlowMattic Connect configuration
- ✅ Test API endpoint independently
- ✅ Review API rate limits

## Tool Management

### Editing Existing Tools
1. Locate the tool in your tools list
2. Click the three-dot menu on the tool card
3. Select **"Edit Tool"**
4. Modify settings as needed
5. Click **"Update Tool"** to save changes

*Note: Plugin/theme tools cannot be edited through the admin interface - they must be modified in code.*

### Duplicating Tools
- Use the **"Duplicate"** option to create similar tools quickly
- Modify the duplicate as needed
- Useful for creating variations with different parameters
- Great for testing new configurations

### Monitoring Tool Usage
- Click **"Tool History"** to view execution logs
- Monitor success rates and performance metrics
- Identify frequently used tools for optimization
- Track error patterns for debugging

### Tool Organization
- Use consistent naming conventions
- Group related tools with similar prefixes
- Document tool purposes in descriptions
- Archive unused tools to reduce clutter

## Advanced Features

### Error Handling Best Practices

**Structured Error Responses**:
```php
// Good error response structure
return array(
    'success' => false,
    'error' => 'User not found',
    'error_code' => 'USER_NOT_FOUND',
    'details' => array(
        'user_id' => $user_id,
        'timestamp' => current_time( 'mysql' )
    )
);
```

**Success Response Structure**:
```php
// Consistent success response
return array(
    'success' => true,
    'data' => $result_data,
    'message' => 'Operation completed successfully',
    'meta' => array(
        'execution_time' => $execution_time,
        'timestamp' => current_time( 'mysql' )
    )
);
```

### Async Processing (API Tools)

For long-running operations, use webhook URLs:

```php
// In your API endpoint configuration
$webhook_url = 'https://yoursite.com/wp-json/flowmattic/v1/webhook/your-endpoint';

// The API tool will:
// 1. Return immediate acknowledgment
// 2. Process data asynchronously  
// 3. Send results to webhook when complete
```

## Best Practices Summary

### Tool Design
- **Single Responsibility**: Each tool should have one clear purpose
- **Descriptive Names**: Use action-oriented, clear names
- **Comprehensive Descriptions**: Help AI understand when and how to use tools
- **Consistent Parameters**: Use standard naming across related tools
- **Error Messages**: Provide clear, actionable error messages

### Development
- **Input Validation**: Always validate and sanitize inputs in your functions
- **Error Handling**: Return structured error responses with helpful messages
- **Testing**: Test tools thoroughly before deploying to production
- **Documentation**: Keep clear documentation of tool purposes and parameters

### Maintenance
- **Monitor Usage**: Regular review of execution history and performance
- **Keep Updated**: Maintain tools as requirements change
- **Optimize Performance**: Review and optimize slow-running tools
- **Version Control**: Track changes to tool configurations

## Troubleshooting Guide

### Server Issues
**Problem**: MCP Server not responding
- Check server status (should be green/active)
- Verify WordPress site is accessible
- Check for plugin conflicts
- Review server error logs

**Problem**: Tools not appearing in clients
- Refresh MCP client connection
- Verify tools are saved correctly
- Check server URL configuration
- Ensure server is active

### Tool Execution Issues
**Problem**: PHP function not found
- Verify function exists in active theme/plugin
- Check function name spelling
- Ensure function is globally accessible
- Test function independently

**Problem**: Database query errors
- Validate SQL syntax
- Check parameter placeholders
- Verify table names and structure
- Test query in database management tool

**Problem**: API endpoint failures
- Verify endpoint URL is correct
- Check authentication credentials
- Review API rate limits
- Test endpoint independently

### Performance Problems
**Problem**: Slow tool execution
- Review database query efficiency
- Check for unnecessary data processing
- Implement caching where appropriate
- Monitor server resource usage

**Problem**: Timeouts
- Optimize long-running operations
- Implement async processing for heavy tasks
- Increase server timeout limits if necessary
- Break large operations into smaller chunks

## Next Steps

After creating and configuring your MCP tools:

1. **Test Thoroughly**: Verify all tools work as expected with various inputs
2. **Document Usage**: Create internal documentation for tool purposes and parameters
3. **Monitor Performance**: Regular review of execution history and performance metrics
4. **User Training**: Educate team members on available tools and their capabilities
5. **Iterate and Improve**: Refine tools based on usage patterns and feedback
6. **Security Review**: Regular security audits of tool configurations and permissions

## Related Resources

- [Understanding MCP Server Admin Screen](https://support.flowmattic.com/kb/article/90) - Complete guide to the admin interface
- [FlowMattic MCP Server: Developer Integration Guide](https://support.flowmattic.com/kb/article/89/) - Detailed developer documentation
- [FlowMattic Connect Documentation](https://support.flowmattic.com/kb/article/4) - Setting up FlowMattic Connects

With these tools properly configured and tested, your MCP server becomes a powerful automation hub that bridges AI assistants with your WordPress site and external services, enabling sophisticated workflow automation and integration capabilities.

---

# How to Add Multiple Repeater Field Items to a Voxel Post using FlowMattic

Source: https://support.flowmattic.com/kb/article/68/how-to-add-multiple-repeater-field-items-to-a-voxel-post-using-flowmattic

With FlowMattic’s powerful automation builder, you can easily loop through a JSON array of repeater field data and dynamically add each item to a Voxel post's Repeater Field—all in one workflow. This eliminates the need to manually add items one by one.

This guide will walk you through how to set it up step by step, using:

- Webhooks to receive data
- Iterator to loop through each repeater item
- Voxel integration to add the item to the selected post

![Repeater Field Items to a Voxel Workflow](/storage/kb-images/4f9cd46ba2-inline.png)

---

## 🗂️ What You’ll Need

- A **Voxel-powered WordPress site**
- A **Repeater Field** configured for a post type in Voxel
- FlowMattic installed and connected
- A **JSON payload** like the following:

```json
{
  "post_id": "32354",
  "repeaterData": [
    { "firstName": "Valeria", "status": "Waiting" },
    { "firstName": "Shelby", "status": "In-progress" }
  ]
}
```

---

## 🔗 Step 1: Capture Webhook with JSON Array Input

### 1.1 Add Webhook Trigger

- In your FlowMattic workflow, select **"Webhooks by FlowMattic"** as the trigger.
- Choose **"Capture Webhook Response"**.

### 1.2 Enable Simple Response

- When configuring the webhook, **enable the “Simple Response” toggle**.
- This makes sure the JSON array (`repeaterData`) is not deeply nested and can be directly passed to the Iterator step.
 

### 1.3 Test the Webhook

- Send a test request to the webhook URL using Postman, Curl, or your app.
- Sample Payload:

```json
{
  "post_id": "32354",
  "repeaterData": [
    { "firstName": "Valeria", "status": "Waiting" },
    { "firstName": "Shelby", "status": "In-progress" }
  ]
}
```

- You should now see the `post_id` and `repeaterData` inside the webhook response panel.

---

## 🔁 Step 2: Use Iterator to Loop Through Repeater Data

### 2.1 Add Iterator Module

- Add a new step in your workflow and choose the **Iterator by FlowMattic** module.
- This module loops through each item in a JSON array, allowing you to process them individually.

### 2.2 Configure Iterator

- In the “Iteration Array” field, select `repeaterData` from the captured webhook response.
- This tells FlowMattic to loop through every object inside the array.

- `firstName`
- `status`
- ...and other fields if required.

**Example: **

![Iterator Configuration](/storage/kb-images/e347c1673e-inline.png)


### 2.3 Test the Iterator

- Click **Next** until you reach the **Test** tab.
- Click **Test Action** to simulate the first item in the loop.
- This will generate a sample item that will be used to configure future steps.

![Iterator Step Response](/storage/kb-images/ae4d50b447-inline.png)

---

## 🧱 Step 3: Add Voxel - Add Repeater Field Item Action

### 3.1 Add Voxel Step

- Add a new step in the workflow and select **Voxel** as the app.
- Choose the action **“Add Repeater Field Item”**.

### 3.2 Configure Voxel Action

#### Post ID

- In the **Post ID** field, select the value from the Webhook response:
  ```
  {{webhook1.post_id}}
  ```

#### Post Type

- Choose the appropriate **Post Type** in which the repeater field is registered.

#### Repeater Fields Mapping

- Once the Post Type is selected, the Repeater Fields panel will auto-populate.
- Map each field using the values from the Iterator step:

| Repeater Field Label | Map From Iterator |
|----------------------|-------------------|
| `Field Item: Name`   | `{{iterator2.firstName}}` |
| `Field Item: Status` | `{{iterator2.status}}`   |


![Repeater fields mapping](/storage/kb-images/ddf4d7b8a7-inline.png)

---

## 🧪 Step 4: Test Voxel Action

- Click **Continue** to move to the **Test** tab.
- Click **Test Action**.

You should receive a successful response:

```json
{
  "success": true,
  "message": "Repeater field item added successfully",
  "post_id": 32354,
  "repeater": [
    { "name": "Valeria", "status": "Waiting" }
  ]
}
```

![Voxel add repeater field item response](/storage/kb-images/5b64d57f17-inline.png)

- This confirms the mapping and Voxel repeater insertion is working for a single item.

---

## ✅ Step 5: Make the Workflow Live & Run Full Test

### 5.1 Save and Close

- Click **Save & Close** on the Voxel step.

### 5.2 Make the Workflow Live

- Use the toggle to turn ON your workflow in FlowMattic.

### 5.3 Send the Full JSON Test

- Resend the full payload with multiple array items to the webhook.
- This time, the **Iterator** will loop through all array items and the **Voxel** step will be executed once per item.

![after workflow execution.png](/storage/kb-images/dfcaaec816-inline.png)

---

## 🔍 How It Works Under the Hood

- The **Webhook** step captures structured JSON data from any source—frontend form, Zapier, third-party service, etc.
- The **Iterator** processes each item in the array sequentially.
- The **Voxel action** uses the post ID and inserts one item at a time into the repeater field.
- Since this runs in automation, no manual post editing is required.

---

## 📝 Pro Tips

- You can include more fields in each repeater item, like `icon`, `url`, `role`, etc.—just ensure they are present in the JSON and mapped in the Voxel step.
- Want to add repeater items **after creating a post** in the same workflow? Just add a "Create Post" action before this and map the returned `post_id`.
- Add conditional logic if you want to limit which items should be inserted based on their values (e.g., status = active).

---

## 📌 Summary

| Component       | Role                                                                 |
|----------------|----------------------------------------------------------------------|
| Webhook        | Captures incoming JSON with `post_id` and `repeaterData` array       |
| Iterator       | Loops through each item in `repeaterData`                            |
| Voxel Action   | Inserts one item into the Repeater Field per iteration               |

---

# How to Apply the Google Sheets 2.1.0 Update with new redirect url?

Source: https://support.flowmattic.com/kb/article/121/how-to-apply-the-google-sheets-210-update-with-new-redirect-url

The Google Sheets 2.1.0 update brings a significant improvement to the authentication and token refresh mechanism. This update ensures that your Google Sheets integration uses your own site's endpoint URL for token refresh requests instead of FlowMattic's central API. This means that if our firewall previously blocked access token refresh requests, you'll no longer face authentication failures because all requests are now served directly from your website. This enhancement provides greater reliability and stability for your Google Sheets workflows.

## Step-by-Step Update Guide

Follow these steps to apply the Google Sheets 2.1.0 update to your FlowMattic installation:

### Step 1: Navigate to FlowMattic Integrations

Go to **FlowMattic → Integrations** from your WordPress admin dashboard.

### Step 2: Refresh Available Updates

Click the **refresh icon** next to the "New Workflow" button a couple of times to check for the latest integration updates.

### Step 3: Apply the Update

Once you see the update notification:
1. Switch to the **Updates** tab
2. Locate the Google Sheets integration update
3. Click the update button to install version 2.1.0

![Google Sheets integration update](/storage/kb-images/7a0176e80e-inline.png)

### Step 4: Create a New Connect

After the update is installed:
1. Navigate to **FlowMattic → Connects**
2. Click **Connect Integration** button
3. Select **Google Sheets** from the integration list
4. You'll now see a new endpoint URL in the **Callback or Redirect URL** field
5. **Copy this new URL** - you'll need it for the next step

### Step 5: Update Your Google Cloud Console Project

Now you need to add the new callback URL to your existing Google Cloud Console project:

1. Go to the [Google Cloud Console](https://console.cloud.google.com/)
2. Select your existing project (the one you created for FlowMattic)
3. Navigate to **APIs & Services → Credentials**
4. Locate your existing **OAuth 2.0 Client ID** credential
5. Click on the credential name to edit it
6. Scroll down to the **Authorized Redirect URIs** section
7. Click **+ ADD URI**
8. **Paste the new callback URL** that you copied from Step 4
9. Keep your existing redirect URI (`https://api.flowmattic.com/google/spreadsheets`) if it's still there
10. Click **Save** at the bottom of the page

**Important:** You can keep both redirect URIs (the old and new one) for a transition period if you have multiple sites or want to maintain backward compatibility.

### Step 6: Complete the Authentication

1. Return to your FlowMattic Connect configuration page
2. Copy the **Client ID** from your Google Cloud Console credential
3. Copy the **Client Secret** from your Google Cloud Console credential
4. Paste both values into the respective fields in your FlowMattic Connect
5. Click the **Save Connect and Authenticate** button
6. Complete the Google OAuth authorization flow
7. Once authenticated successfully, save your Connect

### Final Step: Update your workflows
1. Edit your workflow using the Google Sheets integration
2. Edit the Google Sheets action step and choose the new connect
3. Save the step and do a test action to confirm the working 
4. Save workflow
5. Now, you can delete the **OLD** connect to avoid the duplicate calls to renew access token, or they will conflict with each other.

## What's Changed?

After completing these steps, your Google Sheets integration will use your website's own endpoint URL for all authentication and token refresh operations. This architectural change means:

- **Improved Reliability:** No more failed token refreshes due to firewall restrictions between FlowMattic's API and Google
- **Better Control:** All API communication now flows through your own website
- **Reduced Dependencies:** Your integration is less dependent on external API endpoints
- **Enhanced Stability:** Workflows using Google Sheets will run more consistently without authentication interruptions

Your existing workflows will continue to work seamlessly with this new authentication mechanism once you complete the update process!

---

# How to Configure FlowMattic MCP Server in Cursor

Source: https://support.flowmattic.com/kb/article/75/how-to-configure-flowmattic-mcp-server-in-cursor

To configure the FlowMattic MCP Server in Curser, follow the steps below:


## Steps to Set Up:

1. **Open Cursor Settings**:
    Launch Cursor and navigate to **Preferences > Cursor Settings**.

2. **Navigate to Tools & Add MCP Server**:
  Navigate to the “**Tools & Integrations**” section and click on “**Add Custom MCP**”.


 
 ![Image_2025-07-12_at_24648_AM.jpeg](/storage/kb-images/a91531690c-inline.png)

3. **Add JSON Configuration**:
 Copy and paste the JSON configuration, replacing the placeholder URL with your actual **FlowMattic MCP Server URL**.

 
 ```json
{
  "mcpServers": {
    "FlowMattic": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://flowmattic.com/wp-json/flowmattic/v1/mcp"
      ]
    }
  }
} 
 ```

4. **Save Configuration**:
Press **CMD+S** or **CTRL+S** to save the file. The FlowMattic MCP server will be added and automatically enabled.

### Additional Tips:
- Double-check that you’re using the correct MCP URL provided by FlowMattic.
- Make sure the configuration is properly formatted to avoid any errors.
- If the server doesn't appear or function correctly, try restarting Cursor after saving the configuration.

By following these steps, you can successfully configure the FlowMattic MCP Server in Cursor and start utilizing its features.

---

# How to Configure FlowMattic MCP Server in ElevenLabs

Source: https://support.flowmattic.com/kb/article/74/how-to-configure-flowmattic-mcp-server-in-elevenlabs

### Introduction
This guide provides a step-by-step process to configure the FlowMattic MCP Server in ElevenLabs. By following these instructions, you can seamlessly integrate a FlowMattic MCP server with ElevenLabs and automate your tasks with voice agents.

### Steps to Configure FlowMattic MCP Server

1. **Access the Integrations Tab**
   - Navigate to the **Integrations** tab in ElevenLabs.
   - Click on the **New Integration** button to start setting up a new server.

2. **Set the Custom MCP Server**
   - **Enter a Name**: Provide a recognizable name for your server, such as `FlowMattic MCP`.
   - **Enter a Description (Optional)**: Include a brief description for clarity. Example: `Custom MCP server powered by FlowMattic`.
         
 ![Integrations___ElevenLabs_-_Google_Chrome_2025-07-12_at_25514_AM.jpeg](/storage/kb-images/9ffa6cd7b5-inline.png)

3. **Server Configuration**
   - **Select the Protocol**: Choose the **Streamable HTTP** option.
   - **Select Server Type**: Set the Server type as **Value**.
   - **Enter the MCP Server URL**: Provide the URL of your FlowMattic MCP server.
      
 ![Image_2025-07-12_at_24317_AM.jpeg](/storage/kb-images/1fe40dea93-inline.png)

4. **Tool Approval Mode**
   Set the tool approval mode to **No Approval** (this ensures no manual approval is required for tools).

5. **Trust Confirmation**
   Accept the trust confirmation prompt to verify that you trust this MCP server.

6. **Finalize the Configuration**
   Click on the **Add Server** button to complete the setup.
     
 ![Image_2025-07-12_at_25008_AM.jpeg](/storage/kb-images/c813da307b-inline.png)

### Additional Tips
- Ensure your MCP server URL is accurate to avoid connection issues.
- Set your system prompt in ElevenLabs voice agent to ensure accurate responses.

By following these steps, you can efficiently set up and use the FlowMattic MCP server in ElevenLabs for enhanced automation.

---

# How to Configure FlowMattic MCP Server in MindPal

Source: https://support.flowmattic.com/kb/article/79/how-to-configure-flowmattic-mcp-server-in-mindpal

### Introduction
This article offers a comprehensive, step-by-step guide to configuring the FlowMattic MCP Server in MindPal. By following these instructions carefully, you can successfully integrate the MCP server and ensure smooth operation of your AI agent.

### Steps to Configure FlowMattic MCP Server

1. **Open AI Agent Settings**
   - Navigate to the settings page of the AI agent you want to configure.
   - You can either create a new agent or choose one that already exists.

2. **Navigate to MCP Integration Settings**
   - Within your AI agent’s settings, go to the **Integrations** section.
   - Then, click on **MCPs** to view and manage your remote MCP server connections.

 
 ![Image_2025-07-14_at_70247_PM.jpeg](/storage/kb-images/8294fad7e3-inline.png)

3. **Add a New Remote MCP Server**
   - In the MCP connections area, click on the **Add New Remote MCP Server** button.This will open a form where you can enter the required server details.

 
 ![Image_2025-07-14_at_70626_PM.jpeg](/storage/kb-images/3e03391150-inline.png)

4. **Provide Server Details**
   - In the Server Name field, type a name you’d like to give this server (for example: “FlowMattic MCP”).
   - In the Server URL field, enter your actual **FlowMattic MCP Server URL**. You can find this URL inside your FlowMattic account.

 
 ![Image_2025-07-14_at_70837_PM.jpeg](/storage/kb-images/5979fc348f-inline.png)

5. **Validate the MCP Server**
   - Click the **Validate MCP Server** button to test the connection.
   - Once the Server URL is valid and the server is reachable, the connection will complete successfully, and your tools will appear under the connected MCP server.

6. **Add the MCP Server**
   - Click the **Add Server** button to complete the setup.
   - Once done, your MCP server will be created and ready to use in MindPal.

7. **Add the MCP Server**
   - Go to your AI Workforce, select your Agent, and test it using tool-based commands to ensure the MCP server is working correctly.

### Additional Tips
 Ensure your FlowMattic MCP Server is active, use a clear server name, and recheck the FlowMattic MCP Server URL if validation fails.

### Conclusion
By completing these steps, your FlowMattic MCP Server is now successfully connected to MindPal. You can start using tools via your AI agent right away.

---

# How to Configure FlowMattic MCP Server in Windsurf

Source: https://support.flowmattic.com/kb/article/76/how-to-configure-flowmattic-mcp-server-in-windsurf

To configure the FlowMattic MCP Server in Windsurf, follow the steps below:


## Steps to Set Up:

1. **Open Windsurf Settings**:
    Launch Windsurf and navigate to **Preferences > Windsurf Settings** from the application menu.

2. **Access Plugin Management**:
 Navigate to the **Cascade** section and click on **Manage Plugins** to open the plugin configuration area.

 
 ![Image_2025-07-12_at_40845_PM.jpeg](/storage/kb-images/03cfd03b7c-inline.png)

3. **Edit Raw Configuration File**:
Inside the Manage Plugins view, click on **View Raw Config**. Copy and paste the following MCP server configuration into the file, replacing the placeholder URL with your actual **FlowMattic MCP Server URL**.

 
 ```json
{
  "mcpServers": {
    "FlowMattic": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://flowmattic.com/wp-json/flowmattic/v1/mcp"
      ]
    }
  }
} 
 ```

 
 ![Image_2025-07-12_at_42041_PM.jpeg](/storage/kb-images/cfc09f9a0b-inline.png)

4. **Save Configuration**:
Press **CMD+S (Mac) **or** CTRL+S (Windows)** to save the configuration file. The FlowMattic MCP server will be added and enabled automatically.

### Additional Tips:
- Double-check that you’re using the correct MCP URL provided by FlowMattic.
- Make sure the configuration is properly formatted to avoid any errors.
- If the server doesn’t appear or function as expected, try restarting Windsurf after saving the configuration.

By following these steps, you can successfully configure the FlowMattic MCP Server in Windsurf and start utilizing its features.

---

# How to Configure FlowMattic MCP Server on Claude Desktop

Source: https://support.flowmattic.com/kb/article/78/how-to-configure-flowmattic-mcp-server-on-claude-desktop

### Prerequisites

Before you begin, ensure the following:

1. **Node.js Installation**: Verify that Node.js is installed on your machine. If not, download and install it from the official website: [https://nodejs.org](https://nodejs.org).
2. **Claude Desktop Application**: Download and install the Claude Desktop application from the official source: [Download Cloud Desktop](https://claude.ai/download).

---

### Step-by-Step Instructions

#### 1. Open the Claude Desktop Application

Launch the Claude Desktop application on your computer.

#### 2. Access the Settings

- **For Mac Users**:
  - From the top menu bar, navigate to `Claude > Settings > Developer`.
  - Click on the **Edit Config** button.

- **For Windows Users**:
  - Click on the breadcrumb menu (three horizontal lines) in the top bar.
  - Navigate to `File > Settings > Developer`.
  - Click on the **Edit Config** button.
   
 ![Image_2025-07-14_at_121803_AM.jpeg](/storage/kb-images/a6562c6408-inline.png)

#### 3. Add MCP Server Configuration

1. Open the `claude_desktop_config.json` file in any text editor of your choice.
2. Paste the following configuration code into the file. Ensure the code is correctly formatted and pasted.
     
 ```json
{
"mcpServers": {
	"FlowMattic": {
		"command": "npx",
		"args": [
			"-y",
			"mcp-remote",
			"https://your-flowmattic-mcp-url.com"
		]
	}
}} 
 ```
 
 :::Info
Note: Replace https://your-flowmattic-mcp-url.com with your actual FlowMattic MCP server URL. 
:::

#### 4. Restart Claude Desktop

- Save the changes made to the configuration file. 
- Properly exit the Claude Desktop application:
   - Navigate to `File > Exit` to ensure it closes completely.
- Then reopen Claude Desktop to apply the new settings.

#### 5. Test the Connection

1. Open a new conversation in the Claude Desktop application.
2. Use your FlowMattic tools to verify that Claude now has access to the configured MCP tools.

---

### Additional Tips

- **Backup Configuration File**: Before making any changes to the `claude_desktop_config.json` file, create a backup to avoid losing original settings.
- **Error Troubleshooting**: If the connection test fails, double-check the configuration code for syntax errors or incorrect values.
- **Regular Updates**: Keep both the Claude Desktop application and Node.js updated to ensure compatibility and optimal performance.

---

Your FlowMattic MCP Server is now successfully integrated with Claude Desktop! You can start using FlowMattic tools and workflows directly through your Claude conversations.

---

# How to Configure Global SMTP for Email module in workflow

Source: https://support.flowmattic.com/kb/article/55/how-to-configure-global-smtp-for-email-module-in-workflow

### Overview
FlowMattic's Email module enables users to send emails in workflows using either SMTP or the PHP mail function. This guide provides a step-by-step process to configure global SMTP settings for the Email module, ensuring seamless email delivery.

---

### Steps to Configure Global SMTP Settings

#### **Step 1: Access FlowMattic Settings**
1. Log in to your FlowMattic admin panel.
2. Navigate to the settings page by clicking on the **Settings** option in the FlowMattic admin menu.

#### **Step 2: Locate the SMTP Settings Section**
1. On the settings page, find the section labeled **SMTP Settings for FlowMattic Email Module**.
2. This section is where you will input the SMTP configuration details.

#### **Step 3: Provide SMTP Configuration Details**
Fill in the following fields with the appropriate information:

- **Server Name**: Enter the hostname of your SMTP server (e.g., smtp.gmail.com).
- **Port Number**: Specify the port number used by the SMTP server (e.g., 587 for TLS or 465 for SSL).
- **SMTP Username**: Provide the username required for SMTP authentication.
- **SMTP Password**: Enter the password associated with the SMTP username.
- **Encryption Type**: Choose the encryption type to secure the connection. Options include **SSL** or **TLS**.

#### **Step 4: Save the Configuration**
1. After filling in the required fields, click on the **Save Settings** button.
2. Once saved, FlowMattic will use these global SMTP settings for sending emails in workflows.

#### **Step 5: Enable Global SMTP in the Email Module**
1. In the Email module settings, locate the **Email Provider** field.
2. Select the **FlowMattic Default** option to enable the use of global SMTP settings.

---

### Additional Notes
- FlowMattic's SMTP settings are compatible with most popular SMTP service providers, including Gmail, Amazon SES, SendGrid, and Mailgun.
- Ensure that the SMTP credentials and server details you provide are accurate to avoid errors in email delivery.
- If you encounter any issues, verify the port and encryption type required by your SMTP provider.

---

### Troubleshooting Tips
- Double-check your SMTP username and password for accuracy.
- Ensure that your SMTP provider allows third-party applications to send emails (e.g., enabling "Less Secure Apps" for Gmail).
- If emails fail to send, review the error logs for more details.

By following these steps, you can successfully configure and utilize global SMTP settings in FlowMattic's Email module to streamline your email workflows.

---

# How to configure MCP server in n8n AI Agent

Source: https://support.flowmattic.com/kb/article/87/how-to-configure-mcp-server-in-n8n-ai-agent

## Overview

This guide will walk you through integrating FlowMattic MCP (Model Context Protocol) tools with n8n AI Agent for advanced workflow automation and AI assistance. This integration allows your n8n workflows to leverage FlowMattic's powerful automation capabilities through MCP.

## Prerequisites

Before you begin, ensure you have:

- **n8n instance** (cloud or self-hosted) with AI Agent node support
- **FlowMattic MCP server** configured and running (Server ID: 72)
- **Admin access** to both n8n and FlowMattic
- **Basic knowledge** of n8n workflow creation

## What You'll Achieve

After completing this integration, your n8n AI Agent will be able to:
- Access FlowMattic's automation tools
- Execute FlowMattic workflows from within n8n
- Combine AI-driven decision making with FlowMattic's automation capabilities
- Create sophisticated workflows that leverage both platforms

---

## Step-by-Step Integration Process

### Step 1: Add AI Agent Node

1. **Open your n8n workflow**
   - Navigate to your n8n instance
   - Create a new workflow or open an existing one where you want to add FlowMattic capabilities

2. **Add the AI Agent node**
   - Click the **"+"** button to add a new node
   - Search for **"AI Agent"** in the node library
   - Select and add the **AI Agent** node to your workflow
   - Position the node where you want it in your workflow

3. **Initial AI Agent configuration**
   - Click on the AI Agent node to open its settings
   - Configure basic settings like:
     - **Node name**: Give it a descriptive name (e.g., "FlowMattic AI Agent")
     - **Chat Model**: Select your preferred AI model
     - **System Message**: Add context about FlowMattic tools if needed

### Step 2: Configure MCP Server

1. **Access AI Agent Tools configuration**
   - In the AI Agent node settings, look for the **"Tools"** section
   - Click **"Add Tool"** or **"+"** to add a new tool
   - Select **"MCP Server"** from the available tool types

2. **Add MCP Server node**
   - Click **"Add MCP Server"** to create a new MCP server connection
   - This will open the MCP Server configuration dialog

3. **Configure FlowMattic MCP Server URL**
   - In the MCP Server configuration, locate the **"Server URL"** field
   - Enter your FlowMattic MCP server URL using the following format:
   ```
   {{flowmattic_mcp_server}}/sse
   ```
   
   **Note**: The FlowMattic MCP server ID for this integration is **72**.

4. **Additional MCP Server settings**
   - **Server Name**: Give your MCP server a descriptive name (e.g., "FlowMattic MCP")
   - **Authentication**: Configure any required authentication if your FlowMattic instance requires it
   - **Timeout**: Set appropriate timeout values (default is usually fine)

5. **Test the connection**
   - Click **"Test Connection"** if available
   - Verify that n8n can successfully connect to your FlowMattic MCP server
   - You should see a success message confirming the connection

### Step 3: Configure Tools

1. **Fetch available tools**
   - After successfully connecting to the MCP server, n8n will automatically fetch the available tools from your FlowMattic instance
   - This may take a few moments depending on your FlowMattic configuration

2. **Review available FlowMattic tools**
   - You'll see a list of available tools that FlowMattic MCP server provides
   - Common FlowMattic tools might include:
     - **Workflow triggers**
     - **Data manipulation tools**
     - **Integration connectors**
     - **Custom FlowMattic functions**

3. **Select tools for your workflow**
   You have two options:
   
   **Option A: Use all available tools**
   - Check **"Use all tools"** if you want the AI Agent to have access to all FlowMattic capabilities
   - This gives maximum flexibility but may overwhelm the AI with too many options
   
   **Option B: Select specific tools**
   - Uncheck **"Use all tools"**
   - Manually select only the FlowMattic tools relevant to your specific workflow
   - This provides more focused and predictable AI behavior

4. **Configure tool parameters**
   - For each selected tool, review and configure any required parameters
   - Set default values where appropriate
   - Add descriptions or constraints to guide the AI's usage of each tool

### Step 4: Start Automating Workflows

1. **Complete the AI Agent setup**
   - Review all your AI Agent configurations
   - Ensure the system message guides the AI on how to use FlowMattic tools effectively
   - Save the AI Agent node configuration

2. **Connect the workflow**
   - Connect your AI Agent node to other nodes in your workflow
   - Set up input data that the AI Agent will process
   - Configure output handling for the AI Agent's responses

3. **Test your integration**
   - **Manual test**: Use n8n's test functionality to run your workflow manually
   - **Sample data**: Provide sample input data to test the AI Agent's interaction with FlowMattic tools
   - **Monitor execution**: Watch the execution logs to see how the AI Agent uses FlowMattic tools

4. **Deploy and monitor**
   - Activate your workflow to run automatically
   - Set up appropriate triggers (webhooks, schedules, etc.)
   - Monitor workflow executions to ensure the FlowMattic integration works as expected

---

## Advanced Configuration

### System Message Optimization

Enhance your AI Agent's performance by adding a detailed system message:

```
You are an AI assistant with access to FlowMattic automation tools. Use these tools to:
- Execute workflow automations
- Process data transformations
- Trigger integrations with external services
- Manage complex multi-step processes

Always explain what FlowMattic tool you're using and why, to maintain transparency in your automation decisions.
```

### Error Handling

1. **Configure retry logic**
   - Set up retry attempts for failed FlowMattic tool calls
   - Configure exponential backoff for connection issues

2. **Error notifications**
   - Set up alerts for MCP server connection failures
   - Monitor FlowMattic tool execution errors

3. **Fallback strategies**
   - Define alternative actions when FlowMattic tools are unavailable
   - Implement graceful degradation of functionality

### Performance Optimization

1. **Tool selection strategy**
   - Only enable FlowMattic tools you actually need
   - Group related tools to reduce decision complexity for the AI

2. **Caching considerations**
   - Implement caching for frequently used FlowMattic data
   - Consider rate limiting to avoid overwhelming your FlowMattic server

---

## Troubleshooting

### Common Issues and Solutions

**Issue**: Cannot connect to FlowMattic MCP server
- **Check**: Verify the MCP server URL format is `{{flowmattic_mcp_server}}/sse`
- **Check**: Ensure FlowMattic MCP server (ID: 72) is running and accessible
- **Check**: Verify network connectivity between n8n and FlowMattic

**Issue**: No tools available after connection
- **Check**: Confirm FlowMattic MCP server is properly configured
- **Check**: Verify FlowMattic has workflows/tools available to expose via MCP
- **Check**: Review FlowMattic MCP server logs for errors

**Issue**: AI Agent not using FlowMattic tools effectively
- **Solution**: Improve system message with specific instructions
- **Solution**: Select fewer, more focused tools
- **Solution**: Provide better context in your workflow inputs

**Issue**: Timeout errors when calling FlowMattic tools
- **Solution**: Increase timeout values in MCP server configuration
- **Solution**: Optimize FlowMattic workflows for faster execution
- **Solution**: Implement async processing where possible

---

## Best Practices

### Security Considerations

1. **Secure your MCP server URL**
   - Use HTTPS for all connections
   - Implement proper authentication
   - Restrict access to trusted n8n instances only

2. **API key management**
   - Store FlowMattic API keys securely in n8n credentials
   - Rotate keys regularly
   - Monitor API usage for suspicious activity

### Workflow Design

1. **Clear tool usage guidelines**
   - Document which FlowMattic tools to use in different scenarios
   - Provide examples in your system messages
   - Test thoroughly with various input types

2. **Monitoring and logging**
   - Enable detailed logging for both n8n and FlowMattic
   - Set up monitoring for integration health
   - Track tool usage patterns and performance

---

## Additional Resources

- [FlowMattic MCP Documentation](https://support.flowmattic.com/kb/article/86/) - Official FlowMattic MCP integration guide
- [n8n AI Agent Documentation](https://docs.n8n.io/integrations/builtin/cluster-nodes/root-nodes/n8n-nodes-langchain.agent/) - Comprehensive n8n AI Agent reference
- [MCP Protocol Specification](https://modelcontextprotocol.io/specification) - Technical details about Model Context Protocol

---

## Next Steps

After successfully integrating n8n AI Agent with FlowMattic MCP server:

1. **Explore advanced features** - Experiment with complex multi-step automations
2. **Build custom tools** - Create custom FlowMattic tools for specific use cases
3. **Scale your workflows** - Implement the integration across multiple n8n workflows
4. **Share your experience** - Document your specific use cases and share with the community

Your n8n AI Agent can now leverage the full power of FlowMattic's automation capabilities, enabling sophisticated workflows that combine AI intelligence with robust automation tools.

---

# How to Connect a FlowMattic MCP Server in Witsy

Source: https://support.flowmattic.com/kb/article/83/how-to-connect-a-flowmattic-mcp-server-in-witsy

### Step-by-Step Guide to Connect a FlowMattic MCP Server in Witsy
Follow this guide to configure and connect a FlowMattic MCP Server in Witsy.

1. **Open Witsy and Navigate to Settings**
 - Log in to your Witsy account or open the desktop application.
 - From the main navigation menu, click on **Settings**.
 - Inside the Settings page, locate and select the **MCP ** tab to manage external MCP servers.
 - Click on the ➕ (plus) button to add a new MCP server.
  
 ![Image_2025-07-18_at_22546_PM.jpeg](/storage/kb-images/e07cfae81b-inline.png)
 
2. **Configure MCP Server Details**
 - Select MCP Type: Choose Custom MCP Server from the dropdown menu.
 - Choose Type: In the Type field, select **Streamable HTTP**.
 - Enter Label: Assign a friendly name to your server, such as “FlowMattic MCP”.
 - Enter URL: Paste your FlowMattic MCP Server URL.
 - Click the **Save **button to store your MCP server configuration.
  
![Image 2025-07-18 at 2.29.16 PM.jpeg (1108×548) 2025-07-28 at 3.24.23 AM.png](/storage/kb-images/2ef0fbe07e-inline.png)
 
3. **Start the MCP Server**
After saving the configuration, click on the Start button to activate the MCP connection.
Witsy will attempt to connect to the FlowMattic MCP server.
 
 ![Image_2025-07-18_at_24103_PM.jpeg](/storage/kb-images/db25bda14d-inline.png)

4. **Test the Connection**
Once the server is started, Witsy may automatically fetch available tools from the FlowMattic MCP Server. 
Execute a task related to the tools created in the FlowMattic MCP Server.

### Additional Tips
Double-check the FlowMattic MCP Server URL to prevent connection issues.

### Done!
You’ve successfully connected your MCP Server to Witsy.

---

# How to Connect a FlowMattic MCP Server to Vapi

Source: https://support.flowmattic.com/kb/article/82/how-to-connect-a-flowmattic-mcp-server-to-vapi

### Steps to Connect FlowMattic MCP Server

1. **Log In to Vapi**
    Visit [https://vapi.ai](https://vapi.ai) and log in to your Vapi account.

2. **Access the Tools Section**
   - Navigate to the left sidebar and click on the “**Tools**” option.
   - Click the “**Create Tool**” button.
   - From the dropdown menu, select **MCP** as the tool type.
    
 ![Image_2025-07-14_at_112008_PM.jpeg](/storage/kb-images/fa51a63e2c-inline.png)

3. **Provide Tool Details**
   - Enter a **Tool Name** (e.g., `FlowMattic_MCP`).
   - Add a **Description** (e.g., `FlowMattic MCP Server for executing real-time automation actions, tasks, and workflows via Vapi voice agents.`).
    
 ![Image_2025-07-14_at_112709_PM.jpeg](/storage/kb-images/68d9a31f35-inline.png)

4. **Configure the Server Settings**
    Paste your FlowMattic MCP Server URL in the **Server URL** field.
 
![93baccbe-832a-4d83-be08-61ea46678fc7.png](/storage/kb-images/08a2acd467-inline.png)

5. **Set the MCP Protocol**
    Under the **MCP Settings**, choose the protocol as **Streamable HTTP**.
 
 ![Image_2025-07-14_at_113028_PM.jpeg](/storage/kb-images/0f3d2af324-inline.png)

6. **Save the MCP Tool**
    Click the “Save” button located in the top-right corner of the interface.

7. **Update Assistant Tool Settings**
 - After successfully adding the FlowMattic MCP tool, navigate to your Assistant settings.
 - Go to the “Tools” section within the assistant configuration.
 - Select and enable the FlowMattic_MCP tool for your assistant so it can actively use it during conversations.

8. **Test Your MCP Tool**
   - Test the tool by prompting your Vapi agent with tool-based commands.
   - Ensure that tools are registered and exposed in your FlowMattic MCP Server for Vapi to access them.

### Additional Tips
 Double-check the FlowMattic MCP Server URL to prevent connection issues.

### Conclusion
By following these steps, you can successfully integrate your FlowMattic MCP Server with Vapi, enabling powerful automation capabilities and streamlined workflows.

---

# How to Connect Any App to FlowMattic Using Webhooks

Source: https://support.flowmattic.com/kb/article/49/how-to-connect-any-app-to-flowmattic-using-webhooks

Webhooks provide a seamless way to connect your app to FlowMattic workflows, even if the app is not listed in the integrations. By leveraging Webhooks, you can automate tasks and enhance workflow efficiency. Follow these detailed steps to set up a Webhook connection:

#### Steps to Connect Your App to FlowMattic Using Webhooks

1. **Create a Workflow in FlowMattic**
   - Log in to FlowMattic and create a new workflow.
   - Choose the Webhook trigger, which will generate a unique webhook URL for your workflow.

2. **Locate the Webhook Setup in Your App**
   - Access your app's settings or API section to find the Webhook configuration option.
   - Refer to your app's documentation if needed to locate this feature.

3. **Enter the Webhook URL in Your App**
   - Copy the webhook URL generated by FlowMattic.
   - Paste it into the Webhook URL field in your app's settings.

4. **Test the Webhook Connection**
   - In FlowMattic, edit the Webhook trigger settings and navigate to the Test tab.
   - Click the "Capture Response" button to prepare FlowMattic to receive data.
   - In your app, either send a test payload or perform an action that triggers the Webhook. This ensures the connection is working as intended.

5. **Verify and Use the Captured Data**
   - Once FlowMattic captures the payload, review the data received.
   - Use the captured data in subsequent steps of your workflow for automation.

#### Additional Tips
- Ensure the Webhook URL is correctly entered in your app to avoid connection errors.
- If your app supports sending test payloads, utilize this feature to validate the setup before proceeding.
- Refer to your app's API documentation for any specific Webhook setup requirements.

By setting up Webhooks, you can integrate and automate workflows between FlowMattic and your app, even if the app is not natively supported. This flexibility allows you to streamline processes and enhance productivity.

For further assistance, consult FlowMattic's support team or your app's documentation.

---

# How to Connect Dropbox with FlowMattic?

Source: https://support.flowmattic.com/kb/article/122/how-to-connect-dropbox-with-flowmattic

## Introduction

Dropbox is one of the most popular cloud storage platforms, trusted by millions of users and businesses worldwide for storing, sharing, and collaborating on files. With FlowMattic's Dropbox integration, you can automate your file management workflows directly from your WordPress site. Whether you need to automatically upload files, create folders, generate shared links, monitor file changes with triggers, or sync data between Dropbox and other applications, FlowMattic makes it seamless. This guide will walk you through the process of creating a Dropbox App and connecting it to FlowMattic using OAuth 2.0 authentication with PKCE for enhanced security.

---

## Prerequisites

Before you begin, ensure you have:

- A Dropbox account (free or paid)
- Access to your FlowMattic WordPress installation
- Administrator access to create connects in FlowMattic

---

## Step 1: Create a New Dropbox App

1. Go to the [Dropbox App Console](https://www.dropbox.com/developers/apps) and sign in with your Dropbox account.

2. Click the **Create app** button.

3. On the "Create a new app on the DBX Platform" page, configure the following settings:

### Choose an API
- Select **Scoped access** (this is the recommended option for new apps)

### Choose the Type of Access
- **App folder** - Select this if you want FlowMattic to only access a single folder created specifically for your app
- **Full Dropbox** - Select this if you want FlowMattic to access all files and folders in the user's Dropbox (recommended for full automation capabilities)

### Name Your App
- Enter a unique name for your app (e.g., "Your Company Name - FlowMattic")
- The app name must be unique across all Dropbox apps

4. Click the **Create app** button to create your application.

![Developers - Dropbox Create app.png](/storage/kb-images/376a4cd87e-inline.png)

---

## Step 2: Configure App Settings

After creating your app, you'll be redirected to the app settings page. Here you need to configure the OAuth 2.0 settings:

### Locate Your App Credentials

1. On the **Settings** tab, find the following credentials:
   - **App key** - This is your Client ID (e.g., `23qct0gddhrdqog`)
   - **App secret** - Click "Show" to reveal your Client Secret

> **Important:** Keep your App secret confidential. Never share it publicly or commit it to version control.

![Dropbox app - client id and secret.png](/storage/kb-images/a35cde515b-inline.png)

### Configure OAuth 2 Redirect URI

1. Scroll down to the **OAuth 2** section
2. In the **Redirect URIs** field, enter your FlowMattic callback URL:
   ```
   https://yourdomain.com/wp-json/flowmattic/v1/auth/dropbox
   ```
   Replace `yourdomain.com` with your actual WordPress site domain.

3. Click the **Add** button to save the redirect URI

### Enable PKCE Support

1. Under **Allow public clients (Implicit Grant & PKCE)**, select **Allow**
2. This enables the secure PKCE authentication flow used by FlowMattic

---

## Step 3: Configure App Permissions (Scopes)

FlowMattic requires specific permissions to perform various Dropbox operations. Navigate to the **Permissions** tab and enable the following scopes:

### Account Info
| Scope | Description | Required |
|-------|-------------|----------|
| `account_info.read` | View basic information about your Dropbox account | Recommended |

### Files and Folders
| Scope | Description | Required |
|-------|-------------|----------|
| `files.metadata.write` | View and edit information about your Dropbox files and folders | **Required** |
| `files.metadata.read` | View information about your Dropbox files and folders | **Required** |
| `files.content.write` | Edit content of your Dropbox files and folders | **Required** |
| `files.content.read` | View content of your Dropbox files and folders | **Required** |

### Collaboration
| Scope | Description | Required |
|-------|-------------|----------|
| `sharing.write` | View and manage your Dropbox sharing settings and collaborators | **Required** |
| `sharing.read` | View your Dropbox sharing settings and collaborators | **Required** |

### File Requests (Optional)
| Scope | Description | Required |
|-------|-------------|----------|
| `file_requests.write` | View and manage your Dropbox file requests | Optional |
| `file_requests.read` | View your Dropbox file requests | Optional |

### Contacts (Optional)
| Scope | Description | Required |
|-------|-------------|----------|
| `contacts.write` | View and manage your manually added Dropbox contacts | Optional |
| `contacts.read` | View your manually added Dropbox contacts | Optional |

### Connect (Optional)
| Scope | Description | Required |
|-------|-------------|----------|
| `profile` | Read basic profile info | Optional |
| `openid` | Required for OpenID Connect flow | Optional |
| `email` | Read basic email info | Optional |

> **Note:** After changing permissions, you may need to re-authenticate your connection in FlowMattic for the new permissions to take effect.

![Dropbox app permissions.png](/storage/kb-images/db3defbf76-inline.png)

Click **Submit** to save your permission changes.

---

## Step 4: Connect Dropbox in FlowMattic

Now that your Dropbox app is configured, you can connect it to FlowMattic:

1. In your WordPress admin, navigate to **FlowMattic > Connects**

2. Click **Connect Integration**

3. Search for and select **Dropbox**

4. Enter your credentials:
   - **Client ID** - Paste the App key from your Dropbox app settings
   - **Client Secret** - Paste the App secret from your Dropbox app settings

5. Click **Authenticate and Save Connect** to initiate the OAuth flow

6. A new window will open redirecting you to Dropbox for authorization

7. Review the permissions and click **Allow** to grant FlowMattic access to your Dropbox account

8. The window will close automatically and your connection will be saved

---

## Available Dropbox Actions in FlowMattic

Once connected, you can use the following Dropbox actions in your workflows:

| Action | Description |
|--------|-------------|
| **Upload File** | Upload a file to Dropbox |
| **Download File** | Download a file from Dropbox |
| **Create Folder** | Create a new folder in Dropbox |
| **Delete File** | Delete a file from Dropbox |
| **Delete Folder** | Delete a folder and its contents from Dropbox |
| **Copy File** | Copy a file to a different location |
| **Move File** | Move or rename a file |
| **List Folder Contents** | List all files and folders in a directory |
| **Get File Metadata** | Get metadata for a file or folder |
| **Search Files** | Search for files and folders |
| **Create Text File** | Create a new text file with content |
| **Create Shared Link** | Create a shared link for a file or folder |
| **Get Temporary Download Link** | Get a temporary download link for a file |
| **Share Folder** | Share a folder with collaborators |
| **Add Folder Member** | Add a member to a shared folder |
| **Create File Request** | Create a file request for external uploads |

---

## Available Dropbox Triggers in FlowMattic

FlowMattic also supports Dropbox triggers to start workflows automatically:

| Trigger | Description |
|---------|-------------|
| **File Added** | Triggers when a new file is added to a specified folder |
| **File Modified** | Triggers when a file is modified |
| **File Deleted** | Triggers when a file is deleted |
| **Folder Added** | Triggers when a new folder is created |

---

## Troubleshooting

### "Invalid redirect URI" Error
- Ensure the redirect URI in your Dropbox app settings exactly matches your FlowMattic callback URL
- Check that there are no trailing slashes or typos
- Verify your WordPress site is accessible via HTTPS

### "Invalid response_type" Error
- This typically occurs with Scoped Access apps
- Ensure all required permissions are enabled in the Permissions tab
- Try re-creating the app with the correct settings

### Connection Expires or Stops Working
- FlowMattic automatically refreshes access tokens using the refresh token
- If issues persist, try disconnecting and reconnecting your Dropbox account
- Verify your Dropbox app hasn't been revoked or deleted
- Confirm that the Cron jobs are working fine

### Permission Denied Errors
- Check that the required scopes are enabled in your Dropbox app's Permissions tab
- After changing permissions, you must re-authenticate the connection

---

# How to Connect FlowMattic MCP Server in Claud Assistance

Source: https://support.flowmattic.com/kb/article/81/how-to-connect-flowmattic-mcp-server-in-claud-assistance

### Steps to Connect FlowMattic MCP Server

#### Step 1: Open Settings and Access Connectors
1. Launch the Claud Assistance platform.
2. Navigate to the **Settings** section from the sidebar or top menu.
3. Click on the **Connectors** tab.
4. Select **Add Custom Connector** to initiate the setup process.
 
 ![7ccd563d-dee0-4b71-9aaf-c3e4c971d661.png](/storage/kb-images/cb1024e3c5-inline.png)

#### Step 2: Add Custom Connector Details
1. **Name**: Enter a clear and descriptive name for your connector, such as:
   - Example: `FlowMattic MCP`
2. **URL**: Paste your FlowMattic MCP Server URL. For instance:
   - Example: `https://your-flowmattic-mcp-url.com`
3. Click the **Add** button to save and register the connector.
![e8938625-0fb7-4e80-8e00-1b9ef6d7f44b.png](/storage/kb-images/3f29cd8561-inline.png) 

#### Step 3: Finalize Setup
1. Once you click **Add**, a **Tools Popup** will automatically appear.
2. The popup will display the available tools fetched from your MCP server.
3. Click the **Done** button to complete the setup process.
![138b4d83-23b4-47bd-8c75-09ab424a3ed4.png](/storage/kb-images/a25beb807c-inline.png)

#### Step 4: Test the Connection
1. After completing the setup, test the connection to ensure everything is functioning correctly.
2. Open a new task and ask anything related to the tools created in FlowMattic.

---

### Tips for Successful Integration
- Ensure the URL entered is correct and accessible.
- Regularly update the FlowMattic MCP server URL if changes occur.
---


By following these steps, you can seamlessly integrate FlowMattic MCP as a custom connector within Claud Assistance, enabling enhanced workflows and tool accessibility.

---

# How to Connect FlowMattic MCP Server in Kiro

Source: https://support.flowmattic.com/kb/article/84/how-to-connect-flowmattic-mcp-server-in-kiro

### Introduction
This guide provides a comprehensive walkthrough for integrating the FlowMattic MCP Server into the Kiro application. By following these steps, you'll be able to configure and test the connection seamlessly.

### Steps to Connect FlowMattic MCP Server in Kiro

#### 1. Open Kiro and Access MCP Configuration
1. Launch the Kiro application on your system.
2. Navigate to the **Settings** section.
3. Within **Settings**, click on the option to open the **User MCP Config JSON**. This will allow you to edit the MCP configuration file.
 
 ![Image_2025-07-18_at_33742_PM.jpeg](/storage/kb-images/1464e2a3e9-inline.png)

####  2. Add the FlowMattic MCP Server Configuration
1. Copy the following JSON configuration code:
   ```json
   {
     "mcpServers": {
       "FlowMattic": {
         "command": "npx",
         "args": [
           "-y",
           "mcp-remote",
           "https://flowmattic.com/v1/mcp-server/*************"
         ]
       }
     }
   }
   ```
2. Paste the code into the configuration file.
3. Replace the placeholder URL `https://flowmattic.com/v1/mcp-server/**************` with your actual FlowMattic MCP Server URL.

####  3. Save and Close the Configuration File
1. Once the JSON file is updated, save the changes.
2. Close the editor.

####  4. Locate and Refresh FlowMattic MCP Server
1. After saving the configuration, you should see **FlowMattic** listed under the MCP section on the left sidebar of Kiro.
2. If it doesn’t appear immediately, click the **refresh icon** or restart the Kiro application to reload the available MCP servers.

####  5. Test the Connection
1. Kiro will automatically attempt to fetch tools from the configured FlowMattic MCP Server.
2. Test the connection by selecting tools from the sidebar or interacting with them in a session within Kiro.

### Additional Tips
- Ensure that the FlowMattic MCP Server URL is accurate and accessible.
- If you encounter any issues, verify the JSON syntax and check the server connectivity.

By following these steps, you can successfully integrate and utilize the FlowMattic MCP Server within Kiro.

---

# How to Connect FlowMattic MCP Server in Visual Studio Code for GitHub Copilot

Source: https://support.flowmattic.com/kb/article/77/how-to-connect-flowmattic-mcp-server-in-visual-studio-code-for-github-copilot

### Prerequisites

To successfully connect the FlowMattic MCP Server in Visual Studio Code (VS Code) with GitHub Copilot, ensure the following:

- GitHub Copilot is installed and enabled in your VS Code.
- Copilot is set to **Agent Mode**, which is required for MCP integrations.

### Step-by-Step Instructions

Follow these steps to connect the FlowMattic MCP server:

1. **Open the Command Palette in VS Code**
   - On Windows/Linux: Press `Ctrl + Shift + P`.
   - On Mac: Press `Cmd + Shift + P`.

2. **Search for the MCP Command**
   - In the Command Palette, type: `MCP: Add Server...`.
   - Select it and press `Enter` to execute the command.
     
 ![0443d4ab-0679-463d-8fba-22889472e099.png](/storage/kb-images/958e10bb2e-inline.png)

3. **Select the Server Type**
   - Choose `HTTP (HTTP or Server-Sent Events)` from the available options.
   - Press `Enter` to confirm your selection.
      
 ![612fd577-47e2-4103-aabc-46941f7c1640.png](/storage/kb-images/2f6a92bb74-inline.png)

4. **Enter the MCP Server URL**
   - When prompted for the "URL of the MCP Server" field, paste your FlowMattic MCP Server URL, for example: `https://your-flowmattic-mcp-url.com`.
   - Press `Enter` to proceed.
     
 ![1d53d71e-c7ef-49a4-950b-8eac08fdb989.png](/storage/kb-images/4437bd397a-inline.png)

5. **Name Your Server**
   - Provide a descriptive name for your server, such as `FlowMattic MCP`.
   - Press `Enter`.
     
 ![d3a711fb-ceec-464c-9bdf-2faf06da1752.png](/storage/kb-images/a3d88ea4b7-inline.png)

### Test the Connection
  Open GitHub Copilot Chat and try these commands:
   - Test Command: 
 ```
@copilot What FlowMattic capabilities are available through this MCP server? 
 ```
 
### Verify Successful Connection
  You should see:
 - The FlowMattic MCP server is listed in your MCP configurations
 - GitHub Copilot responding with FlowMattic-specific information
 - Access to FlowMattic tools through Copilot chat

### Additional Tips

 Double-check the MCP server URL for accuracy before proceeding.

Your FlowMattic MCP server is now fully integrated with VS Code GitHub Copilot and ready to use!

---

# How to Connect YouTube with FlowMattic

Source: https://support.flowmattic.com/kb/article/236/how-to-connect-youtube-with-flowmattic

### Overview

This guide walks you through creating a Google Cloud project for the **YouTube Data API v3** and connecting it to FlowMattic. Once connected, you can upload and update videos, manage playlists, moderate comments, track subscribers, and start workflows the moment something happens on your channel.

YouTube connects use **your own Google Cloud credentials**, so your channel access never passes through anyone else's application. You will create an OAuth client in Google Cloud, paste the Client ID and Secret into FlowMattic, and authorise your channel.

> **Before you start:** you need a Google account that owns (or manages) the YouTube channel you want to automate, and access to the [Google Cloud Console](https://console.cloud.google.com/).

---

### Steps to Set Up the Google Console Project

#### 1. Create a Google Cloud Project

- Log in to the **[Google Cloud Console](https://console.cloud.google.com/)**.
- Click the **Select a project** dropdown at the top of the page, then click **New Project**.
- Provide the following details:
-- **Project Name:** Enter a meaningful name (e.g. “FlowMattic YouTube Integration”).
-- **Location:** Leave it as “No organization” if you do not have one.
- Click **Create**. Google will redirect you to the project dashboard.

#### 2. Enable the YouTube Data API v3

- Navigate to **[APIs & Services > Library](https://console.cloud.google.com/apis/library)**.
- Search for **YouTube Data API v3**, click on it, and then click **Enable**.

> Make sure you enable **YouTube Data API v3** specifically. The “YouTube Analytics API” and “YouTube Reporting API” are separate products and are not used by this integration.

![youtube-data-api-v3](https://assets.infidesk.support/kb/inline/2026/08/lspuo9uruRrQHueLDiXKZ2jCWvtg8403hS61gDCF.jpg)

#### 3. Configure the OAuth Consent Screen

- Go to **[APIs & Services > OAuth consent screen](https://console.cloud.google.com/apis/credentials/consent)**.
- Choose **External** as the user type and click **Create**.
- Fill out the following details:
 - **App Name:** Enter a meaningful name (e.g. “FlowMattic YouTube Integration”).
-- **User Support Email:** Enter your email address.
-- **App Logo:** Optional.
-- **Authorized Domains:** Add the domain of the website where FlowMattic is installed (e.g. `yoursite.com`).
-- **Developer Contact Information:** Enter your email address.
- Click **Save and Continue**.

> Unlike some other Google integrations, YouTube sends users back to **your own website**, so the authorised domain must be **your domain** — not `flowmattic.com`.

#### 4. Add Scopes

- On the **[Scopes](https://console.cloud.google.com/auth/scopes)** screen, click **Add or Remove Scopes**.
- Select the following scopes from the list, or paste them in manually:
  - `https://www.googleapis.com/auth/youtube`
  - `https://www.googleapis.com/auth/youtube.upload`
  - `https://www.googleapis.com/auth/youtube.force-ssl`
  - `https://www.googleapis.com/auth/youtube.readonly`
- Click **Update**, then **Save and Continue**.

> All four scopes are required. `youtube.force-ssl` is what allows comment actions (post, reply, edit, delete and moderate), and `youtube.upload` is required for the Upload Video action. Leaving one out will make the matching actions fail with a permissions error after you connect.

![add youtube scopes](https://assets.infidesk.support/kb/inline/2026/08/NR8Mu1ecyMjm6beJq3FueJTC2qBExHgd7rf9RncW.jpg)

#### 5. Add Test Users

- On the **[Audience](https://console.cloud.google.com/auth/audience)** tab, under the **Test Users** section:
-- Click **Add Users**.
-- Enter the email address of the Google account that owns the YouTube channel you want to connect, plus any other accounts that will authorise the connection.
- Click **Save and Continue**.

![add-testers-to-google-app](https://assets.infidesk.support/kb/inline/2026/08/45BJ8v3tg2bkxBACAoJCBvzLU6XAszLJ1w9OyT4o.jpg)

#### 6. Create OAuth 2.0 Credentials

- Go to **[APIs & Services > Credentials](https://console.cloud.google.com/apis/credentials)**.
- Click **+ Create Credentials** and select **OAuth Client ID**.
- On the **Create OAuth Client ID** screen:
  - Select **Web Application** as the application type.
  - Provide a name for the credential.
  - Under **Authorized Redirect URIs**, click **Add URI** and enter your site's callback URL:

```
https://yoursite.com/wp-json/flowmattic/v1/auth/youtube
```

- Replace `yoursite.com` with the domain where FlowMattic is installed.
- Click **Create**, then securely store the **Client ID** and **Client Secret**.

> **This is the step people most often get wrong.** The redirect URI points at *your* website, not at FlowMattic's servers. It must match your site's REST API URL exactly — including `https://`, the `www.` prefix if your site uses one, and with no trailing slash. If your WordPress REST API uses the plain permalink format, your callback URL will instead look like `https://yoursite.com/?rest_route=/flowmattic/v1/auth/youtube`. You can confirm the exact URL on the FlowMattic connect screen in the next step.

![youtube-authorized-redirect-url](https://assets.infidesk.support/kb/inline/2026/08/sMEP662VyAFMhi3x6zcwfR6BHYEUNYGCcDqMm9vi.jpg)

#### 7. Configure the Connect in FlowMattic

- Navigate to **FlowMattic → Connects** in your WordPress dashboard.
- Click the **Connect Integration** button.
- Search for **YouTube** and click the box.
- Provide the following details:
  - **Connect Name:** Enter a meaningful name (e.g. “My YouTube Channel”).
  - **Client ID:** Paste the Client ID from Google Cloud.
  - **Client Secret:** Paste the Client Secret from Google Cloud.
- Click **Save Connect & Authenticate**.

![FlowMattic-connect-youtube](https://assets.infidesk.support/kb/inline/2026/08/QGw3FI4oZNeyooNCkPHCCA8aBI706Hehu6BGlPUy.jpg)

#### 8. Authenticate and Grant Access

- After saving, you will be redirected to Google's sign-in page.
- Sign in with the Google account that owns the channel.
- If you see a **“Google hasn't verified this app”** warning, click **Advanced**, then **Go to … (unsafe)**. This is expected for a private app that only you use.
- If the account manages more than one channel, pick the channel you want to automate.
- Review the permissions and click **Allow**.
- On success you are returned to FlowMattic and the connect is saved with its access and refresh tokens.

---

### Verify the Connection

Open any workflow, add a **YouTube** action step, choose **Get My Channel**, select your connect and click **Send Test Request**. A successful response returns your channel's title, ID and statistics — confirming the credentials and scopes are correct.

---

### Tips and Things to Watch

- **Keep your site's cron jobs healthy.** FlowMattic renews the YouTube access token in the background using WordPress cron. If cron is not running, the token will expire and your workflows will start failing with an authentication error. Setting up a real server-side cron is strongly recommended.
- **Apps left in “Testing” expire refresh tokens after 7 days.** While your OAuth consent screen is in **Testing** status, Google invalidates refresh tokens after seven days and you will have to reconnect. To avoid this, set the publishing status to **In production** on the OAuth consent screen. For a private app using sensitive scopes this is still fine — you simply keep it unverified and accept the warning screen at step 8.
- **Mind the API quota.** The YouTube Data API gives each project 10,000 quota units per day by default. Read operations are cheap (about 1 unit), but **each video upload costs 1,600 units** — roughly six uploads per day — and a search costs 100. If you plan heavy use, request a quota increase in the Google Cloud Console.
- **The “New Video in Channel” trigger needs no connect.** It reads a channel's public RSS feed, so you can use it — and its transcript field — without creating any Google credentials at all. The other four triggers do require the connect.
- **Comments cannot be posted on private videos.** YouTube rejects comment actions on videos set to Private with an “insufficient permissions” error. Set the video to Unlisted or Public if a workflow needs to comment on it.
- **One connect per channel.** If you manage several channels, create a separate connect for each and pick the right one on each workflow step.

---

### Troubleshooting

| Message | What it means | Fix |
| --- | --- | --- |
| `redirect_uri_mismatch` | The callback URL in Google Cloud does not exactly match your site's REST URL. | Re-check step 6 — protocol, `www.`, trailing slash, and permalink format all matter. |
| `access_blocked` / app not verified | Your Google account is not on the test-user list. | Add the account under **Audience → Test Users**, or set the app to **In production**. |
| `YouTube authentication required` | The connect has no valid access token. | Reconnect the integration; then check that WordPress cron is running so the token can refresh. |
| `insufficient permissions` on comment actions | The `youtube.force-ssl` scope is missing, or the target video is Private. | Add the scope and reconnect; or change the video's visibility. |
| `quotaExceeded` | The project's daily quota is used up. | Wait for the daily reset, or request a higher quota in Google Cloud. |

---

# How to Create and Connect a Facebook App to Access Facebook Pages API with FlowMattic

Source: https://support.flowmattic.com/kb/article/60/how-to-create-and-connect-a-facebook-app-to-access-facebook-pages-api-with-flowmattic

### Overview
This guide outlines a step-by-step process for creating a Facebook app and integrating it with FlowMattic to access the Facebook Pages API. Follow the instructions below to enable smooth integration and manage Facebook Pages via FlowMattic workflows.

### Steps to Create and Connect a Facebook App

#### Step 1: Create a Facebook App
- Visit the [Facebook Developer Documentation](https://developers.facebook.com/docs/development/create-an-app/) to initiate the app creation process.
- Login with your Facebook account and visit this page - [Create Facebook App](https://developers.facebook.com/apps/creation/)
- Enter App Name and email and click next, on the **Use Cases** section, choose **Other** and click next
- On next step, choose **App Type** as **Business** and click next
- Verify the details, choose your Business portfolio if already have and click **Create App** button

#### Step 2: Enable Products
- Access your Facebook App Dashboard and navigate to the section labeled "Add products to your app."
- Click the "Setup" button next to "Facebook Login" and "Webhooks."
 
 ![Facebook Apps Configure Products](/storage/kb-images/87285bbd11-inline.png)


#### Step 3: Configure Products
**Facebook Login for Business:**
- Go to **Settings** under Facebook Login for Business.
- Add the following URL under **Valid OAuth Redirect URIs:**
  - `https://api.flowmattic.com/facebook-pages`
- Specify the **Allowed Domains for the JavaScript SDK:**
  - `https://api.flowmattic.com`

**Webhooks:** 
- After adding webhooks to the app, you will be asked to choose the object and subscribe to the object like below. Choose **Page** as object and click the subscribe button.
 
 ![Subscribe to Page Webhooks](/storage/kb-images/90d583d250-inline.png)

- Facebook permits only one webhook URL per app. To use Facebook Pages integration across multiple workflows with different triggers, utilize the following webhook URL and connect it to your Facebook Pages trigger in the workflow:
  - `https://api.flowmattic.com/facebook-pages/webhook.php`
- Use the verify token: `FlowMatticPages`
- Alternatively, for custom webhook URLs, configure the Router to handle different triggers based on Facebook's data. Use the verify token: `flowmattic` (all lowercase).
- After setting up the webhook URL, click the **Subscribe** button next to the **Feed** item in the list and set the version to **22.0.**

#### Step 4: Retrieve Client ID and Client Secret
- Navigate to **App Settings -> Basic**.
- Securely copy and save the **App ID** and **App Secret.**
 
 ![Get App ID and App Secret](/storage/kb-images/4219e54f88-inline.png)


#### Step 5: Connect to Facebook Pages
- Open **FlowMattic -> Connects.**
- Click the **Connect Integration** button.
- Search for **Facebook Pages** and select it.
- Input the **App ID** and **App Secret** into the **Client ID** and **Client Secret** fields.
- Click **Save and Authenticate** and complete the Facebook account authentication process.
- During authentication, ensure that the pages you wish to use are selected.

### Tips
- Verify the accuracy of URLs and tokens to prevent configuration errors.
- When using custom webhook URLs, ensure the Router is correctly set up to manage various triggers.

### Additional Context
This setup facilitates the integration of Facebook Pages into multiple workflows and triggers via FlowMattic, enabling streamlined page management and task automation.

---

# How to Create a Shopify App and Get Client ID & Secret for FlowMattic?

Source: https://support.flowmattic.com/kb/article/120/how-to-create-a-shopify-app-and-get-client-id--secret-for-flowmattic

This guide will walk you through the process of creating a custom Shopify app to connect your Shopify store with FlowMattic. You'll need to access your Shopify admin panel and follow these steps carefully.

## Prerequisites

Before you begin, make sure you have:
- Admin access to your Shopify store
- Access to your FlowMattic dashboard
- Your FlowMattic redirect URL (you can get this from FlowMattic → Connect settings)

---

## Step 1: Access Apps and Sales Channels Settings

1. Log in to your **Shopify Admin Panel**
2. In the left sidebar, scroll down and click on **"Apps"**
3. In the search bar at the top, search for **"Apps"**
4. Click on **"App and sales channel settings"** from the dropdown menu

![App and sales channel settings.png](/storage/kb-images/455d60c52a-inline.png)

> **Note:** This is where you manage all your app integrations and create custom apps for your store.

---

## Step 2: Navigate to App Development

1. On the Settings page, look for the **"Apps and sales channels"** section in the left sidebar
2. You'll see an "App development" page with information about building apps
3. Click the **"Build apps in Dev Dashboard"** button

![build apps in dev dashboard.png](/storage/kb-images/40373d7e93-inline.png)

> **Important:** Starting January 1, 2026, you will not be able to create new legacy custom apps. Use the Dev Dashboard for all new app development.

---

## Step 3: Create a New App

1. You'll be taken to the "Create an app" page
2. Look for the section titled **"Start from Dev Dashboard"**
3. Enter your app name in the "App name" field (e.g., "My FlowMattic")
   - You have 30 characters maximum for the app name
4. Click the **"Create"** button

![Create an app.png](/storage/kb-images/271e0c2a0e-inline.png)

> **Tip:** Choose a descriptive name that helps you identify this connection later (e.g., "FlowMattic Integration" or "My Store Automation").

---

## Step 4: Configure App Name (If Needed)

After creating the app, you'll land on the "Create a version" page where you can verify or update your app name:

1. Confirm the **App name** is correct (13/30 character limit shown)
2. Proceed to the next section to configure URLs and scopes

---

## Step 5: Configure App URLs and Scopes

This is the most important step where you'll configure how FlowMattic communicates with Shopify.

### Configure URLs

1. Scroll down to the **"URLs"** section
2. In the **"App URL"** field, enter: `https://flowmattic.com`
3. Check the **"Embed app in Shopify admin"** checkbox if needed

### Configure Redirect URLs

1. Go to your **FlowMattic Dashboard** → **Connect** section
2. Copy the redirect URL provided by FlowMattic
3. Paste it in the **"Redirect URLs"** field in Shopify
   - The format will be: `https://YOURDOMAIN/wp-json/flowmattic/v1/auth/shopify`
   - **Replace YOURDOMAIN with your actual website domain**

### Select Scopes

1. Click the **"Select scopes"** button
2. A modal will appear with various permission scopes
3. **Select ALL scopes** to avoid permission issues later
   - This includes: read/write access to orders, products, customers, inventory, etc.

> **Why select all scopes?** This ensures FlowMattic has full access to automate all aspects of your Shopify store without running into permission errors.

### Set Webhooks API Version

1. In the **"Webhooks API Version"** dropdown, select the latest version (e.g., **2025-10**)

![Create a version My FlowMattic.png](/storage/kb-images/d82a29531c-inline.png)

---

## Step 6: Release Your App Version

1. After configuring all settings, scroll to the top or bottom of the page
2. Click the **"Release"** button
3. Confirm the release when prompted

> **Important:** Your app must be released before you can use the credentials. An unreleased app version won't work with FlowMattic.

---

## Step 7: Get Your Client ID and Secret

Now you'll retrieve the credentials needed to connect FlowMattic to Shopify.

1. In the left sidebar of the Dev Dashboard, click on **"Settings"**
2. Look for the **"Credentials"** section at the top of the page
3. You'll see two values:
   - **Client ID**: A long alphanumeric string (e.g., `ce5cd59e3abdd0f8255883...`)
   - **Secret**: Hidden with dots (••••••••••••••••••)

### Copy Your Credentials

1. Click the **copy icon** (📋) next to the **Client ID** to copy it
2. Click the **eye icon** (👁️) next to the **Secret** to reveal it
3. Click the **copy icon** to copy the secret
4. Keep these credentials secure and don't share them publicly

![Get client id and secret.png](/storage/kb-images/7cb66465d2-inline.png)

> **Security Note:** Treat your Client Secret like a password. Never share it publicly or commit it to version control systems.

---

## Step 8: Connect FlowMattic with Shopify

Now that you have your credentials, it's time to complete the connection in FlowMattic.

1. Go to your **FlowMattic Dashboard**
2. Navigate to **Connect** (or wherever Shopify integration settings are located)
3. Find the **Shopify Connect** settings
4. Enter the following details:
   - **Client ID**: Paste the Client ID you copied from Shopify
   - **Client Secret**: Paste the Client Secret you copied from Shopify
   - **Shop URL**: Enter your Shopify store URL (e.g., `yourstore.myshopify.com`)
5. Click **"Authenticate"** or **"Connect"** button
6. You'll be redirected to Shopify to authorize the connection
7. Click **"Install"** or **"Authorize"** on the Shopify authorization page
8. You'll be redirected back to FlowMattic with a successful connection

---

## Troubleshooting

### Common Issues and Solutions

**Issue: "Redirect URI mismatch" error**
- **Solution**: Double-check that the redirect URL in Shopify exactly matches the one provided by FlowMattic, including the protocol (https://) and path.

**Issue: "Insufficient permissions" when running workflows**
- **Solution**: Go back to your app settings in Shopify, click "Select scopes," and ensure all necessary scopes are selected for the operations you want to perform.

**Issue: "Invalid Client ID or Secret"**
- **Solution**: Make sure you copied the entire Client ID and Secret without any extra spaces. Try copying them again.

**Issue: Can't find "Build apps in Dev Dashboard" button**
- **Solution**: Ensure you have admin permissions on your Shopify store. Only store owners and staff with full permissions can create custom apps.

---

## Next Steps

Once connected, you can:
- Create automated workflows that trigger when events happen in your Shopify store
- Automatically create or update products, orders, and customers
- Send data from Shopify to other apps and services
- Build custom automation workflows tailored to your business needs

---

## Additional Resources

- [Shopify App Development Documentation](https://shopify.dev/docs/apps)
- [FlowMattic Shopify Integration](https://flowmattic.com/integration/shopify)
- [Shopify API Scopes Reference](https://shopify.dev/docs/api/usage/access-scopes)

---

## Need Help?

If you encounter any issues during this process:
- Check the FlowMattic documentation for specific integration guides
- Contact FlowMattic support for assistance with connection issues
- Visit Shopify Help Center for questions about app development permissions

---

# How to Create MCP Tools from Your Installed Integrations?

Source: https://support.flowmattic.com/kb/article/125/how-to-create-mcp-tools-from-your-installed-integrations

FlowMattic allows you to expose your installed integrations as MCP (Model Context Protocol) tools. This enables AI assistants like Claude, ChatGPT, and other MCP-compatible clients to interact with your WordPress integrations directly.

---

## Overview

The MCP Server feature in FlowMattic transforms your existing integrations into AI-accessible tools. Once configured, AI assistants can:

- Execute actions from your installed integrations
- Access data through authenticated API connections
- Perform automated tasks on your behalf

---

## Prerequisites

Before adding MCP tools, ensure you have:

- FlowMattic version 5.5.0 or higher installed
- At least one integration installed in FlowMattic
- For integrations requiring authentication, a configured Connect in FlowMattic Connects

---

## Step-by-Step Guide

### Step 1: Navigate to MCP Server admin page

Go to **FlowMattic → MCP Server** in your WordPress Admin Panel.

This is the central hub for managing all your MCP tools and configurations.

---

### Step 2: Add Integration Tools

Click the **"Add Integration Tools"** button.

A modal will open displaying a list of all available integrations you have installed in FlowMattic.

![MCP Server - Add integration tools button.png](/storage/kb-images/6b0635d38a-inline.png)

---

### Step 3: Select an Integration

Choose the integration you want to add MCP Server tools for by clicking on the application card.

You'll see the integration's available actions that can be converted into MCP tools.

![MCP Server - create tool from integration.png](/storage/kb-images/a68ef2fd45-inline.png)

---

### Step 4: Choose Tools to Add

You will see a modal with the list of available MCP Server tools for that integration.

1. Review the available tools/actions
2. Select the tools you want to add by checking the corresponding checkboxes
3. Click the **"Add Selected Tools"** button

![MCP Server - add mcp tools for integration.png](/storage/kb-images/28c019799b-inline.png)
---

### Step 5: Start Using Your Tools

The selected MCP Server tools will be added to the chosen integration immediately.

You can now start using them with any MCP-compatible AI assistant by connecting to your FlowMattic MCP Server endpoint.

---

## Authentication Requirements

> **Important:** If your integration requires authentication (API keys, OAuth, etc.) that is configured in FlowMattic Connects, make sure to set up the Connect first before adding MCP Server tools.

### Setting Up Authentication

1. Go to **FlowMattic → Connects**
2. Add a new connection for your integration
3. Complete the authentication process
4. Return to MCP Server to add tools

Without proper authentication, the MCP tools will not be able to execute actions that require API access.

---

## Removing MCP Tools

If you need to remove any MCP Server tools from an integration:

1. Go to **FlowMattic → MCP Server**
2. Find the tool you want to remove
3. Click the **action button** (three dots icon) on the tool card
4. Select **"Remove Tool"** from the dropdown menu
5. Confirm the removal in the popup modal

![MCP Server - Delete tool.png](/storage/kb-images/5c10087fdd-inline.png)

The tool will be removed from the integration and will no longer appear in the MCP Server tools list.

---

## Use Cases

### Customer Support Automation
Add CRM integration tools to let AI assistants look up customer information, create tickets, or update records.

### Content Management
Expose WordPress or CMS tools for AI-powered content creation and management.

### E-commerce Operations
Add WooCommerce or other e-commerce tools for order lookups, inventory checks, and customer management.

### Communication Tools
Enable AI assistants to send emails, Slack messages, or SMS notifications through your configured integrations.

---

## Best Practices

1. **Start Small** - Begin with a few essential tools and expand as needed
2. **Test Thoroughly** - Verify each tool works correctly before deploying to production
3. **Secure Your Connections** - Ensure all OAuth tokens and API keys are properly configured
4. **Monitor Usage** - Keep track of which tools are being used and how frequently
5. **Update Regularly** - Keep FlowMattic and your integrations up to date for the latest features and security patches

---

## Troubleshooting

### Tools Not Appearing

- Ensure the integration is properly installed
- Check that FlowMattic is updated to version 5.5.0 or higher
- Refresh the page and try again

### Authentication Errors

- Verify your Connect is properly configured
- Check if OAuth tokens have expired and need refreshing
- Ensure API keys have the necessary permissions

### MCP Client Connection Issues

- Confirm your MCP Server endpoint URL is correct
- Check that your WordPress site is accessible from the AI client
- Verify any firewall or security plugins are not blocking the connection

---

# How to create workflow

Source: https://support.flowmattic.com/kb/article/2/how-to-create-workflow

Here's a step-by-step guide on how to create a new workflow, add trigger and action steps, and finally, set the workflow Live to start accepting data and execute it.

* * *

### 1\. Go to FlowMattic — Dashboard

When you're logged-in to your WordPress site, go to FlowMattic -&gt; Dashboard admin page. You'll be presented with a admin page with navigation to various admin pages, welcome message, your recent workflows, your stats etc.

### 2\. Click on Create Workflow Button in Start From Scratch section

To create a new workflow, you need to click on the Create Workflow button on the in the Start From Scratch section in your FlowMattic dashboard. It will create a new workflow, and redirect you to the Visual Workflow Editor to edit your workflow.

![](/storage/kb-images/5fdf925081-Zight-2024-12-21-at-2.25.16-AM.png)

### 3\. Choose your trigger application

The Trigger Step is the starting point of your workflow, providing the necessary data or executing tasks at a scheduled time. By default, the Webhook app is preselected, but you can customize it to suit your needs. To choose a different application, click on the Trigger Step, then click the **Change** button to select your preferred app for seamless workflow integration.

![](/storage/kb-images/853bfdb317-Screenshot-2024-12-04-235655.png)

### 4\. Choose your preferred application from the list

Once you click on the **Change** button, you’ll be presented with a list of applications displayed with their icons and titles. Select the application you want to use to pull data for the workflow.Eg. Contact Form 7.

![](/storage/kb-images/c68eec92b0-Screenshot-2024-12-05-022331.png)

### 5\. Select the application event that will trigger the workflow

Once you choose your trigger application for the workflow, you'll see the list of events as next step. Choose your trigger event ( An action performed by the selected application that will pass data to your workflow. ) to proceed further.

![](/storage/kb-images/c7a4cc753f-Screenshot-2024-12-05-022820.png)

### 6\. Additional Configuration Options

Depending on the chosen application and trigger event, the corresponding configuration options will be displayed under the **Configure** tab, allowing for further customization and setup.

![](/storage/kb-images/5543fbc387-Screenshot-2024-12-05-023257.png)

In case there's no configuration required, the configure tag might shows as blank. Just click on the Test tab link and you should be able to proceed to the next tab.

### 7\. Capture Response

Once you are done with setting up the required configuration for the trigger, head over to the last tab called "Test", where you need to capture response, which will be used to map with different data points in further action steps in the workflow. Click the capture response button, and submit a new form from Contact Form 7 form. ( Contact Form 7 is used to demonstrate purpose only. You will need to send the data from your selected app to the trigger depend on the configuration. )

![](/storage/kb-images/5aa2edbba4-capture-response-1.png "capture-response")

Once you submit the response, it will be added to the responses list and you can choose which response you want to use within the workflow for mapping. To change the response, just click the response to view, then click the button "Use selected response" to use the selected response for mapping. Max. 5 last saved responses will be displayed in the Responses.

### \# Adding Action Steps

To add action steps to the workflow, just click the + button at the bottom of the trigger step. Clicking this button will add a new step to the workflow and opens up the Action App selection popup.

Once the popup opens, search for the required app for this step and click on the app name to select it. Once you select the app, the step settings popup will open, where you need to set the configuration required for this app to work in the workflow step.

**Understanding the Settings Popup Tabs in FlowMattic**

The **Settings Popup** is a key interface in FlowMattic that allows you to configure and manage actions, conditions, and tests within your workflows. Here's a breakdown of the tabs and their features to help you get the most out of them.

##### **1\. Setup Tab**

- **Purpose**: Configure the app and action/event for the selected step in your workflow.

- **Features**:
    - **App Selection**: Choose the app (e.g., API by FlowMattic) you want to interact with.
    
    - **Action Event**: Define the specific action to perform, such as GET, POST, or another API request.

- **Use Case**: For example, selecting the GET method allows you to fetch data from an external API.

##### **2\. Configure Tab**

- **Purpose**: Customize the specific parameters and fields required for the chosen action.

- **Features**:
    - Set input fields for dynamic values or hardcoded data.
    
    - Map data from previous steps to be used in this action.

- **Use Case**: Configure the URL and headers for an API request or specify fields for creating a new record in a database.

##### **3\. Conditions Tab**

- **Purpose**: Define conditions that determine whether the action will execute.

- **Features**:
    - Add conditional logic, such as "Execute this step only if certain conditions are met."
    
    - Skip execution or ignore errors to control workflow behavior dynamically.

- **Use Case**: For example, only execute an API call if the value in a previous step matches a certain condition.

##### **4\. Test Tab**

- **Purpose**: Test the action to ensure it’s configured correctly before running the full workflow.

- **Features**:
    - Send test requests or trigger a test action to verify the setup.
    
    - View response data to confirm the action works as expected.

- **Use Case**: Test an API request to ensure the correct data is fetched or sent before enabling the workflow.

![](/storage/kb-images/b4f0a0ec4e-action-step-settings-922x1024.png "action step settings")

### **How These Tabs Work Together**

When setting up a workflow step:

1. Start in the **Setup Tab** to select the app and action.

3. Move to the **Configure Tab** to specify the necessary inputs and parameters.

5. Use the **Conditions Tab** to define when and how the action should run.

7. Test the action in the **Test Tab** to ensure it's functioning as intended.

These tabs provide a structured way to build robust, flexible, and error-free workflows in FlowMattic.

Once you are done with setting up the actions steps, repeat these steps to add new actions to the workflow.

After adding all the necessary steps and testing them, click on the Toggle button near admin menu to publish the workflow in Live mode. After publishing the workflow, it will get executed after the trigger step is triggered with new data ( like form submission in Contact Form 7 ) and continue through the different action steps in your workflow.

---

# How to Effectively Use the Delay Module in Workflows

Source: https://support.flowmattic.com/kb/article/52/how-to-effectively-use-the-delay-module-in-workflows

The Delay module is a powerful tool designed to pause workflow execution for a specified duration or until a specific date and time. This feature is ideal for scenarios where timing is critical, such as scheduling tasks, sending notifications, or delaying actions for a defined period. Below is a detailed guide to help you understand and utilize the Delay module effectively.

### Supported Delay Periods
You can configure the Delay module to pause execution for the following durations:
- **Seconds**
- **Minutes**
- **Hours**
- **Days**
- **Weeks**
- **Specific Date and Time**

### Common Use Cases
Here are some practical scenarios where the Delay module can be applied:

- **Email Scheduling**: Send a welcome email or follow-up message a few hours or days after a user registers on your platform.
- **Reminder Notifications**: Delay sending reminders for tasks, appointments, or events until the appropriate time.
- **Social Media Management**: Schedule posts to be published at specific times to maximize audience engagement.
- **Customer Support Follow-ups**: Wait for a certain duration before sending a follow-up email or feedback request after resolving a ticket.
- **Subscription Renewals**: Notify users a week before their subscription expires.

### Step-by-Step Guide to Using the Delay Module
1. **Add a New Step**: Open your workflow editor and click on the "`+`" icon to add a new step.
2. **Search and Select the Module**: Look for the "`Delay`" module in the search bar and click to add it to your workflow.
3. **Configure Delay Settings**:
   - Choose the desired delay period (e.g., seconds, minutes, hours, etc.).
   - Alternatively, set a specific date and time for the delay.
4. **Save and Execute**: Save your workflow changes and execute the workflow in live mode.

### Tips for Optimal Use
- **Plan Ahead**: Use the Delay module to align actions with specific events or deadlines.
- **Combine with Other Modules**: Pair the Delay module with notification or action modules to create seamless, time-based workflows.
- **Test Your Workflow**: Before running the workflow in a live environment, test it to ensure the delay settings are configured correctly.

 
 :::Info
Note: Delay module depends on your WordPress site cron jobs. Make sure your site is getting enough traffic and cron jobs are working properly.  Learn more about [fixing cron job](https://support.flowmattic.com/kb/article/46/authentication-keeps-expiring-or-delay-not-working) issue.
 :::

By integrating the Delay module into your workflows, you can automate time-sensitive tasks efficiently, ensuring that actions are executed at the right moment. This not only enhances productivity but also improves user experience by delivering timely responses and updates.

---

# How to Embed Table on Frontend of your website?

Source: https://support.flowmattic.com/kb/article/15/how-to-embed-table-on-frontend-of-your-website

Displaying tables on the frontend of your website is an excellent way to share structured data with your visitors. Whether it's showcasing product reviews, tracking sales, or displaying user-generated content, embedding tables makes information accessible and visually appealing. With FlowMattic, you can easily add advanced, filterable tables to any page on your website without relying on expensive plugins.

* * *

### **Step-by-Step Guide to Embed a Table Using a Shortcode**

Here’s how you can use the FlowMattic shortcode to display a table on the frontend:

1. **Get the Table Name and Database**:
    - Navigate to the **Tables Admin Screen** in FlowMattic.
    
    - Locate the name of the table you want to embed and note the database it’s stored in (e.g., "local" or an external database).

3. **Copy the Shortcode**: Use the following shortcode format:  
    `[flowmattic_table table_name="Product Reviews" database="local" filter_column="product_id" filter_value="4"]`  
    Replace the parameters (explained below) to fit your specific requirements.

5. **Add the Shortcode to a Page**:
    - Open the **WordPress Page Editor** (Gutenberg, Classic Editor, or your preferred page builder).
    
    - Paste the shortcode into the desired section of the page.
    
    - Save or publish the page to display the table on your website.

7. **Preview the Table**:
    - Visit the page on your website to ensure the table is displayed correctly and filters are applied as intended.

* * *

### **Understanding the Shortcode Parameters**

The shortcode comes with several parameters to customize the table display:

- **`table_name`**:
    - The name of the table you want to embed.
    
    - Example: `"Product Reviews"`.
    
    - Get this value from the Tables Admin Screen.

- **`database`**:
    - Specifies the database where the table is stored.
    
    - Example: `"local"` for WordPress database or the name of an external database connected to FlowMattic.

- **`filter_column`**:
    - Filters the table data based on a specific column.
    
    - Example: `"product_id"` to filter by a column named "Product ID."

- **`filter_value`**:
    - The value in the column to filter the table by.
    
    - Example: `"4"` to display rows where the "Product ID" column has a value of 4.

By adjusting these parameters, you can tailor the table display to meet your needs, such as showing only specific rows or filtering data dynamically.

<figure>

![](/storage/kb-images/c8f5df1e68-embeded-table-on-frontend.png "embedded table on frontend")

<figcaption>

Embedded Table View on Frontend

</figcaption>

</figure>

* * *

### **Conclusion**

Embedding tables on the frontend of your website using FlowMattic is simple, flexible, and powerful. You don’t need to invest in expensive table plugins to showcase advanced tables with dynamic filtering. With FlowMattic’s shortcode functionality, you can easily share critical data with your visitors while maintaining full control over how it’s displayed. Whether for e-commerce, analytics, or content presentation, FlowMattic has you covered!

---

# How to Enable WP Debug Mode in WordPress: A Step-by-Step Guide

Source: https://support.flowmattic.com/kb/article/69/how-to-enable-wp-debug-mode-in-wordpress-a-step-by-step-guide

### Introduction
Enabling the WP Debug mode in WordPress is essential for troubleshooting and identifying issues on your website. This guide will walk you through the process of turning on the debug mode by editing the `wp-config.php` file using FTP/SFTP, cPanel, or File Manager.

### Prerequisites
- Access to your WordPress installation files.
- FTP/SFTP client, cPanel, or File Manager access.
- A text editor to modify the `wp-config.php` file.

### Step-by-Step Guide

1. **Access Your WordPress Files**
   - Use an FTP/SFTP client (e.g., FileZilla) or log in to your hosting control panel (e.g., cPanel).
   - Navigate to the root directory of your WordPress installation. This is typically the folder named `public_html` or the folder containing your WordPress files.

2. **Locate the `wp-config.php` File**
   - Find the `wp-config.php` file in the root directory of your WordPress installation.
   - Download a backup of the file before making any changes to ensure you can restore it if needed.

3. **Edit the `wp-config.php` File**
   - Open the `wp-config.php` file in a text editor.
   - Scroll down to find the line that says: `/* That's all, stop editing! Happy publishing. */`

4. **Add Debugging Constants**
   - Just before the line mentioned above, add the following constants:
     ```php
     // Turn ON the debug mode
     define( 'WP_DEBUG', true );

     // Turn ON the debug logs
     define( 'WP_DEBUG_LOG', true );

     // Turn OFF the log display on frontend
     define( 'WP_DEBUG_DISPLAY', false );
     ```
   - Ensure no conflicting constants are already defined in the file. If you find any, remove or comment them out.

5. **Save and Upload the File**
   - Save the changes to the `wp-config.php` file.
   - If you used an FTP/SFTP client, upload the modified file back to the server, replacing the existing one.

6. **Verify Debug Mode is Enabled**
   - Visit your WordPress site and check the debug log file, which is typically located in the `wp-content` directory with the name `debug.log`.
   - Ensure that errors are being logged but not displayed on the frontend.

### Tips
- Always create a backup of your `wp-config.php` file before making any changes.
- Use a staging environment to test changes before applying them to your live site.
- Remember to turn off debugging in a production environment to avoid exposing sensitive information.

### Additional Context
- The `WP_DEBUG` constant enables debugging mode in WordPress.
- The `WP_DEBUG_LOG` constant saves errors to a log file for easier review.
- The `WP_DEBUG_DISPLAY` constant prevents error messages from being displayed on the frontend, ensuring a better user experience.

By following these steps, you can enable WP Debug mode in WordPress effectively and safely troubleshoot your website issues.

---

# How to Find Records from FlowMattic Tables in Multiple Ways

Source: https://support.flowmattic.com/kb/article/66/how-to-find-records-from-flowmattic-tables-in-multiple-ways

FlowMattic Tables is a powerful feature within the FlowMattic automation plugin that allows users to store, retrieve, and manage structured data directly inside their WordPress dashboard—similar to a mini database. You can create tables with custom fields and use them to track leads, manage form submissions, create dynamic datasets, and more, all without needing external tools like Google Sheets or Airtable.

One of the key actions in FlowMattic Tables is the **"Find Record"** action. As of FlowMattic v5.1.0, this action has received two important enhancements:

- Support for **filtering using two columns** to find more accurate results.
- Ability to search using either **exact match** or **contains** logic on column values.

> ⚠️ **Important:** The "Find Record" action only returns **one matching record** (the first matched result). If there are multiple matching records, only the first one will be returned. Use filters wisely to narrow it down.

---

## 🔎 Why Use the "Find Record" Action?

The "Find Record" action is used in your automation workflows to locate data within a FlowMattic table. For example:

- Lookup a user by email to fetch their stored details.
- Find a product by SKU or ID before processing an order.
- Retrieve a ticket based on status and priority for support workflows.

---

## 🆕 New in v5.1.0 — Dual Column Filtering

### ✅ What's New?
You can now filter by **two columns** instead of just one. The first column is required, while the second column is optional.

### 📘 Use Case: Finding Unique Users

Let’s say your table has multiple entries with the name `John`. If you only search by name, you may get multiple results. But since the Find Record action returns only **one record**, you might not get the one you're looking for.

To avoid this, you can add an additional filter—like `Email = john@example.com`. This ensures that FlowMattic returns the most accurate match.

#### More Examples:
- Searching by **Product Name** may return multiple results, but adding **SKU** ensures it finds the right product.
- Filtering leads by **Phone Number** alone might not be unique. Adding **City** or **Form ID** as a second filter narrows it down to a unique match.

This enhancement improves data accuracy and helps ensure you're getting the **correct record** from your table.

---

## 🧠 New in v5.1.0 — Lookup Method (Exact vs Contains)

### ✅ What’s New?
You now have the option to choose the **lookup method** for your column value:
- **Exact** — Matches the value exactly as you provided.
- **Contains** — Returns a record where the column **contains** the specified value (partial match).

### 📘 Use Case: Partial Email or Domain Matching

Let’s say you only have part of a user's email (e.g., you know it contains `@example.com`) and you want to find a record related to them. You can use:

- **Lookup Column:** `Email`
- **Lookup Value:** `example.com`
- **Lookup Method:** `Contains`

FlowMattic will return the **first record it finds** where the email column contains `example.com`.

#### More Examples:
- Find a customer whose **name contains** `John` when you’re not sure if it’s `Johnny`, `Johnson`, or `Johnathan`.
- Lookup a support ticket where the **notes contain** the word `urgent`.
- Find a contact where the **status contains** `pending`, such as `pending-client` or `pending-approval`.

Again, since only one record is returned, it's important to make your filters specific enough to retrieve the right result.

---

## 🛠 Step-by-Step Guide: Using the Enhanced "Find Record" Action

1. **Add the "Find Record" Step**  
   In your workflow, select the FlowMattic Tables module and choose the **"Find Record"** action.

2. **Select the Table**  
   Choose the table where your data is stored.

3. **Configure the Primary Lookup**  
   - Select the required **Lookup Column** (e.g., `Name`).
   - Enter the **Lookup Value** (e.g., `John`).

4. **(Optional) Add a Second Filter**  
   - Choose an additional **Lookup Column** (e.g., `Email`).
   - Enter the corresponding **Lookup Value** (e.g., `john@example.com`).

5. **(Optional) Set the Lookup Method**  
   - Choose between **Exact** or **Contains** for partial matching.

6. **Click Continue**  
   FlowMattic will search the table using your criteria and return **only the first matching record**.

---

## ✅ Best Practices

- Always try to **combine two fields** when values might not be unique (e.g., Name + Email).
- Use the **"Contains"** method when you only have a portion of the data.
- Keep in mind: **Only one record is returned**. The more specific your filters, the better the accuracy.

---

## 🧪 Example: Lead Qualification Workflow

You receive a form submission where:
- **Name:** John
- **Email domain:** `example.com`

You set up a Find Record step that:
- Looks up `Name = John`
- And `Email contains example.com`

This way, you can find a lead even if the exact email isn't available. As long as one match is found, it will be returned for use in the next step of your workflow.

---

## Final Thoughts

These enhancements in FlowMattic v5.1.0 make the “Find Record” action more powerful and flexible. Whether you're narrowing down results using multiple filters or performing partial lookups, you now have more control—while ensuring you’re always working with just one clean, accurate record.

Try using these new filters in your next workflow, and make your automation even smarter and more reliable.

---

# How to Get Instagram App Credentials (Client ID & Secret)

Source: https://support.flowmattic.com/kb/article/123/how-to-get-instagram-app-credentials-client-id--secret

## Prerequisites

- A Facebook account
- An Instagram Business or Creator account (not personal)
- Your Instagram account must be connected to a Facebook Page

---

## Step 1: Create a Facebook Developer Account

1. Go to [developers.facebook.com](https://developers.facebook.com)
2. Click **"Get Started"** or **"Log In"** (top right)
3. Log in with your Facebook account
4. Accept the Facebook Developer terms

---

## Step 2: Create a New App

1. Click **"My Apps"** (top right) → **"Create App"**
2. Select use case: **"Other"** → Click **"Next"**
3. Select app type: **"Business"** → Click **"Next"**
4. Fill in app details:
   - **App Name**: e.g., "My Instagram Integration"
   - **App Contact Email**: Your email
   - **Business Account**: Select or create one
5. Click **"Create App"**

---

## Step 3: Add Instagram Graph API Product

1. In your app dashboard, scroll to **"Add products to your app"**
2. Find **"Instagram Graph API"** → Click **"Set Up"**
3. This adds Instagram capabilities to your app

---

## Step 4: Configure OAuth Settings

1. Go to **App Settings** → **Basic** (left sidebar)
2. Note your:
   - **App ID** (this is your Client ID)
   - **App Secret** (click "Show" to reveal - this is your Client Secret)
3. Scroll down to **"Add Platform"**:
   - Click **"+ Add Platform"** → Select **"Website"**
   - Enter your site URL: `https://your-site.com`
4. In **"App Domains"**: Add your domain (e.g., `your-site.com`)
5. Click **"Save Changes"**

---

## Step 5: Add OAuth Redirect URI

> ⚠️ **Important**: You MUST use your site's REST API endpoint as the redirect URI, NOT the default FlowMattic proxy URL. The redirect URI shown below is specific to YOUR website.

1. Go to **Facebook Login** → **Settings** (left sidebar)
   - If not visible, go to Products → Add Product → Facebook Login → Set Up
2. In **"Valid OAuth Redirect URIs"**, add your site's Instagram OAuth endpoint:
   ```
   https://your-site.com/wp-json/flowmattic/v1/auth/instagram
   ```
   *(Replace `your-site.com` with your actual domain)*

   **Example**: If your site is `mysite.flowmattic.com`, use:
   ```
   https://mysite.flowmattic.com/wp-json/flowmattic/v1/auth/instagram
   ```
3. Click **"Save Changes"**

---

## Step 6: Request Permissions (For Live Mode)

1. Go to **App Review** → **Permissions and Features**
2. Request these permissions:
   - `instagram_basic`
   - `instagram_content_publish`
   - `instagram_manage_comments`
   - `instagram_manage_insights`
   - `pages_show_list`
   - `pages_read_engagement`
   - `business_management`

> **Note**: For testing, you can use **Development Mode** without approval. Only your account (and app admins/testers) can authenticate.

---

## Step 7: Add Test Users (Development Mode)

1. Go to **App Roles** → **Roles** (left sidebar)
2. Under **"Testers"**, click **"Add Testers"**
3. Enter the Facebook username of anyone who needs to test
4. They must accept the invitation from their Facebook settings

---

## Step 8: Connect Instagram to Facebook Page

Before authenticating, ensure your Instagram is properly connected:

1. Open **Instagram App** → **Settings** → **Account** → **Sharing to other apps**
2. Select **Facebook** and link to your Facebook Page
3. OR on Facebook: Go to your **Page Settings** → **Instagram** → **Connect Account**

---

## Step 9: Use Credentials in FlowMattic

1. In FlowMattic, go to **Connects** → **Add New**
2. Search for **"Instagram"**
3. Enter:
   - **Client ID**: Your Facebook App ID
   - **Client Secret**: Your Facebook App Secret
4. Click **Connect** to authenticate

---

## Troubleshooting

| Issue | Solution |
|-------|----------|
| "App not authorized" | Add yourself as a Tester in App Roles |
| "Invalid redirect URI" | Ensure the redirect URI matches exactly (including https://) |
| "No redirect URI in the params" | For local sites (.local domain): Use ngrok and set up the redirect URI filter (see above). For live sites: Ensure the URI in Facebook matches your site's REST endpoint exactly. |
| "No Instagram accounts found" | Connect your Instagram to a Facebook Page first |
| "Permissions denied" | Request permissions in App Review (for live mode) |
| Connection popup closes immediately | Check that your Facebook App has "Facebook Login" product added and configured |

---

## Quick Reference

| Setting | Where to Find |
|---------|---------------|
| **Client ID** | App Settings → Basic → App ID |
| **Client Secret** | App Settings → Basic → App Secret |
| **Redirect URI** | `https://your-site.com/wp-json/flowmattic/v1/auth/instagram` |

---

# How to Resize the Settings Popup Window in FlowMattic

Source: https://support.flowmattic.com/kb/article/65/how-to-resize-the-settings-popup-window-in-flowmattic

Starting with v5.1.0, FlowMattic now allows you to **resize the settings popup window** while configuring any step in your workflow. This enhancement makes it easier to view longer content, avoid unnecessary **horizontal scrolling**, and work efficiently on smaller or wide screens.

Whether you're mapping dynamic fields, writing large expressions, or if your settings popup is hiding the workflow steps due to small screen size and you want to see your workflow steps alongside the settings panel—this feature will give you more flexibility and control.

![Zight Recording 2025-04-14 at 12.14.00 AM.gif](/storage/kb-images/6c68a7fe9b-inline.png)

*Example: Resize handles visible when hovering on the left and bottom edges.*

---

## 🔧 Why This Feature is Useful

- ✅ Reduces **horizontal scrolling** when content exceeds visible width  
- ✅ Helps on **smaller screen sizes** by allowing a larger view of input fields  
- ✅ Keeps the **workflow canvas visible** while editing steps  
- ✅ Useful when working with **long dynamic tokens** or large configuration blocks

> 📝 **Note:** This does **not impact vertical scrolling** unless the content fits fully within the resized window height.

---

## 📝 Step-by-Step: How to Resize the Settings Window

### 1. **Open Any Workflow Step**
- In your FlowMattic workflow, click on any step (trigger, action, or condition) to open the configuration panel.

### 2. **Hover to Reveal Resize Handles**
- Move your mouse to the **left edge** or **bottom edge** of the settings popup.
- You will see **arrow-like resize handles** appear **only when you hover** over these edges.

### 3. **Click and Drag to Resize**
- Drag horizontally from the left edge to adjust **width**.
- Drag vertically from the bottom edge to adjust **height**.
- The popup will immediately resize and adapt its contents to fit.

### 4. **Continue Editing Seamlessly**
- You can now configure your step with a broader view.
- The resized popup helps keep both your settings and workflow canvas visible together.

---

## 🧠 Important Notes

- 🔄 **Resize is session-based:** The new size will persist **only during the current browser session**.  
  - If you refresh, restart your browser, open the editor in a new browser, or switch to incognito mode, the popup will reset to its default size.
- 👆 **Hover is required:** Resize indicators appear **only when you hover** your mouse on the edge of the popup.
- 📏 You can resize both **width (left)** and **height (bottom)** independently to suit your preference.

---

## 💡 Pro Tips

- When working with **code, HTML blocks, or JSON responses**, widen the popup for easier editing.
- On **larger monitors**, take advantage of the screen space by expanding the popup fully.
- If using many **dynamic tokens**, a wider view helps see full token names without horizontal scroll.

---

This small but powerful feature improves your day-to-day workflow building experience in FlowMattic. Give it a try and adjust your workspace the way that suits you best!

---

# How to Send Iterator Response to Another Workflow Without Mapping All Fields Individually

Source: https://support.flowmattic.com/kb/article/94/how-to-send-iterator-response-to-another-workflow-without-mapping-all-fields-individually

FlowMattic's latest enhancement to the Iterator and Webhook Outgoing modules introduces a streamlined approach for sending iterator data to external workflows. Instead of manually mapping each field from your iterator response, you can now use a single mapping to transfer the entire data structure seamlessly. The receiving webhook will get the exact same data structure as the iterator output, making it effortless to pass data between workflows.

## The Challenge with Traditional Mapping

Previously, when sending iterator data through webhooks, users had to:
- Map each individual field from the iterator response
- Manually configure every data parameter
- Update mappings whenever new fields were added to the source data
- Spend considerable time on repetitive mapping tasks

This process was not only time-consuming but also error-prone and difficult to maintain.

## The New Solution: Single Field Mapping

With the new feature, FlowMattic automatically packages the entire iterator response into a single JSON object under the key `current_array_item`. When you map this to the `iterator_item` key in your webhook, FlowMattic intelligently sends the data in the same format as the original iterator output, eliminating any wrapper objects and maintaining the exact structure.

## How It Works

### Step 1: Set Up Your Iterator

Configure your iterator as usual to loop through your data array. The iterator will process each item and make it available for the next steps in your workflow.

### Step 2: Configure the Webhook Outgoing Module

In your Webhook Outgoing module configuration:

1. **Webhook URL**: Enter your destination webhook URL
2. **Data Parameters**: 
   - Set the key as `iterator_item`
   - Map the value to `{{iterator2.current_array_item}}` (where `iterator2` is your iterator step name)

```json
Data Parameters:
Key: iterator_item
Value: {{iterator2.current_array_item}}
```

### Step 3: Add Additional Data (Optional)

You can still add other parameters alongside the iterator data:

```json
Data Parameters:
Key: iterator_item
Value: {{iterator2.current_array_item}}

Key: new_data
Value: {{iso_8601_utc}}
```

## Response Examples

### Iterator Output Example

When your iterator processes an item, the `current_array_item` contains the complete data structure:

```json
{
  "id": 0,
  "firstName": "Farley",
  "lastName": "Cain",
  "email": "farleycain@uniworld.com",
  "address": "944 Hunts Lane, Stockwell, Indiana, 3655",
  "status": "Canceled"
}
```

### Webhook Request Body

The receiving webhook will get the **exact same structure** as the iterator output:

```json
{
  "id": 0,
  "firstName": "Farley",
  "lastName": "Cain",
  "email": "farleycain@uniworld.com",
  "address": "944 Hunts Lane, Stockwell, Indiana, 3655",
  "status": "Canceled",
  "new_data": "2025-08-05T17:31:02+00:00"
}
```

### Multiple Iterator Items

For each iteration, a separate webhook request is sent with the same clean structure:

**First Request:**
```json
{
  "id": 0,
  "firstName": "Farley",
  "lastName": "Cain",
  "email": "farleycain@uniworld.com",
  "address": "944 Hunts Lane, Stockwell, Indiana, 3655",
  "status": "Canceled",
  "new_data": "2025-08-05T17:31:02+00:00"
}
```

**Second Request:**
```json
{
  "id": 14,
  "firstName": "Priscilla",
  "lastName": "Robinson",
  "email": "priscillarobinson@uniworld.com",
  "address": "504 Ridge Boulevard, Heil, Vermont, 6244",
  "status": "Waiting",
  "new_data": "2025-08-05T17:31:02+00:00"
}
```

## Benefits

### 1. Identical Data Structure
- **Key Advantage**: The webhook receives the exact same data structure as the iterator output
- **No Wrapper Objects**: Clean, direct data transfer without nested objects
- **Seamless Integration**: Perfect for passing data between FlowMattic workflows

### 2. Simplified Configuration
- **Before**: Map 6+ individual fields
- **After**: Map 1 field containing all data

### 3. Dynamic and Maintenance-Free
- New fields added to source data are automatically included
- No need to update webhook configurations when data structure changes
- Works regardless of how your data evolves over time

### 4. Time Efficiency
- Reduces setup time by up to 80%
- Eliminates repetitive mapping tasks

### 5. Error Reduction
- Less manual configuration means fewer chances for mapping errors
- Consistent data structure across all webhook calls

## Best Practices

### 1. Keep It Simple
The beauty of this feature is its simplicity. In most cases, you only need:

```json
Data Parameters:
Key: iterator_item
Value: {{iterator2.current_array_item}}
```

### 2. Add Metadata When Needed
If you need additional context, add it alongside the iterator data:

```json
Data Parameters:
Key: iterator_item
Value: {{iterator2.current_array_item}}

Key: processed_at
Value: {{iso_8601_utc}}

Key: source_workflow
Value: {{workflow.name}}
```

### 3. Test Your Configuration
Use the "Test Action" button to verify that your receiving webhook gets the expected data structure.

## Troubleshooting

### Common Issues

**Issue**: Receiving webhook doesn't get the expected data structure
**Solution**: Verify that you're using `iterator_item` as the key name and mapping to `current_array_item`

**Issue**: Missing fields in webhook requests
**Solution**: Ensure your iterator is properly configured and test the iterator output before setting up the webhook

**Issue**: Data not updating when source changes
**Solution**: This feature automatically includes new fields, so check if your iterator source is actually providing the updated data

## Migration from Old Method

If you're currently using individual field mapping, here's how to migrate:

### Before (Individual Mapping):
```json
Data Parameters:
Key: id
Value: {{iterator2.id}}

Key: firstName  
Value: {{iterator2.firstName}}

Key: lastName
Value: {{iterator2.lastName}}

Key: email
Value: {{iterator2.email}}

Key: address
Value: {{iterator2.address}}

Key: status
Value: {{iterator2.status}}
```

**Result**: Webhook receives exactly what you mapped
```json
{
  "id": 0,
  "firstName": "Farley",
  "lastName": "Cain",
  "email": "farleycain@uniworld.com",
  "address": "944 Hunts Lane, Stockwell, Indiana, 3655",
  "status": "Canceled"
}
```

### After (Single Mapping):
```json
Data Parameters:
Key: iterator_item
Value: {{iterator2.current_array_item}}
```

**Result**: Webhook receives the complete iterator output automatically
```json
{
  "id": 0,
  "firstName": "Farley",
  "lastName": "Cain",
  "email": "farleycain@uniworld.com",
  "address": "944 Hunts Lane, Stockwell, Indiana, 3655",
  "status": "Canceled"
}
```

## Real-World Use Cases

### 1. Workflow Chaining
Pass complete customer records from one workflow to another for different processing stages.

### 2. Data Synchronization
Send entire product catalogs item by item to external systems without worrying about field changes.

### 3. Notification Systems
Forward complete event data to notification workflows while maintaining all original context.

## Conclusion

This new feature revolutionizes how you handle iterator data in FlowMattic workflows. By providing the exact same data structure at the receiving end, it eliminates complexity and ensures seamless data flow between workflows. Whether your data has 5 fields or 50 fields, whether it changes tomorrow or next month, your webhook configuration remains simple and reliable.

The key insight is that you no longer need to think about individual field mapping – just pass the entire iterator response with a single mapping, and FlowMattic handles the rest intelligently. This makes building robust, maintainable automation workflows faster and more intuitive than ever before.

---

# How to Set Up a Custom Domain for Your FlowMattic Link Shortener?

Source: https://support.flowmattic.com/kb/article/119/how-to-set-up-a-custom-domain-for-your-flowmattic-link-shortener

This guide will walk you through setting up your own custom domain (e.g., `go.yourdomain.com`) for your short links powered by FlowMattic Short Links.

## What You'll Achieve

Instead of using `fmtk.in/abc123`, your short links will use your own branded domain like `go.yourdomain.com/abc123`.

## Prerequisites

- Access to your domain's DNS settings (via your domain registrar or DNS provider)
- A subdomain you want to use (e.g., `go`, `link`, `s`, or any name you prefer)
- 5-10 minutes for setup and DNS propagation

---

## Step 1: Choose Your Subdomain

Decide what subdomain you want to use for your short links. Popular choices include:
- `go.yourdomain.com`
- `link.yourdomain.com`
- `s.yourdomain.com`
- `short.yourdomain.com`

For this guide, we'll use `go.yourdomain.com` as an example.

---

## Step 2: Add CNAME Record to Your DNS

### For Cloudflare Users

1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com)
2. Select your domain from the list
3. Click on **DNS** in the left sidebar
4. Click **Add record** button
5. Configure the record:
   - **Type**: Select `CNAME`
   - **Name**: Enter your subdomain (e.g., `go`)
   - **Target**: Enter `fmtk.in`
   - **Proxy status**: Enable (Orange cloud icon should be ON)
   - **TTL**: Auto
6. Click **Save**

### For Other DNS Providers (GoDaddy, Namecheap, etc.)

1. Log in to your domain registrar's control panel
2. Find the DNS Management or DNS Settings section
3. Add a new DNS record with these details:
   - **Type**: CNAME
   - **Host/Name**: Your subdomain (e.g., `go`)
   - **Points to/Target/Value**: `fmtk.in`
   - **TTL**: 3600 (or leave as default)
4. Save the record

---

## Step 3: Configure SSL Settings (Cloudflare Users Only)

If you're using Cloudflare, you need to configure SSL settings to avoid redirect errors:

1. In your Cloudflare dashboard, go to **SSL/TLS** section
2. Under **Overview**, set the SSL/TLS encryption mode to **Full**
   - ⚠️ Do NOT use "Flexible" - this will cause redirect loops
   - ✅ Use "Full" for proper SSL encryption
3. (Optional) Go to **SSL/TLS → Edge Certificates**
4. Enable **Always Use HTTPS** for automatic HTTP to HTTPS redirect

---

## Step 4: Wait for DNS Propagation

DNS changes can take anywhere from **5 minutes to 48 hours** to propagate globally, though it's typically complete within 15-30 minutes.

You can check the propagation status using these tools:
- [DNS Checker](https://dnschecker.org)
- [What's My DNS](https://www.whatsmydns.net)

Enter your full subdomain (e.g., `go.yourdomain.com`) and check if the CNAME record points to `fmtk.in`.

---

## Step 5: Configure Custom Domain in FlowMattic

Once your DNS is set up and propagated, configure your custom domain in your FlowMattic workflow:

1. Open your workflow in FlowMattic
2. Navigate to the **Link Shortener** action step
3. Go to the **Configure** tab
4. In the **Custom Domain (Optional)** field, enter your full custom domain (e.g., `go.yourdomain.com`)
5. Enter the URL you want to shorten in the **URL to Shorten** field
6. Save your workflow configuration

FlowMattic will now automatically use your custom domain when generating short links in this workflow.

---

## Step 6: Test Your Custom Domain

Verify that your custom domain is working correctly:

1. In your FlowMattic workflow, go to the **Test** tab of the Link Shortener action
2. Click **Test Action** to generate a test short link
3. FlowMattic will create a short link using your custom domain (e.g., `https://go.yourdomain.com/abc123`)
4. Copy the generated short link from the test results
5. Open the link in your browser to verify:
   - The link should redirect to the destination URL without errors
   - Check that the browser shows a secure connection (🔒 padlock icon)
   - Verify there are no redirect loops or SSL warnings

If the link works correctly, your custom domain is properly configured! You can now use it in your live workflows.

![link shortener - custom domain.png](/storage/kb-images/219023034b-inline.png)

---

## Troubleshooting

### Issue: "This site can't be reached" or DNS errors

**Solution:**
- Verify your CNAME record is correct and points to `fmtk.in`
- Wait longer for DNS propagation (up to 48 hours)
- Clear your browser cache or try in an incognito window
- Check DNS propagation at [DNS Checker](https://dnschecker.org)

### Issue: Infinite redirect loop / "Too many redirects"

**Solution (Cloudflare users):**
1. Go to Cloudflare → **SSL/TLS** → **Overview**
2. Change encryption mode from "Flexible" to **"Full"**
3. Wait 2-3 minutes and clear your browser cache
4. Try accessing your link again

### Issue: SSL certificate warnings / "Not Secure"

**Solution (Cloudflare users):**
- Ensure Proxy status is **enabled** (orange cloud icon)
- Go to **SSL/TLS** → **Edge Certificates**
- Wait for Cloudflare to issue a certificate (usually 15-30 minutes)
- If using other DNS providers, SSL certificates are automatically handled by our service

### Issue: 404 Not Found errors

**Solution:**
- Verify your custom domain is entered correctly in the FlowMattic Link Shortener configuration
- Check that your short code/link was generated successfully
- Ensure DNS propagation is complete
- Test the link generation again using the Test Action button

### Issue: Error 520 or 522 (Cloudflare)

**Solution:**
- Check that your CNAME points to `fmtk.in` (not an IP address)
- Verify SSL/TLS mode is set to "Full"
- Disable any page rules or firewall rules that might block the connection
- Contact support if issue persists

---

## Need Help?

If you're still experiencing issues after following this guide or need any help with the setup, please submit a support ticket by login to this support site.
Please include the following information when contacting support:
- Your custom domain name
- DNS provider (Cloudflare, GoDaddy, etc.)
- Screenshot of your CNAME record
- Screenshot of your FlowMattic Link Shortener configuration
- Error message or behavior you're experiencing

---

## Summary

🎯 **Quick Checklist:**
- [ ] CNAME record added (subdomain → fmtk.in)
- [ ] SSL/TLS mode set to "Full" (Cloudflare users)
- [ ] DNS propagation complete (check at dnschecker.org)
- [ ] Custom domain configured in FlowMattic Link Shortener action
- [ ] Test Action completed successfully with custom domain link working

Once complete, all your short links generated by this workflow will use your custom branded domain! 🚀

---

# How to Set Up and Use the Email Parser Module in FlowMattic

Source: https://support.flowmattic.com/kb/article/56/how-to-set-up-and-use-the-email-parser-module-in-flowmattic

### Overview
The Email Parser Module in FlowMattic is a powerful tool that enables you to parse incoming emails and trigger workflows based on the email's content. This article provides a step-by-step guide to setting up the Email Parser trigger and utilizing its features effectively.

### Step-by-Step Guide

#### Step 1: Create a Workflow
1. Log in to your WordPress site where FlowMattic is installed
2. Create a new workflow and select the "Email Parser" app as the trigger.

#### Step 2: Configure the Email Parser
1. Navigate to the **Configure** tab.
2. Copy the custom email address provided for your workflow.
3. Use this email address to forward emails you wish to parse.

#### Step 3: Prepare for Email Capture
1. Switch to the **Test** tab.
2. Click the "Capture Response" button to prepare FlowMattic for receiving email data.

#### Step 4: Forward Emails
1. Forward the email you want to parse to the custom email address obtained in the **Configure** tab.

#### Step 5: View Parsed Content
1. Once the email is received, go to the **Test** tab.
2. Check the **Responses** section to view the parsed content.

#### Step 6: Add Workflow Actions
1. Use the parsed email content to add specific actions to your workflow.

### Parsed Email Content Details
The Email Parser extracts the following information from emails:

- **from_name**: Name of the sender.
- **from_email**: Email address of the sender.
- **to_email**: Email address of the recipient.
- **subject**: Subject of the email.
- **message_html**: HTML content of the email (encoded with HTML entities for security).
- **message_text**: Plain text content of the email.
- **date**: Date and time the email was received.
- **attachments**: Attachments in the email are uploaded to your WordPress media gallery, and their URLs are included in the parsed data.
- **emails_in_message_array**: Array of email addresses found in the email content, useful for advanced modules like Iterator or PHP Array -> Extract JSON.
- **emails_in_message_list**: Comma-separated list of email addresses found in the email content.

### Tips and Notes
- Ensure that forwarded emails are sent to the custom email address exactly as provided in the **Configure** tab.
- Use the parsed data fields to create dynamic and robust workflows.
- Regularly test the Email Parser setup to ensure consistent functionality.

### Conclusion
By following these steps, you can seamlessly set up and use the Email Parser Module in FlowMattic to automate workflows based on email content. This feature allows for efficient email management and workflow automation, saving time and effort.

---

# How to Set Up FlowMattic MCP Server in OpenAI Playground

Source: https://support.flowmattic.com/kb/article/80/how-to-set-up-flowmattic-mcp-server-in-openai-playground

### Step-by-Step Guide to Setting Up FlowMattic MCP Server in OpenAI Playground

Follow these steps to successfully integrate and configure your FlowMattic MCP Server in the OpenAI Playground environment:

---

#### **Step 1: Access OpenAI Playground**
2. OpenAI Playground at [platform.openai.com/playground](https://platform.openai.com/playground).

---

#### **Step 2: Create a New Prompt**
1. In the OpenAI Playground interface, create a new prompt.
2. Click the **Save** button to save the prompt.
3. Enter a descriptive name for your prompt (e.g., "FlowMattic MCP Integration").
4. Publish the prompt to make it active.

---

#### **Step 3: Add MCP Server Tool**
1. Locate the tools section in the playground interface.
2. Click on the **plus icon (+)** to add a new tool.
3. From the dropdown menu, select **MCP Server**.

 ![da102236-547e-4862-83f7-e0926583e9a5.png](/storage/kb-images/9e99bf41a9-inline.png)

4. Click on **Add New** to proceed.
 
 ![845ce6d2-da04-4dd4-a3a4-e1ddbfa7ec69.png](/storage/kb-images/49382a282a-inline.png)

---

#### **Step 4: Configure MCP Server Connection**
1. Fill out the MCP Server configuration form with the following details:
   - **URL Field**: Enter your FlowMattic MCP Server URL. This should be the full endpoint URL (e.g., `https://your-flowmatic-server.com/mcp`).
   - **Label**: Provide a descriptive label (e.g., "FlowMattic MCP" or "FlowMattic Automation Server").
   - **Description**: Write a brief description of the server's purpose (e.g., "FlowMattic MCP Server for automation and workflow management").
   - **Authentication**: From the dropdown, select **none** to indicate that no authentication is required.
   - **Connect**: Click the **Connect** button to establish a connection to your FlowMattic MCP Server.
     
 ![Prompts_Playground_-_OpenAI_API_2025-07-14_at_20259_PM.png](/storage/kb-images/f863af44b5-inline.png)
2. Double-check the details for accuracy.


#### **Step 5: Add Available Tools**
1. Once connected, the system will display a list of tools available on your FlowMattic MCP Server.
2. Review the list of tools.
3. Click the **Add** button below the tools list to add them to your playground environment.
 
 ![f0d87c91-6fe6-4ccf-8029-ce0f8c7cdafa.png](/storage/kb-images/32c85779c4-inline.png)

---

#### **Step 6: Test the Integration**
1. Verify that the FlowMattic MCP Server tools are now available in your OpenAI Playground.
2. Test the integration by creating prompts that utilize the FlowMattic tools and functionalities.

---

### Additional Tips:
Ensure your FlowMattic MCP Server URL is correct and accessible.

By following these steps, you can seamlessly integrate the FlowMattic MCP Server into your OpenAI Playground and leverage its automation capabilities effectively.

---

# How to Set Up FlowMattic MCP Server in Warp

Source: https://support.flowmattic.com/kb/article/73/how-to-set-up-flowmattic-mcp-server-in-warp

To configure the FlowMattic MCP Server in Warp, follow the steps below:

## Steps to Set Up:

1. **Access Warp Drive**:
    Locate the Warp Drive option in the left corner of the Warp interface and click on it.

2. **Navigate to MCP Server Settings**:
    Go to the 'Personal' section and open the MCP Server settings.

3. **Add a New Server**:
    Click on the 'Add Server' button to begin the configuration process.
    
 ![warp-settings.jpeg](/storage/kb-images/d98108ca20-inline.png)

4. **Enter JSON Configuration**:
    Add the following JSON configuration, replacing the placeholder URL with your actual FlowMattic MCP Server URL.
 ```json
{
  "flowmattic": {
    "command": "npx",
    "args": [
      "mcp-remote",
      "https://flowmattic.com/v1/mcp-server/*************",
      "--transport",
      "http-only"
    ],
    "env": {},
    "working_directory": null,
    "start_on_launch": true
  }
} 
 ```

5. **Save and Start the Server**:
    After entering the configuration, click 'Save' to store the settings. Then, click 'Start' to activate the server.
   
## Additional Tips:
 - Double-check the MCP URL from FlowMattic to ensure accuracy.
 - If you encounter any errors, verify the JSON structure and ensure all necessary fields are included.
 - Make sure the server status is showing as Running.

By following these steps, you can successfully configure the FlowMattic MCP Server in Warp and start utilizing its features.

---

# How to Set Up WooCommerce Abandoned Cart Recovery System in FlowMattic?

Source: https://support.flowmattic.com/kb/article/107/how-to-set-up-woocommerce-abandoned-cart-recovery-system-in-flowmattic

Setting up an automated abandoned cart recovery system can significantly boost your WooCommerce store's revenue. With FlowMattic's WooCommerce 2.0 integration, you can create powerful cart abandonment workflows that rival premium plugins costing $99+ annually.

## What is Cart Abandonment?

Cart abandonment occurs when customers add products to their shopping cart but leave your website without completing the purchase. Studies show that the average cart abandonment rate is around 70%, making recovery systems essential for e-commerce success.

## Prerequisites

Before setting up abandoned cart recovery, ensure you have:

- FlowMattic plugin installed and activated
- WooCommerce plugin installed and configured
- FlowMattic WooCommerce integration (version 2.0 or higher)
- An email service integrated with FlowMattic (Gmail, Mailgun, SendGrid, etc.)

## Accessing the Abandoned Cart Dashboard

FlowMattic provides a dedicated dashboard to monitor and manage abandoned carts:

1. Navigate to **WooCommerce > Abandoned Carts** in your WordPress admin
2. The dashboard displays key metrics including:
   - Total abandoned carts
   - Recovery rate percentage
   - Revenue recovered
   - Recent abandonment activity

![Abandoned Carts ‹ FlowMattic dashboard.png](/storage/kb-images/8280247942-inline.png)

## Viewing Abandoned Cart Details

From the dashboard, you can view detailed information about each abandoned cart:

1. Click on any abandoned cart entry to view details
2. The detail view shows:
   - Customer information
   - Cart contents with product images
   - Cart value and timestamps
   - Recovery attempts made
   - Cart recovery link

![Abandoned Cart details.png](/storage/kb-images/75fd9b7ae1-inline.png)

### Cart Details Include:
- **Customer Email**: Contact information for recovery
- **Cart Value**: Total amount of abandoned items
- **Time Since Abandonment**: How long the cart has been abandoned
- **Product List**: Items left in the cart with images and quantities
- **Recovery Status**: Whether recovery emails have been sent

## Creating an Abandoned Cart Recovery Workflow

Now let's create an automated workflow to recover abandoned carts:

### Step 1: Create New Workflow

1. Go to **FlowMattic > Workflows**
2. Click **Add New Workflow**
3. Name it "Abandoned Cart Recovery"
4. Set status to **Live**

### Step 2: Configure the Abandoned Cart Trigger

1. Click **Choose Trigger**
2. Select **WooCommerce**
3. Choose **New Cart Abandonment** event
4. The trigger will automatically detect when customers abandon their carts without any additional configuration needed

![Abandoned Carts - FlowMattic.png](/storage/kb-images/e0966fd7b0-inline.png)

#### Testing the Trigger
To test the trigger and capture response data for mapping in your workflow:

1. In your workflow, click the **Capture Response** button for the Cart Abandonment trigger
2. Navigate to **WooCommerce > Abandoned Carts** in your WordPress admin
3. Click the **Test Trigger** button in the abandoned cart admin page
4. This will instantly send test data to your workflow for response mapping
5. Return to your workflow to see the captured data and map the fields you need

![abandoned cart workflow.png](/storage/kb-images/66be5b551e-inline.png)

### Step 3: Add Delay Module

To give customers time to return naturally before sending recovery emails:

1. Click the **+** button to add a new step
2. Select **Delay** from the module options
3. Configure the delay duration (recommended: **1-2 Hours** for first recovery email)
4. This prevents sending emails too quickly and gives customers time to complete their purchase naturally

### Step 4: Configure Recovery Email Action

1. Add new action
2. Select **WooCommerce**
3. Choose **Send Abandoned Cart Email**
4. Configure email settings:

#### Email Configuration:
- **Email Subject**: Enter a compelling subject line (e.g., "Don't forget your cart!")
- **Cart ID**: Use `{cart_id}` from the abandoned cart trigger data
- **From Name**: Your store name (appears in recipient's inbox)
- **From Email**: Your store email address (e.g., noreply@yourstore.com)

#### Email Content Options:
FlowMattic provides three flexible options for email content:

**1. Use Custom Content**
- Write your own personalized email content
- Full control over messaging and design
- Perfect for brand-specific communication
- Use dynamic variables for personalization

**2. Use Default Template**
Choose from professionally designed templates:
- **Abandoned Cart**: Simple reminder email
- **Coupon Discount**: Includes discount code incentive
- **Last Chance**: Urgent final reminder

**3. Use FlowMattic Email Templates**
- Access FlowMattic's powerful email template builder
- Create beautiful, professional email designs with drag-and-drop interface
- Design once, use across all your workflows
- Built-in responsive design ensures emails look great on all devices
- Save and reuse templates for consistent branding
- Perfect for creating visually appealing cart recovery emails with your brand colors, fonts, and styling

#### Available Dynamic Variables:
Personalize your emails with these variables:
- `{customer_name}` - Customer's full name
- `{first_name}` - Customer's first name
- `{last_name}` - Customer's last name
- `{customer_email}` - Customer's email address
- `{cart_items}` - HTML formatted list of abandoned products
- `{cart_total}` - Formatted total cart value
- `{cart_url}` - Direct link to view cart
- `{recovery_url}` - One-click recovery link

![abandoned-cart-send-email-configuration.png](/storage/kb-images/c9508a0b44-inline.png)

### Step 5: Test Your Workflow

1. Set workflow to **Live** mode
2. Add items to cart on your store (using a test email)
3. Leave checkout without completing
4. Wait for the delay period - **Note**: The default time to check abandoned cart status is 30 minutes. You can change this setting from the **WooCommerce > Abandoned Carts** admin page
5. Check if the recovery email is sent

## Sample Recovery Email Template

Here's an effective email template you can use (HTML format for email content):

```
Subject: Don't miss out on your items!

Hi {customer_name},

You left some great items in your cart. Complete your purchase now before they're gone!

Your Cart:
{cart_items}

Total: {cart_total}

<a href="{recovery_url}" style="background: #0073aa; color: white; padding: 12px 24px; text-decoration: none; border-radius: 4px; display: inline-block;">Complete My Purchase</a>

This cart is saved for 48 hours.

Best regards,
The {site_name} Team
```

![abandoned-cart-email.png](/storage/kb-images/90afd8c5e7-inline.png)


## Monitoring Recovery Performance

Track your abandoned cart recovery success:

### Dashboard Metrics
- **Total Carts Abandoned**: Number of detected abandonments
- **Recovery Rate**: Percentage of carts recovered
- **Revenue Recovered**: Total sales from recovered carts
- **Email Performance**: Open rates and click-through rates

### Task History
Monitor individual workflow executions:

1. Go to **FlowMattic > Task History**
2. Filter by your abandoned cart workflow
3. View success/failure rates
4. Check email delivery status

## Best Practices for Success

### Email Timing
- **First Email**: 1-2 hours after abandonment
- **Second Email**: 24 hours later (optional)
- **Final Email**: 72 hours with incentive (optional)

### Email Content Tips
1. Keep subject lines short and compelling
2. Include product images in the email
3. Add a clear call-to-action button
4. Create urgency without being pushy
5. Personalize with customer's name

### Optimization Strategies
- Test different email subject lines
- Try various delay timings
- Experiment with discount offers
- Monitor and adjust based on results

## Common Troubleshooting

### Emails Not Sending
- Verify email service connection
- Check workflow is set to "Live"
- Confirm trigger conditions are met

### Low Recovery Rates
- Improve email subject lines
- Add product images to emails
- Consider offering small discounts
- Optimize email timing

### Duplicate Emails
- Ensure only one abandoned cart workflow is active
- Check for multiple triggers on same event

## Advanced Features

### Multiple Email Sequence
Create several workflows with different delays:
- Immediate reminder (1 hour)
- Follow-up with discount (24 hours)
- Final attempt with larger discount (72 hours)

### Segmentation
Create different workflows for:
- High-value carts ($100+)
- Regular carts ($25-$99)
- Low-value carts (under $25)

## Getting Started

1. **Enable the feature**: Ensure WooCommerce 2.0 integration is active
2. **Create your workflow**: Follow the steps above
3. **Test thoroughly**: Use test mode before going live
4. **Monitor results**: Check dashboard regularly for performance
5. **Optimize**: Adjust based on recovery rates and feedback

Your abandoned cart recovery system will start working immediately, helping you recover lost sales and increase your store's revenue automatically.

---

# How to Set Up Your AI Assistant Chatbot in FlowMattic

Source: https://support.flowmattic.com/kb/article/138/ai-assistant-setup-guide

The AI Assistant in FlowMattic lets you add an intelligent chatbot to your WordPress site in minutes. This guide walks you through every setting in the **Setup** tab so you can get your chatbot running quickly.

## Prerequisites

Before you begin, make sure you have:

- FlowMattic 6.1.0 or later installed and activated
- An OpenAI account with an API key
- Your OpenAI API key added as a Connect in FlowMattic (go to **FlowMattic > Connects > Add New** and select OpenAI)

## Creating a New AI Assistant

1. Go to **FlowMattic > AI Assistants** in your WordPress dashboard
2. Click **Add New** to create a new assistant
3. You will get a popup to create your Assistant. Just fill the required fields and click "Create Assistant"
4. Your assistant will be created and you will see it in your Assistants page now. Just click the newly created assistant name to edit.
5. You'll land on the **Setup** tab — this is where all the core configuration happens

![AI Assistants - create assistant.png](/storage/kb-images/993b338ab2-inline.png)

## Step 1: Set the Identity

### Chatbot Name

Enter a name for your chatbot. This is the name your visitors will see in the chat header.

**Example:** "Support Bot", "Sales Assistant", or your brand name like "ACME Helper"

### Description

Add a short description (up to 512 characters) for internal reference. This helps you identify the chatbot's purpose when you have multiple assistants.

**Example:** "Customer support chatbot for the help center"

## Step 2: Connect Your AI Model

### OpenAI Connect

Select the OpenAI Connect account you created earlier. If you haven't added one yet, click the link to go to **Manage Connects** and set it up first.

### AI Model

Choose which OpenAI model powers your chatbot. The dropdown automatically fetches all available models from your OpenAI account, so you'll always see the latest options. Generally, larger models give better quality responses but cost more per message — pick the one that fits your quality and budget needs.

### Vector Store ID

The Vector Store is where your chatbot's knowledge base lives. When you add content (documents, web pages, posts), it gets stored in a Vector Store on OpenAI so the chatbot can search and reference it.

You have two options:

**Option A: Paste an existing Vector Store ID**

If you already have a Vector Store on OpenAI, paste its ID directly in the field (it looks like `vs_xxxxxxxxxxxxxxxxx`). You can find or create Vector Stores from the [OpenAI Dashboard — Storage](https://platform.openai.com/storage/vector_stores).

![openai-create-vector-store-FlowMattic.png](/storage/kb-images/47fb3d031c-inline.png)

**Option B: Create one from FlowMattic**

If the Vector Store ID field is empty, you'll see a **Create New** button next to it. Clicking it opens a dialog where you enter a **Vector Store Name** (e.g., "Customer Support - FlowMattic"). It uses the OpenAI Connect you already selected in the Setup tab.

Click **Create Vector Store** and FlowMattic will create the vector store on OpenAI and populate the ID automatically.

> **Note:** Make sure you've selected an OpenAI Connect in the Setup tab before creating a vector store.

Once a Vector Store is connected, you'll see a green **Connected** badge next to the field.

![AI Assistants- vector store - FlowMattic.png](/storage/kb-images/ff6c834772-inline.png)

## Step 3: Configure Behavior

### Instructions

This is the system prompt — the most important setting for your chatbot's personality and behavior. Tell the AI who it is, what it should do, and what it should avoid.

**Example Instructions:**

```
You are a helpful customer support assistant for ACME Inc. 
You help customers with product questions, order tracking, and returns.
Always be polite and professional.
If you don't know the answer, suggest the customer contact support@acme.com.
Do not discuss competitors or make up information.
```

You can use up to 32,768 characters — be as detailed as you need.

### Welcome Message

The first message visitors see when they open the chatbot. Make it friendly and actionable.

**Example:** "Hi there! I'm here to help with any questions about our products or your orders. How can I assist you today?"

### Input Placeholder

The placeholder text shown inside the chat input box before the user types anything.

**Example:** "Type your question here..." or "Ask me anything about our products"

## Step 4: Session Settings

### Load User Session Chats

When set to **Yes** (default), returning visitors will see their previous chat messages when they reopen the chatbot. Set to **No** if you want every visit to start with a fresh conversation.

## Step 5: Save and Embed

1. Click **Save** to save your chatbot configuration
2. After saving, you'll get a **shortcode** that you can place on any page, post, or widget area
3. You can also use the **full-page** mode or **widget** mode (configured in the Themes tab)

## What's Next?

Your chatbot is now configured and ready to answer questions. To make it smarter, head to the **Content** tab to add your knowledge base — documents, web pages, database tables, and WordPress posts.

- [Managing Content Sources for Your AI Assistant Chatbot](/kb/ai-assistant-content-sources) — Add knowledge sources
- [Customize your chatbot's appearance](/kb/customize-your-chatbots-appearance) — change colors, position, and style
- [Collect leads and schedule meetings from your chatbot](/kb/collect-leads-and-schedule-meetings-from-your-chatbot) — capture contact details and let visitors book a slot

---

# How to Successfully Complete an Action Step

Source: https://support.flowmattic.com/kb/article/45/how-to-successfully-complete-an-action-step

To complete an action step effectively, follow these detailed steps:

1. **Configure Settings**: Begin by configuring the settings of the action step. Ensure all necessary parameters are set correctly to match your requirements.

2. **Perform a Test Action**: Navigate to the "Test" tab within the settings popup. Click on the "Test Action" button to execute a test of the configured action. This step is crucial to verify that the action performs as expected.

3. **Save and Close**: Once you have confirmed that the action works correctly, finalize the process by clicking the "Save and Close" button in the settings popup. This will save your configurations and mark the action step as complete.

4. **Utilize Response Data**: After successfully completing the action step, you can utilize the response data generated. This data can be used in subsequent action steps, allowing you to map it with relevant fields and continue your workflow efficiently.

**Tips:**
- Double-check all configurations before performing the test action to avoid errors.
- If the test action fails, review the settings and try again.
- Document any specific configurations or settings that are crucial for future reference.

By following these steps, you can ensure that your action steps are completed successfully and efficiently, facilitating a smooth workflow process.

---

# How to Use AI Agents in FlowMattic to Categorize and Reply to Support Tickets

Source: https://support.flowmattic.com/kb/article/140/ai-agent-support-ticket-triage

Support teams spend hours triaging tickets — reading each request, tagging it, and routing it to the right person before anyone can even reply. With FlowMattic's **AI Agent** you can hand that work to an automated workflow that reads every incoming ticket, classifies it, and drafts a context-aware response in seconds.

This guide walks you through building that workflow from scratch.

## What you'll build

A single FlowMattic workflow that:

1. **Receives** a new support ticket from your helpdesk or contact form.
2. **Categorizes** it with an AI Agent (for example *Billing*, *Technical*, *Feature request*, or *General*) and assigns a priority.
3. **Routes** the ticket down the right path based on that category.
4. **Drafts a reply** with a second AI Agent that matches the ticket's intent and tone.
5. **Sends** the reply back to the customer — or saves it for an agent to approve.

## Before you start

Make sure you have:

- **FlowMattic installed and activated** on your WordPress site.
- An **AI provider Connect** already set up. FlowMattic supports OpenAI, Anthropic (Claude), Google Gemini, and more. Go to *FlowMattic → Connects* and add your provider's API key if you haven't done so yet.
- A **source of tickets** that can send data out — a helpdesk that supports webhooks, a WordPress contact form, or an inbox you can forward.

## Step 1 — Create a new workflow

1. Open **FlowMattic** from your WordPress admin menu.
2. Click **Create Workflow**.
3. Give it a clear name, such as `AI Support Ticket Triage`, and confirm.

You'll land on the visual workflow editor with an empty **Trigger** step.

## Step 2 — Set up the trigger

The trigger is the event that starts the workflow — a new support ticket arriving.

1. Click the **Trigger** step.
2. Choose the **Webhook** application.
3. Select the **Catch Webhook** event.
4. FlowMattic generates a unique **Webhook URL**. Copy it.
5. Paste that URL into your helpdesk's outgoing webhook or "new ticket" notification settings so every new ticket is sent to FlowMattic.
6. Send one test ticket, then click **Capture Webhook Response** so FlowMattic learns the data structure (subject, message, customer name, email, and so on).

![Webhook trigger configured with the generated webhook URL and the option to capture a webhook response](https://assets.infidesk.support/kb/inline/2026/07/AkU6pCnPgnQhNUbkzqPzNpHwYZUfQ58XK2mKOgp7.png)

> **Tip:** If your tickets arrive by email, use the **Incoming Email / Email Parser** trigger instead. If you collect tickets through a WordPress form plugin (WPForms, Fluent Forms, Gravity Forms), pick that plugin's "New Submission" trigger.

## Step 3 — Categorize the ticket with an AI Agent

Now add the first AI Agent step to classify the ticket.

1. Click the **+** below the trigger to add a step.
2. Choose the **AI Agent** application.
3. Select your **AI provider Connect** and a **model**.
4. In the **System Instructions**, describe the job:

```
You are a support ticket classifier for FlowMattic.
Read the ticket and return:
- category: one of [Billing, Technical, Feature Request, General]
- priority: one of [Low, Normal, High, Urgent]
- summary: a one-sentence summary of the customer's issue.
Respond only with the requested fields.
```

5. In the **User Message**, map the ticket fields from the trigger using the field picker:

```
Subject: {{trigger.subject}}
Message: {{trigger.message}}
Customer: {{trigger.customer_name}}
```

6. If your model supports it, set the **Response Format** to **JSON** so the output is structured and easy to reuse in later steps.
7. **Save** the step and run a test. Confirm the agent returns a clean category, priority, and summary.

![system prompt ](https://assets.infidesk.support/kb/inline/2026/07/s6DvuxAMNO4c1dS0IiWuxSs1EomvHXu6OnnuGq4i.png)

## Step 4 — Route by category (optional but recommended)

To handle each category differently, add a **Router / Paths** step:

1. Add a step and choose **Router / Paths**.
2. Create one path per category. For each path, set a condition such as:
   - **Billing path:** `AI Agent → category` *equals* `Billing`
   - **Technical path:** `AI Agent → category` *equals* `Technical`
   - …and so on for the remaining categories.
3. Each path can have its own reply tone, escalation rule, or assignee. For example, send **Urgent** tickets straight to a Slack channel for a human.

![Router step configured with separate paths for Billing, Technical, Feature Request, and General support tickets.](https://assets.infidesk.support/kb/inline/2026/07/ha1lGwqvjgSuCoxJqT7M39dT9NnoctVwC0fFfoDZ.png)

If you'd rather keep things simple, skip the Router — a single reply step (Step 5) works for every category.

## Step 5 — Draft the reply with a second AI Agent

Inside each path — or directly after Step 3 if you skipped routing — add another **AI Agent** step to write the response.

1. Add a step → **AI Agent** → select your Connect and model.
2. Set the **System Instructions**:

```
You are a friendly, concise support agent for FlowMattic.
Write a reply that:
- Greets the customer by name.
- Directly addresses the issue described in the summary.
- Gives clear, accurate next steps.
- Stays polite and professional, and never invents features.
If you are unsure, ask one clarifying question instead of guessing.
```

3. In the **User Message**, pass the category and ticket context from the earlier steps:

```
Category: {{categorize.category}}
Priority: {{categorize.priority}}
Customer name: {{trigger.customer_name}}
Issue summary: {{categorize.summary}}
Original message: {{trigger.message}}
```

4. **Use tools (advanced):** FlowMattic AI Agents can call other actions as **tools**. Attach a knowledge-base search or order-lookup action so the agent grounds its reply in real data instead of guessing.
5. Save the step and test it to review the drafted reply.

![AI Agent configured to generate a customer support reply using the ticket category, priority, summary, and original message](https://assets.infidesk.support/kb/inline/2026/07/iWzBWT76TTfOVE6ZXLBaD7rpictL7Q7CB8RPqV9f.png)

## Step 6 — Send the reply

Add a final action step to deliver the AI-drafted reply:

- **Post it back to your helpdesk** using that helpdesk's "Add Reply" or "Update Ticket" action, or its API through the **Webhooks** action.
- **Email the customer** with the **Email** action or your SMTP/Gmail integration.
- **Keep a human in the loop:** instead of sending automatically, save the reply as an internal note or send it to Slack for approval first. This is the safest setup while you build trust in the workflow.

![Email action configured to send the AI-generated support reply to the customer's email address](https://assets.infidesk.support/kb/inline/2026/07/wsarqPyQJ8MrK2mLtW4HyZyglC0jyUuVv7Mw8Yre.png)

Map the AI Agent's reply into the message body, and the customer's email or ticket ID from the trigger.

## Step 7 — Test and activate

1. Use **Test Workflow** to run the whole flow end to end with a sample ticket.
2. Check each step's output — the category, the routing, and the final reply.
3. When you're satisfied, toggle the workflow to **Active**.

![Workflow execution history showing successful processing of a support ticket from webhook trigger through AI classification and reply generation](https://assets.infidesk.support/kb/inline/2026/07/LqA6uvLFPQCnCS92IViyp15vfFDomGYzKEwm3mBW.png)

Every new ticket will now be categorized and answered automatically.

## Best practices

- **Start in review mode.** Save AI replies as drafts for the first week and let agents approve them before they go out.
- **Be specific in prompts.** The clearer your categories and tone instructions, the more consistent the results.
- **Use JSON output** for the categorize step so later conditions stay reliable.
- **Add a fallback path** for tickets the agent marks as `General` or low-confidence, and route those to a human.
- **Monitor the Workflow History** in FlowMattic to spot mis-categorized tickets and refine your prompts over time.

## Conclusion

With two AI Agent steps and a webhook trigger, FlowMattic can triage your entire support inbox — categorizing tickets and drafting accurate replies around the clock. Start with a human approving each reply, tune your prompts from real results, then let the workflow run on its own once you trust it.

---

# How to use Box with FlowMattic

Source: https://support.flowmattic.com/kb/article/22/how-to-use-box-with-flowmattic

Box empowers your teams by making it easy to work with people inside and outside your organization, protect your valuable content, and connect all your apps.

Here’s an in-depth tutorial about how you can set up the Box workflow in FlowMattic and get the most out of your apps by automating the process.

## **Authenticating Box account in FlowMattic**

You will learn how to connect your Box account using the FlowMattic connects. Once you connect your account in connects, you can use it in any number of workflows, or even in the API module as well, that allows you to connect with the APIs that are not yet covered in the integration.

### 1\. Go to FlowMattic &gt; Connects

From the FlowMattic admin menu, click on the Connects.

![](/storage/kb-images/1d99cf3f6a-Screenshot-2024-12-05-114546-1024x550.png)

### 2\. Click on Connect Integration

While you’re on the Connects admin screen, click on the Connect Integration button. It will open a popup and display all the apps available to be connected.

![](/storage/kb-images/9673e5bcef-Screenshot-2024-12-05-114738-1024x477.png)

### 3\. Click on Box

Choose the Box integration for authentication.

![](/storage/kb-images/cfdc667c07-Screenshot-2024-12-05-114832-1024x484.png)

### 4\. Click on Authenticate & Save Connect

Once the Box Connect app popup opens, it will ask you to enter a Connect Name. If you’re going to connect multiple Box accounts, name each connection for better understanding. Then, click on the Authenticate and Save Connect button. Your connection will be saved first, and then you will be redirected to the authentication at Box.

![](/storage/kb-images/416e38d358-Screenshot-2024-12-05-115044-1024x491.png)

### 5\. Click on Grant access to Box

You will be redirected to the Box authentication screen if you're logged in. You just need to click on the "Grant access to Box" button and the authentication will be successful.

![](/storage/kb-images/a75a359b33-Screenshot-2024-12-05-115227-1024x560.png)

## **Configuring Box triggers**

You will learn how to configure the Box triggers.

### 1\. Create a new workflow

To get started with configuring triggers, create a new workflow from your FlowMattic dashboard.

![](/storage/kb-images/bcad742ba8-Screenshot-2024-12-05-115347-1024x485.png)

### 2\. Click on the Change button

Click on the change button. It will open up the window with all the available integrations.

![](/storage/kb-images/110d2e4aa4-Screenshot-2024-12-04-002952.png)

### 3\. Insert the Box Integration

Search for the Box integration. You will see the sorted list while you type in, and finally, the Box app will be displayed. Just click the app icon and it will be set as the action app.

![](/storage/kb-images/14238e087a-Screenshot-2024-12-04-003151-1024x255.png)

### 4\. Choose the trigger event

Box integration provides you with various triggers. Choose the one that you want to get the data in after this event is happened in your Box account.

![](/storage/kb-images/c1c61d1452-Screenshot-2024-12-04-003304.png)

### 5\. Choose New File Action

We will use the New File trigger for this example.

![](/storage/kb-images/5093c5bae5-Screenshot-2024-12-04-003348-1024x389.png)

### 6\. Click on Choose Connect

The next step is to set the Connect for authenticating the API connections. Click on the Choose Connect dropdown, it will display all your available connects.

![](/storage/kb-images/467f9a4c7e-Screenshot-2024-12-04-003903-1024x400.png)

### 7\. Choose the Box Connect

Search for the connect of your Box account, and choose it from the dropdown. It will be used to authenticate the API connections for this trigger.

![](/storage/kb-images/bb87c3868a-Screenshot-2024-12-04-003810-1024x450.png)

### 8\. Click on Choose folder to monitor

Box triggers require the entity to monitor. In this case, we need to provide the Folder to monitor for new files. As soon a new file is added to this folder, Box will send the data to your workflow.

![](/storage/kb-images/f0d7fe7ee5-Screenshot-2024-12-05-014759-1024x476.png)

### 9\. Choose your preferred folder

Once you click on the Choose Folder dropdown, you will get the list of folders. Choose the once you want to monitor for this workflow.

![](/storage/kb-images/f85ac0abe3-Screenshot-2024-12-05-015220-1024x380.png)

### 10\. Click on Connect to Box

The final step in configuring the trigger is to connect this workflow with your Box account. To do so, click on the "Connect to Box" button. It will register this workflow for the folder you choose to monitor.

![](/storage/kb-images/1c6760b872-Screenshot-2024-12-05-015528-1024x519.png)

## **Adding and Configuring Action Steps**

We will see how to add and configure the action steps for Box.

### 1\. Add new action step

Click on the + icon after the trigger step to add a new action step.

![](/storage/kb-images/7ab61360ae-Screenshot-2024-12-05-030528-1024x486.png)

### 2\. Click on Box to use the app

Type "Box" in the search field to find the Box application. Once it appears, simply click on it to select it for the action step.

![](/storage/kb-images/c2d9a8083b-Screenshot-2024-12-05-031143-1024x394.png)

### 3\. Choose an action event

The next step is to set the action event. The Box app provides different action events. Choose the one you want to perform in the action step and click the "Continue" button.

![](/storage/kb-images/3cbe801075-Screenshot-2024-12-05-031507-1024x502.png)

### 4\. Click on Choose Connect

The next step is to set the Connect for authenticating the API connections. Click on the Choose Connect dropdown, it will display all your available connects

![](/storage/kb-images/5b3be33107-Screenshot-2024-12-05-032645-1024x441.png)

### 5\. Choose the Box Connect

Search for the connect of your Box account, and choose it from the dropdown. It will be used to authenticate the API connections for this action step.

![](/storage/kb-images/41168172e6-Screenshot-2024-12-05-033015-1024x461.png)

### 6\. Text Action and Save & Close

After setting up the required options, click the "Test Action" button to perform a live test with the data you have entered. To confirm that the workflow is working, verify that the new post appears in your Nuelink collection. Then click "Save and Close."

![](/storage/kb-images/fc2e827bb1-Screenshot-2024-12-05-043334.png)

---

# How to use Connects?

Source: https://support.flowmattic.com/kb/article/4/how-to-use-connects

Here is a step-by-step guide on **"How to use Connects in FlowMattic"**, which allows users to connect and manage API access or integrations globally within their workflows.

### Step 1: Accessing the Connects Page

1. From the FlowMattic dashboard, click on the **"Connects"** option in the left-hand menu.

- This opens the **Connects** admin page, where existing connections (APIs and integrations) are listed.

### Step 2: Creating a New Connection

On the Connects page, you have two main options:

1. **Connect Integration**

3. **Connect New API**

* * *

#### Option 1: **Connect Integration**

1. Click on the **"Connect Integration"** button at the top right.

- This will open a popup with a list of available integrations, such as Google Sheets, HubSpot CRM, Facebook Lead Ads, and more.

1. Use the **search bar** to find the specific integration you're looking to connect.

3. Click on the desired integration.

- A new popup will appear, where you'll proceed with the required authentication (OAuth 2.0, for example). Follow the on-screen steps to complete authentication.

1. Once authentication is successful, the integration will be added to the Connects list, ready to be used in workflows.

* * *

#### Option 2: **Connect New API (Custom API Connection)**

1. Click on the **"Connect New API"** button (blue button) to create a new custom API connection.

3. A popup will open, prompting you to:

- **Enter Connect Name**: This name will help you identify the API you're connecting.

- **Choose Authentication Type**: Several options are available:
    - **Basic**: Username and password access via HTTP headers.
    
    - **API Key**: Single token for API request authorization.
    
    - **Bearer Token**: Token-based authentication using JWT.
    
    - **OAuth 2.0**: Protocol for secure token-based access.

1. After filling out the details, click **Save** to create the connection.

- The custom API will now appear in the Connects list under the "Source" category as **Custom**.

* * *

### Step 3: Managing Your Connects

1. On the **Connects** admin page, your existing integrations and custom API connections are listed with options to:

- **Edit** (pencil icon): Update connection details.

- **Settings** (gear icon): Configure advanced settings, if available.

- **Delete** (trash icon): Remove the connection.

1. Each entry displays key details like:

- **Auth Type**: OAuth 2.0, API Key, etc.

- **Source**: Integration or Custom.

- **Creation Date**: When the connection was added.

* * *

### Step 4: Using Connects in Workflows

1. Once you've successfully created a Connect (either an integration or custom API), you can use it in your workflows.

3. In the **Workflows** module:

- Choose to add a step with an **API Module** or select the appropriate **integration module** from the available options.

- Select the **Connect** from the dropdown list of available connections.

- Proceed with configuring the workflow step based on the API or integration you've connected.

* * *

### Conclusion

By following these steps, you can easily set up, manage, and use your API and integration connections globally within FlowMattic, making workflow automation smoother and more efficient.

---

# How to Use Deactivation Cleanup in FlowMattic

Source: https://support.flowmattic.com/kb/article/133/how-to-use-deactivation-cleanup-in-flowmattic

FlowMattic's Deactivation Cleanup feature lets you selectively delete plugin data before deactivating the plugin. This ensures a clean removal when you no longer need FlowMattic, while giving you full control over exactly what gets deleted.

---

## Overview

When you deactivate FlowMattic from the WordPress Plugins page, a cleanup dialog appears allowing you to choose which data to remove. You can:

- **Delete specific data** — Select exactly which items to remove.
- **Delete all data** — Remove everything with the "Select All" option.
- **Skip cleanup** — Deactivate without deleting anything (data is preserved for reactivation).
- **Cancel** — Stay on the page without deactivating.

> **Important:** Data deletion is irreversible. Once deleted, data cannot be recovered. Consider exporting your workflows before deleting if you might need them on another site.

---

## When Does the Cleanup Dialog Appear?

The cleanup dialog appears **only** when you click the **Deactivate** link for FlowMattic on the WordPress Plugins page (**Plugins > Installed Plugins**).

It does **not** appear:
- When updating the plugin
- When deactivating other plugins
- Automatically on any schedule

![Deactivation Cleanup Dialog.png](/storage/kb-images/ee429a498c-inline.png)

---

## Data Items You Can Delete

The cleanup dialog presents **8 categories** of data you can select for deletion:

### 1. Workflows

All your automation workflows and their configurations.

- Shows the total number of workflows (e.g., "5 workflows").
- Deleting this removes all workflow definitions, trigger configurations, and action steps.

### 2. Task History

Execution logs and task history records from all workflow runs.

- Shows the total number of task records.
- Deleting this removes all execution history, logs, and debug data.

### 3. Connections

API connections and authentication data (Gmail, Slack, OpenAI, etc.).

- Shows the total number of connections.
- Deleting this removes all stored API keys, OAuth tokens, and connection configurations.

### 4. Custom Tables

User-created database tables and their data.

- Shows the count of tables you've created using FlowMattic's database feature.
- Deleting this removes both the table schemas and the actual data stored in those tables.

### 5. Plugin Database Tables

FlowMattic's internal database tables (14 tables).

- These are the core tables FlowMattic uses to operate.
- Includes tables for workflows, tasks, connections, chatbot, variables, RSS feeds, IMAP accounts, data connections, email templates, MCP server, and more.

### 6. Plugin Settings & Options

All FlowMattic settings, license data, and configuration options.

- Shows the count of options stored in the WordPress database.
- Deleting this removes all plugin settings, license information, and stored preferences.

### 7. User Roles

FlowMattic-specific user roles and capabilities.

- Removes the `flowmattic_workflow_manager` custom role.
- Also removes FlowMattic-specific capabilities from the Administrator role (`manage_flowmattic`, `edit_flowmattic_workflows`, `delete_flowmattic_workflows`, `view_flowmattic_task_history`).

### 8. Cached Data

Temporary cached data and transients.

- Removes all FlowMattic transients from the WordPress database.
- This is safe to delete and has no permanent impact.

---

## How to Use Deactivation Cleanup

### Step 1: Open the Cleanup Dialog

1. Go to **Plugins > Installed Plugins** in your WordPress dashboard.
2. Find **FlowMattic** in the plugin list.
3. Click the **Deactivate** link.
4. The cleanup dialog appears.

### Step 2: Select Data to Delete

- **Check individual items** — Click the checkbox next to each data category you want to delete.
- **Select All** — Use the "Select All" checkbox at the top to select all 8 categories at once.

Each item shows a count badge indicating how much data will be affected (e.g., "5 workflows", "14 tables").

### Step 3: Choose an Action

| Button | What Happens |
|--------|-------------|
| **Cancel** | Dismisses the dialog. Nothing is deactivated or deleted. |
| **Skip & Deactivate** | Deactivates FlowMattic without deleting any data. All data is preserved. |
| **Delete Selected & Deactivate** | Deletes the selected items, then deactivates FlowMattic. |

> **Note:** The "Delete Selected & Deactivate" button is disabled until you select at least one item.

### Step 4: Confirm Deletion

After clicking "Delete Selected & Deactivate", a confirmation prompt appears:

> **"Are you sure you want to delete the selected data? This cannot be undone."**

Click **OK** to proceed or **Cancel** to go back.


![confirm-deletion](/storage/kb-images/2a0435d9ba-inline.png)


### Step 5: Cleanup Completes

A progress indicator shows while data is being deleted. Once complete:

- A success message appears: **"Data deleted successfully!"**
- FlowMattic is automatically deactivated.
- You are returned to the Plugins page.


---

## What Happens If You Skip Cleanup?

If you click **Skip & Deactivate**:

- FlowMattic is deactivated normally.
- **All data is preserved** in the database (workflows, connections, history, settings, etc.).
- If you reactivate FlowMattic later, all your data will still be there.
- This is the safe option if you're temporarily deactivating or troubleshooting.

---

## What Is NOT Deleted

Regardless of your cleanup selections, the following are **never affected**:

- WordPress core database and settings
- Other plugin data
- WordPress user accounts (except the FlowMattic custom role)
- Posts, pages, and custom post types
- Theme settings and configurations
- FlowMattic plugin files (these are removed only if you delete the plugin from WordPress)

---

## Recommended Cleanup Scenarios

### Temporary Deactivation (Troubleshooting)

If you're deactivating FlowMattic temporarily to troubleshoot an issue:

- Click **Skip & Deactivate**.
- All data is preserved.
- Reactivate when ready — everything will be intact.

### Permanent Removal

If you're permanently removing FlowMattic and want a clean database:

1. Check **Select All** to select all data categories.
2. Click **Delete Selected & Deactivate**.
3. Confirm the deletion.
4. After deactivation, delete the plugin from the Plugins page.

### Partial Cleanup

If you want to keep some data but remove others (e.g., keep workflows but delete task history):

1. Select only the items you want to delete.
2. Click **Delete Selected & Deactivate**.
3. Selected items are deleted; unselected items are preserved.

---

## Troubleshooting

### Cleanup dialog doesn't appear

- Ensure you have **Administrator** access (the cleanup feature requires `manage_options` capability).
- Check that JavaScript is enabled in your browser.
- Disable browser extensions that may block JavaScript dialogs.

### Deletion fails with an error

- An error message will appear with details.
- The dialog returns to the selection state so you can retry.
- Check your server's PHP error logs for more details.
- Ensure your database user has DROP and DELETE permissions.

### Data remains after cleanup

- If you notice FlowMattic data still in your database after cleanup, it may be because:
  - You didn't select all categories for deletion.
  - A database permission issue prevented some deletions.
  - Cached data may still exist temporarily (WordPress transients expire on their own).

---

## Summary

| Feature | Details |
|---------|---------|
| **Access** | Plugins > Installed Plugins > FlowMattic > Deactivate |
| **When It Appears** | Only when deactivating FlowMattic |
| **Data Categories** | 8 (Workflows, Task History, Connections, Custom Tables, Plugin Tables, Settings, User Roles, Cached Data) |
| **Selection** | Individual items or Select All |
| **Skip Option** | Yes — deactivate without deleting anything |
| **Reversible** | No — deleted data cannot be recovered |
| **Permission Required** | WordPress Administrator |
| **Confirmation** | Yes — double confirmation before deletion |

---

# How to Use FlowMattic Patcher to Install Patches

Source: https://support.flowmattic.com/kb/article/132/how-to-use-flowmattic-patcher-to-install-patches

FlowMattic Patcher allows you to apply incremental updates and bug fixes between major plugin releases. Patches are small, focused updates that contain only the changed files — so you get fixes faster without waiting for a full release.

---

## What Are Patches?

Patches are small updates delivered directly from the FlowMattic update server. They can include:

- **Security fixes** — Critical vulnerability patches
- **Hotfixes** — Urgent bug fixes
- **Bug fixes** — Regular bug corrections
- **Improvements** — Feature enhancements
- **New features** — New functionality additions
- **Performance** — Speed and efficiency improvements
- **Compatibility** — Third-party compatibility fixes

Patches do not affect your workflows, connections, settings, or any other data. They only update plugin files.

---

## Accessing the Patcher

1. In your WordPress dashboard, go to **FlowMattic > Patcher**.
2. The Patcher page automatically checks for available patches for your current FlowMattic version.

![Patcher - FlowMattic 6.0.png](/storage/kb-images/f988f41abd-inline.png)

---

## Understanding the Interface

### Patch List

The Patcher displays all available patches in a table with the following columns:

| Column | Description |
|--------|-------------|
| **Patch #** | Unique patch number and version (e.g., "#1 v6.0") |
| **Title** | Brief name describing the patch |
| **Description** | What the patch fixes or improves |
| **Type** | Color-coded status badge indicating the patch category |
| **Action** | Apply button, applied status, or dependency message |

### Patch Type Badges

Each patch is categorized with a color-coded badge:

| Badge | Color | Meaning |
|-------|-------|---------|
| **Security** | Red | Critical security fix — apply immediately |
| **Hotfix** | Orange | Urgent bug fix |
| **Bugfix** | Yellow | Regular bug fix |
| **Improvement** | Blue | Enhancement to existing features |
| **Feature** | Purple | New functionality |
| **Performance** | Green | Speed or efficiency improvement |
| **Compatibility** | Gray | Third-party compatibility fix |

### Action Buttons

| Button | Meaning |
|--------|---------|
| **Apply Patch** (blue) | This patch is ready to be applied. Click to install it. |
| **Applied** (gray) | This patch has already been applied successfully. |
| **"Apply patch #X first"** | This patch requires a previous patch to be applied first. |

---

## Applying Patches

### Important: Sequential Order

Patches must be applied in order. You cannot skip ahead — each patch may depend on changes from previous patches. The Patcher enforces this automatically by only enabling the next unapplied patch.

### Method 1: Apply from Dashboard (Recommended)

**Apply patches one at a time:**

1. Navigate to **FlowMattic > Patcher**.
2. Review the first available patch (title, description, type).
3. Click the **Apply Patch** button.
4. Wait for the patch to download and install.
5. The button changes to **Applied** with a checkmark.
6. The next patch becomes available (if any).
7. Repeat until all desired patches are applied.


**Apply all patches at once:**

1. Navigate to **FlowMattic > Patcher**.
2. Click the **Apply All Patches** button at the top of the page.
3. Patches are applied sequentially in order.
4. Each patch shows as "Applied" as it completes.
5. A success message appears when all patches are applied.


### Method 2: Manual Installation via FTP

If the dashboard method doesn't work (e.g., server permission issues), you can apply patches manually:

1. Click the **download icon** next to the patch to download the ZIP file.
2. Extract the ZIP file on your computer.
3. Inside the extracted folder, locate the `flowmattic-patch` directory (or the patch files directly).
4. Connect to your server using an FTP/SFTP client (e.g., FileZilla, Cyberduck).
5. Navigate to `/wp-content/plugins/flowmattic/`.
6. Upload the extracted patch files to the plugin directory.
7. When prompted, choose **Overwrite** to replace existing files.
8. Verify the upload is complete.


> **Note:** Patches applied manually via FTP are not tracked in the Patcher dashboard. The fixes will be active, but the dashboard may still show the patch as unapplied.

---

## When No Patches Are Available

If no patches are available for your version, you'll see:

> **All Caught Up!** No patches are available for this version of FlowMattic.

This means your FlowMattic installation is fully up to date for the current version.

![Patcher - no patches.png](/storage/kb-images/66870b1bf7-inline.png)

---

## Patches and Plugin Updates

- **Patches are version-specific** — they only apply to the FlowMattic version you're currently running.
- **Major updates include all patches** — when you update to a new FlowMattic version, all previous patches are already included.
- **Patch tracking resets after updates** — after a major update, the applied patches list resets since they're bundled in the new version.

---

## Troubleshooting

### Patch fails to apply

**Common causes:**
- **File permissions** — Your web server needs write access to `/wp-content/plugins/flowmattic/`. Contact your hosting provider to verify permissions.
- **Network issues** — Your server must be able to reach `updates.flowmattic.com`. Check if your firewall or security plugin is blocking outbound requests.
- **Disk space** — Ensure your server has sufficient disk space for the patch download and extraction.

**Solutions:**
1. Click the patch button again to retry.
2. Temporarily disable caching plugins.
3. Use the manual FTP method as a fallback.
4. Contact FlowMattic support if the issue persists.

### Patcher page shows an error

If the Patcher page shows an error loading patches:
1. Click the **Retry** button to fetch patches again.
2. Verify your internet connection is working.
3. Check if `updates.flowmattic.com` is accessible from your server.

### Patches not showing after manual FTP install

Patches applied via FTP are not tracked by the Patcher. The fixes are active even if the dashboard still shows them as unapplied. You can safely ignore the status for manually applied patches.

---

## Best Practices

- **Back up before patching** — While patches are designed to be safe, it's good practice to back up your site before applying updates.
- **Apply security patches immediately** — Red "Security" badges indicate critical fixes that should be applied as soon as possible.
- **Don't skip patches** — Even if a patch description doesn't seem relevant, it may contain changes that later patches depend on.
- **Check after applying** — After applying patches, verify your workflows are running correctly.
- **Use the dashboard method** — The dashboard method is preferred because it tracks which patches have been applied.

---

## Summary

| Feature | Details |
|---------|---------|
| **Access** | FlowMattic > Patcher |
| **Application Methods** | Dashboard (recommended) or Manual FTP |
| **Patch Order** | Sequential — must be applied in order |
| **Apply All** | One-click to apply all pending patches |
| **Rollback** | Not available — back up before patching |
| **Plugin Updates** | All patches included in major updates |
| **Tracking** | Dashboard method only (FTP not tracked) |
| **Permission Required** | WordPress Administrator |

---

# How to Use Fusioo with FlowMattic?

Source: https://support.flowmattic.com/kb/article/24/how-to-use-fusioo-with-flowmattic

Fusioo helps growing businesses get organized. Create your custom online database and manage everything in one place. Use FlowMattic to automate the database record insertion operations, sit back and relax!

## Creating Connect for Fusioo Integration

### 1\. Go to FlowMattic &gt; Connects

From the FlowMattic admin menu, click on the Connects.

![](/storage/kb-images/dd130b6d29-Screenshot-2024-12-05-113602-1024x496.png)

### 2\. Click on Connect Integration

While you’re on the Connects admin screen, click on the Connect Integration button. It will open a popup and display all the apps available to be connected.

![](/storage/kb-images/87af337cfa-Screenshot-2024-12-05-113727-1024x482.png)

### 3\. Click on Fusioo

Click on the Fusioo integration to connect and store your authentication details.

![](/storage/kb-images/3dc87f6a2e-Screenshot-2024-12-05-113903-1024x488.png)

### 4\. Give a suitable name and paste the Access Token

To get your Access token, follow these steps -

- Go to the Integrations page on your workspace - [https://app.fusioo.com/integrations](https://app.fusioo.com/integrations)

- Switch to the tab "API Settings"

- Create a new custom application by clicking on the "Add an Application" button.

- Set the app to be private by checking the box.

- Once an application is created, refresh the page, switch to the "API Settings" tab, and click on the link where it says click here to create access token - [https://share.infiwebs.net/9Zuy8j8j](https://share.infiwebs.net/9Zuy8j8j)

- Your access token will be generated. Each time you click on the link, it will generate a new access token. Copy the generated access token and paste it in the Bearer Token field shown in the screenshot here:

![](/storage/kb-images/edc0d2fe76-Screenshot-2024-12-05-114040-1024x481.png)

### 5\. Click on Save Connect

Once you paste the access token, hit the "Save Connect" button, and a new connect will be created for you to use in the Fusioo integration or an API module if you want to use any additional APIs that are not yet covered by the integration.

![](/storage/kb-images/647615cadd-Screenshot-2024-12-05-114147-1024x480.png)

## Creating workflow with Fusioo integration

### 6\. From the Workflows Screen, Click on New Workflow

In order to create a new workflow, click on the New Workflow button at the top on any admin screen.

![](/storage/kb-images/23054228f5-Screenshot-2024-12-05-025810-1024x359.png)

### 7\. Configure the trigger to get data

Setup your trigger app first to get the data in your workflow. Eg. use webhook to receive data to trigger the workflow.

![](/storage/kb-images/b42874cf5b-Screenshot-2024-12-05-034158-1024x448.png)

### 8\. Setup the Fusioo Action

The next step is to set up the Fusioo action. Click on the **+** icon after the trigger step to add a new action step. This will display a list of available action apps for you to choose from.

![](/storage/kb-images/9aacd7853f-Screenshot-2024-12-05-035042-1024x439.png)

### 9\. Choose Fusioo Integration

Type in the search field to locate the Fusioo app and click it to set it up. This will set the app for this action step as Fusioo.

![](/storage/kb-images/2ccd1c4a9d-Screenshot-2024-12-05-035225-1024x454.png)

### 10\. Choose the Connect

First thing we need to do is to choose the appropriate connect account we used to store the Fusioo access token. Click on the Choose Connect dropdown and search for that connect account.

![](/storage/kb-images/f0a4cc01cd-Screenshot-2024-12-05-035927-1024x504.png)

### 11\. Selecting Fusioo App

Once you choose the connect account, FlowMattic will fetch the list of apps in your account using the Fusioo API. It will be listed in the dropdown. If for some reason, the app list is not auto populated, you can always sync it by clicking on the Sync button next to the dropdown.

![](/storage/kb-images/0f36dec83c-Screenshot-2024-12-05-040134.png)

### 12\. Choose the App

Once the list of available apps is populated, you need to select the app you want to use for this action step. For different apps, you need to setup different action steps.

![](/storage/kb-images/7c63aff7cf-Screenshot-2024-12-05-040319-1024x398.png)

### 13\. Map data for the fields

Once you choose the app, FlowMattic will fetch and display all the fields in your app database in Fusioo. Map the fields with the appropriate data you want to push to your Fusioo database. You can always change the mapping as per your requirements.

![](/storage/kb-images/a87fd156e8-Screenshot-2024-12-05-041338.png)

### 14\. Text Action and Save & Close

After setting up the required options, click the "Test Action" button to perform a live test with the data you have entered. To confirm that the workflow is working, verify that the new post appears in your Nuelink collection. Then click "Save and Close."

![](/storage/kb-images/53b8b48e5d-Screenshot-2024-12-05-043139.png)

---

# How to Use Nuelink with FlowMattic?

Source: https://support.flowmattic.com/kb/article/18/how-to-use-nuelink-with-flowmattic

Nuelink helps you plan, automate, and manage your social media and saves you time to focus on your business while your social media runs itself. Connect hundreds of applications and add quality content to your Nuelink collections using Nuelink with FlowMattic.

Here's an in-depth tutorial about how you can set up the Nuelink workflow in FlowMattic and get the most out of your apps by automating the process.

### 1\. Go to FlowMattic &gt; Connects

From the FlowMattic admin menu, click on the Connects.

![](/storage/kb-images/1d99cf3f6a-Screenshot-2024-12-05-114546-1024x550.png)

### 2\. Click on Connect Integration

While you're on the Connects admin screen, click on the Connect Integration button. It will open a popup and display all the apps available to be connected.

![](/storage/kb-images/9673e5bcef-Screenshot-2024-12-05-114738-1024x477.png)

### 3\. Click on Nuelink

Choose the Nuelink integration for authentication.

![](/storage/kb-images/3ae09ecc74-Screenshot-2024-12-05-115659-1024x486.png)

### 4\. Click on Authenticate & Save Connect

Once the Nuelink Connect app popup opens, it will ask you to enter a Connect Name. If you're going to connect multiple Nuelink accounts, name each connection for better understanding. Then, click on the Authenticate and Save Connect button. Your connection will be saved first, and then you will be redirected to the authentication at Nuelink.

![](/storage/kb-images/af91700afd-Screenshot-2024-12-05-115808-1024x483.png)

### 5\. Click on Select a collection

Choose the collection you want to add posts to, and click on the Give Access button below. Your selected collection name will be appended to the button.

![](/storage/kb-images/646eed2529-Screenshot-2024-12-05-120039.png)

### 6\. Click on Give Access to General

Considering you selected the Collection named "General", the button is now renamed to "Give Access to General". Just click on that button, and you will be redirected back to your site.

![](/storage/kb-images/225b780a3d-Screenshot-2024-12-05-120102.png)

* * *

## Working with FlowMattic Workflow Editor

### 1\. Create a new workflow for Nuelink

Let's assume you want to get new quotes from ChatGPT every morning at 9:00 and add them to the Nuelink collection, this workflow will help. We used the trigger as a Schedule module and have set the time to morning 9:00

![](/storage/kb-images/547c74a638-Screenshot-2024-12-03-173255-1024x462.png)

### 2\. Add a new action for Nuelink

Click on the + button to add a new action step. You will be presented with a nice highlighted action step that allows you to choose your application you want to perform action on.

![](/storage/kb-images/9331d03892-Screenshot-2024-12-03-173455-1024x460.png)

### 3\. Insert the Nuelink Integration

Click on the Action step and Search for the Nuelink integration. You will see the sorted list while you type in, and finally, the Nuelink app will be displayed. Just click the app icon and it will be set as the action app.

![](/storage/kb-images/cc19f31a99-Screenshot-2024-12-03-180558-1024x438.png)

## Configure the options

### 4\. Choose Connect

We need to choose the connection we created previously by authorizing the Nuelink account. Just click on the Choose Connect dropdown, it will display the list of available connects.

![](/storage/kb-images/10b9532ae5-Screenshot-2024-12-03-232019-1024x439.png)

### 5\. Search and Select Nuelink Connect

Type the Nuelink connect name we used while creating the connect, and select it. Now, every time this action step is executed, the authorization details from this connection will be used to connect to the Nuelink account.

![](/storage/kb-images/9292c51bd3-Screenshot-2024-12-03-233117-1024x541.png)

### 6\. Enter the Caption

Caption is a required field. You must provide the caption, which is the body text for your social media post.

![](/storage/kb-images/38956b6c43-Screenshot-2024-12-03-233501.png)

### 7\. Provide Media URL

If you want to display the image or video in your post, just provide the appropriate file URL. FlowMattic will automatically detect the file type and set it accordingly in the Nuelink post.

![](/storage/kb-images/64bb3af319-Screenshot-2024-12-03-234043.png)

### 8\. Enter Alt Text

Refer the Nuelink documentation to see how the Alt Text works.

![](/storage/kb-images/0eaa4d901a-Screenshot-2024-12-03-234224.png)

### 9\. Provide Title Text

Refer the Nuelink documentation to see how the Title Text works.

![](/storage/kb-images/dbbe7063e5-Screenshot-2024-12-03-234402.png)

### 10\. Set Share to Feed (Instagram Reels)

If you want to set this post to be shared to your Instagram feed, turn this option ON.

![](/storage/kb-images/24d3195c90-Screenshot-2024-12-03-234514.png)

### 11\. Set Share as Short

If the post is for video, you can set to create shorts from it and share on your social media accounts connected to your Nuelink account.

![](/storage/kb-images/8e2e4ac59c-Screenshot-2024-12-03-234652.png)

### 12\. Text Action and Save & Close

After setting up the required options, click the "Test Action" button to perform a live test with the data you have entered. To confirm that the workflow is working, verify that the new post appears in your Nuelink collection. Then click "Save and Close."

![](/storage/kb-images/a7db4c5d34-Screenshot-2024-12-03-234912.png)

---

# How to Use the Email Template Builder in FlowMattic

Source: https://support.flowmattic.com/kb/article/61/how-to-use-the-email-template-builder-in-flowmattic

FlowMattic’s **Email Template Builder** makes it super easy to create and manage custom email templates for your workflows. Whether you want to send newsletters, notifications, or promotional content, you can do it all with just a few clicks — no coding required!

Follow this step-by-step guide to create your own email template, customize it, and even use dynamic data.

---

## 🚀 Step 1: Navigate to the Email Templates Section

From your FlowMattic dashboard:

1. Look at the left sidebar.
2. Click on **Email Templates**.
3. You will be redirected to the admin page of your Email Templates. Here, you can create new templates, edit existing templates, delete unused templates or clone existing to get started easily.

![Zight 2025-04-09 at 4.05.11 AM.png](/storage/kb-images/6daab7c5f2-inline.png)

> 📌 This section is dedicated to creating and managing your reusable email layouts.

---

## ➕ Step 2: Create a New Template

If you don’t have any templates created yet, you’ll see a message saying “No Templates Found.”

To create your first template:

- Click on the **+ Create New Template** button (top-right or center of the page).
- It will open a modal asking you to enter template name and choose pre-built template to start with

![Zight 2025-04-09 at 3.34.45 AM.png](/storage/kb-images/1a39f4b5fe-inline.png)

---

## 🧱 Step 3: Choose a Template Type

You'll now see a popup titled **"Create New Template"**.

1. **Enter a name** for your template (e.g., `Weekly Newsletter`).
2. Choose from the **Prebuilt Templates** or start from scratch with a **Blank Template**.
3. Click the **Use Template** button under the one you want.
4. You will be redirected to the Email Template Builder with your selected Email Template pre-loaded. 
5. Customize it as per your requirements, and make sure to hit the **SAVE** button or your changes will be lost.

> 💡 You can always edit any section of the template you choose, so pick the one that’s closest to what you want to send.

![Zight 2025-04-09 at 3.35.43 AM.png](/storage/kb-images/9328d025dc-inline.png)

---

## 🎨 Step 4: Customize the Template

After importing the template, it opens in the **visual editor**.

Here’s what you can do:

- **Click on any block** (image, heading, button, etc.) to edit it.
- **Click the + icon** to **add a new block** (see image).

![Zight 2025-04-09 at 3.39.28 AM.png](/storage/kb-images/8cdc439935-inline.png)

- Available blocks include:
  - **Heading** – Add titles or section headings.
  - **Text** – Add regular paragraph text.
  - **Button** – Add clickable buttons with links.
  - **Image** – Upload and insert an image.
  - **Avatar** – Add user profile images.
  - **Divider** – Insert a line divider between sections.
  - **Spacer** – Add white space.
  - **HTML** – Embed custom HTML.
  - **Columns** – Create multi-column layouts.
  - **Container** – Group multiple blocks together.

You can **move** or **delete** blocks using the floating toolbar that appears when you click on any block.

---

## ✨ Step 5: Use Dynamic Data

You can use **dynamic placeholders** to insert personalized content automatically, such as the user’s name, email, links, etc.

1. Click on the **Data** tab (top-right side of the editor).
2. You’ll see a prefilled JSON object like if you have a template imported that supports dynamic data:

```json
{
  "unsubscribe_link": "#",
  "whats_new_link": "#",
  "preview_updates_link": "#"
}
```

3. You can add your own fields. Example:

```json
{
  "first_name": "John",
  "last_name": "Doe",
  "account_link": "https://yourdomain.com/account"
}
```

4. To use these values inside the email, use this format:

- `{{first_name}}` → Displays "John"
- `{{account_link}}` → Can be used to replace the button URLs or links etc.

> 🧠 Tip: These placeholders will be replaced with actual values during the email send process inside your workflow.

---

## ✉️ Step 6: Send a Test Email (Optional)

Before using your template in a workflow, you can test how it looks:

1. Click the **Send Test Email** button in the left sidebar.
2. You will be prompted to enter an email address to send the test email to.
3. The test email you send will prepend the text "Test Email" to the subject to avoid confusion.
4. Once you enter the email and click send test email button, it sends a preview to your configured test address using the mock data under the `Data` tab.

---

## 💾 Step 7: Save the Template

Once you’re done editing:

- Click the **SAVE** button at the top to save your template.
- This is a required step. Without clicking the Save button, no changes or the template itself will be saved.

---

## 🔄 Step 8: Use the Template in a Workflow

To send emails using your template:

1. Go to **Workflows** and edit your existing workflow or create new one.
2. Add a step using the **Email SMTP** module and **Send Template Email** action.
3. In the template selection dropdown, choose the template you just created.
4. If you have configured the Dynamic Data within the template, you will get an option to provide the values for each data item. You can map the data with previous action step responses or trigger response as well.

![Zight 2025-04-09 at 4.06.51 AM.png](/storage/kb-images/588fa5ba3c-inline.png)

> ✅ FlowMattic will automatically replace dynamic variables with actual data from your workflow execution.

---

## 📚 Final Notes

- You can always return to **Email Templates** to update or duplicate your templates.
- Make sure your **SMTP settings** are correctly configured under **Settings → Email SMTP**.
- This feature is perfect for automating marketing emails, updates, onboarding, and more.

---

Got questions or need help? Check out our support portal or reach out via chat! 🎯

---

# How to Use the PHP Functions Module in FlowMattic Workflows

Source: https://support.flowmattic.com/kb/article/51/how-to-use-the-php-functions-module-in-flowmattic-workflows

The PHP Functions module in FlowMattic allows you to enhance your workflows by integrating custom or predefined PHP functions. This module is particularly useful when existing modules are insufficient for your requirements or when you need to perform advanced operations. Here's a detailed guide to help you get started:

### Steps to Use the PHP Functions Module

1. **Write or Add Your PHP Function**
   - Create a custom PHP function or use a predefined one.
   - Insert your custom function into your site using plugins like [Fluent Snippets](https://wordpress.org/plugins/easy-code-manager/) or similar tools.
   - Ensure the function is publicly accessible. For class-based functions, ensure they are static (e.g., `MyClass::my_function`).

2. **Configure the PHP Functions Module**
   - **Function Name**: Enter the name of your PHP function. For example, use `my_function` for standalone functions or `MyClass::my_function` for static class functions.
   - **Function Parameters Type**: Select how to pass parameters:
     - `Single Array`: Combines all parameters into a single array.
     - `Individual Variables`: Passes each parameter as a separate variable.
     - `No Parameters`: Use this if your function does not require any parameters.
   - **Function Parameters**: Add the required parameters as key-value pairs. FlowMattic provides an intuitive UI for this. For example, you can pass parameters as:
     ```php
     array(
         "key1" => "value1",
         "key2" => "value2"
     )
     ```

3. **Handle JSON Data** (Optional)
   - If your function requires JSON data, use the `JSON Value Decode` option to convert the JSON input into a PHP array. Set this option to `Yes` to enable decoding.

### Tips for Best Practices
- Always test your PHP function independently before using it in a workflow to ensure it behaves as expected.
- Use descriptive parameter keys to make your workflows easier to debug and maintain.
- If you're using third-party plugins for adding custom PHP functions, ensure they are compatible with your WordPress version and FlowMattic.

### Example Workflow
Suppose you have a custom function named `calculate_discount` that calculates a discount based on an order total and a discount percentage. Here's how you can configure the PHP Functions module:

 
 ![PHP Functions module configuration](/storage/kb-images/d4afea5bef-inline.png)

- **Function Name**: `calculate_discount`
- **Function Parameters Type**: `Individual Variables`
- **Function Parameters**:
  ```
  order_total => 100
  discount_percentage => 10
  ```
- **JSON Value Decode**: `No`

When executed, the `calculate_discount` function will process the parameters and return the calculated discount value.

By leveraging the PHP Functions module, you can greatly expand the capabilities of your workflows, making them more dynamic and tailored to your specific needs.

---

# Human in The Loop (HITL) Module by FlowMattic

Source: https://support.flowmattic.com/kb/article/103/human-in-the-loop-hitl-module-by-flowmattic

## What is Human in The Loop?

Human in The Loop (HITL) is a powerful FlowMattic feature that introduces manual approval steps into automated workflows. This module allows you to pause workflow execution at critical points and wait for human approval or rejection before proceeding. It bridges the gap between full automation and human oversight, ensuring important decisions remain under human control while still benefiting from workflow automation.

Think of HITL as a smart pause button in your workflows that sends approval requests via email, waits for a response, and then continues the workflow based on whether the request was approved or rejected.

## Key Features

### Core Capabilities
- **Email-based Approval Requests**: Send beautifully formatted HTML emails with approve/reject buttons
- **Time-bound Requests**: Set expiration times for approval requests (minutes, hours, or days)
- **Smart Timeout Actions**: Configure what happens when requests expire
- **Round-Robin Assignment**: Distribute approval requests evenly among team members
- **Request Reassignment**: Automatically or manually reassign requests to other approvers
- **User Response Messages**: Approvers can add optional messages when responding
- **Request Tracking**: Full audit trail of all approval requests and responses

### Visual Status Indicators
The HITL module provides clear visual feedback in the Task History:
- **Green checkmark**: Request approved

![human in the look - request approved](/storage/kb-images/743ce87808-inline.png)

- **Yellow hourglass**: Waiting for response

![human in the look - request pending](/storage/kb-images/da49b1daab-inline.png)

- **Red hourglass**: Request expired/timed out

![human in the look - request timed-out](/storage/kb-images/90dd0a854c-inline.png)

- **Red Exclamation**: Request rejected

![human in the look - request rejected](/storage/kb-images/f5ee090105-inline.png)

## Getting Started

### Step 1: Add HITL to Your Workflow

1. Open your workflow in the FlowMattic editor
2. Click "Add New Step" where you want the approval point
3. Select "Human in the Loop" from the applications list
4. Choose "Get Approval on Email" as the action

![Human in the loop node and settings.png](/storage/kb-images/4312886daa-inline.png)

### Step 2: Basic Configuration

Configure these essential fields:

- **Sender Name**: The name that appears in the approval email (e.g., "Sales Team")
- **Email Subject**: Subject line for the approval email
- **Approval Headline**: Main heading in the email body
- **Approval Message**: Detailed message explaining what needs approval
- **Assignee Email**: Email address of the person who needs to approve

## Configuration Options

### Timeout Settings

Control how long the workflow waits for approval:

- **Max Wait Time**: Number value (1-999)
- **Timeout Unit**: Choose from:
  - Minutes
  - Hours
  - Days

### Timeout Actions

Define what happens when a request expires:

1. **Skip and Continue** (Default)
   - Workflow continues as if approved
   - Status marked as "approved_with_timeout"
   - Useful for non-critical approvals where proceeding is safe

2. **End Workflow**
   - Stops workflow execution completely
   - Status marked as "timeout_ended"
   - Use for critical approvals that must not proceed without human input

3. **Reassign**
   - Sends request to a backup approver
   - Specify reassignment email in configuration
   - Maximum 3 reassignment attempts for round-robin, 1 for custom assignee
   - If all reassignment attempts expire, workflow stops

![HITL - time out settings.png](/storage/kb-images/0c51764128-inline.png)

### Assignment Types

#### Custom Assignment
Direct assignment to a specific email address. This is the simplest approach for single approvers.

```
Assignee Type: Custom
Assignee Email: manager@company.com
```

#### Round-Robin Assignment
Distributes approval requests evenly among team members:

1. Select "Round Robin" as assignee type
2. Choose a user role (e.g., "Administrator", "Editor")
3. Optionally filter by user meta key/value
4. System automatically tracks and assigns to least recently assigned user

![HITL - round robbin assignment.png](/storage/kb-images/80fc655272-inline.png)

### Optional Fields

- **Email Subject**: Custom subject line (defaults to "Approval Requested: [Headline]")
- **Reassign Email**: Backup approver for timeout reassignments
- **User Meta Filters**: For round-robin, filter eligible users by custom meta data

## Understanding the Approval Process

### The Approval Flow

1. **Request Creation**
   - Unique request ID generated
   - Request saved to database
   - Approval email sent to assignee

2. **Email Receipt**
   - Assignee receives HTML email with:
     - Clear approval message
     - Workflow name and sender info
     - Three action buttons: Approve, Reject, View Details
     - Expiration time warning

3. **Response Options**
   - **Approve**: Workflow continues with approved status
   - **Reject**: Workflow stops execution (rejection is logged in task history)
   - **View Details**: Opens detailed view with optional message field

4. **Workflow Behavior**
   - **If Approved**: Workflow continues with approval data
   - **If Rejected**: Workflow stops, rejection is recorded in task history
   - **If Timeout**: Behavior depends on timeout action setting:
     - Skip and Continue: Workflow continues
     - End Workflow: Workflow stops
     - Reassign: Request sent to backup approver

![Approval Required email.png](/storage/kb-images/f9ca1f02d6-inline.png)

### The View Details Page

When clicking "View Details", approvers see:
- Complete request information
- Full approval message
- Option to add a response message
- Approve/Reject buttons
- Request expiration time
- Request history and status

![Approval Request Details page.png](/storage/kb-images/c5bc8dd5e8-inline.png)

## Task History Indicators

The Task History provides visual indicators for HITL status:

### Status Icons
- **Green Checkmark**: Request approved successfully
- **Yellow Hourglass**: Currently waiting for response
- **Red Exclamation**: Request was rejected
- **Red Hourglass**: Request expired without response

### Status Details
Each HITL step in Task History shows:
- Current approval status
- Request creation time
- Assignee information
- Expiration time
- Response details (if responded)

## Database Cleanup Settings

To maintain optimal performance, FlowMattic includes automatic cleanup for expired HITL requests.

### Configuring Cleanup

1. Navigate to **FlowMattic > Settings**
2. Find the "Human in the Loop" section
3. Configure these options:

**Clean Human in the Loop Data?**
- Yes: Enable automatic cleanup
- No: Disable cleanup (keeps all data)

**Human in the Loop Cleanup (Days)**
- Enter number of days (1-365)
- Default: 90 days
- Requests older than this are automatically deleted

![Settings ‹HITL.png](/storage/kb-images/6ac82d380c-inline.png)

### How Cleanup Works
- Runs daily via WordPress cron
- Deletes requests where expiration date is older than specified days
- Maintains database performance
- Preserves recent history for auditing

## Real-World Examples

### Example 1: Purchase Order Approval

**Scenario**: Automatically approve purchase orders under $500, but require manager approval for higher amounts.

**Workflow Setup**:
1. Trigger: New purchase order submitted
2. Router: Check if amount > $500
3. If Yes: HITL approval step
4. If Approved: Process order
5. If Rejected: Workflow stops (consider sending rejection notification before HITL step)

**HITL Configuration**:
```
Sender Name: Purchasing Department
Approval Headline: Purchase Order Approval Required
Approval Message: 
  Order #{{order_number}}
  Amount: ${{order_amount}}
  Vendor: {{vendor_name}}
  Items: {{item_list}}
  
  Please review and approve this purchase order.
  
Max Wait Time: 24
Timeout Unit: Hours
Timeout Action: Reassign
Assignee Email: {{manager_email}}
Reassign Email: {{finance_director_email}}
```

### Example 2: Content Publishing Approval

**Scenario**: Blog posts need editorial review before publishing.

**Workflow Setup**:
1. Trigger: New post created in WordPress
2. HITL: Send to editor for review
3. If Approved: Publish post and notify author
4. If Rejected: Workflow stops (post remains in draft)

**HITL Configuration**:
```
Sender Name: Content Team
Approval Headline: New Article Ready for Review
Approval Message:
  Title: {{post_title}}
  Author: {{author_name}}
  Category: {{post_category}}
  Word Count: {{word_count}}
  
  Preview URL: {{preview_link}}
  
  Please review this article for publication.

Assignee Type: Round Robin
User Role: Editor
Max Wait Time: 4
Timeout Unit: Hours
Timeout Action: Skip and Continue
```

### Example 3: Customer Refund Processing

**Scenario**: Refund requests above $100 need manual approval.

**Workflow Setup**:
1. Trigger: Refund request form submission
2. Condition: Check refund amount
3. HITL: Manager approval for high-value refunds
4. If Approved: Process refund
5. If Rejected: Workflow stops (no refund processed)

**HITL Configuration**:
```
Sender Name: Customer Service
Email Subject: Urgent: Refund Approval Needed
Approval Headline: Customer Refund Request
Approval Message:
  Customer: {{customer_name}}
  Order ID: {{order_id}}
  Refund Amount: ${{refund_amount}}
  Reason: {{refund_reason}}
  
  Customer History:
  - Total Orders: {{total_orders}}
  - Customer Since: {{customer_since}}
  
Max Wait Time: 2
Timeout Unit: Hours
Timeout Action: End Workflow
Assignee Email: {{customer_service_manager}}
```

### Example 4: Employee Leave Approval

**Scenario**: Vacation requests need manager approval with automatic delegation.

**Workflow Setup**:
1. Trigger: Leave request form submission
2. HITL: Send to direct manager
3. If Approved: Update HR system and notify employee
4. If Rejected: Workflow stops (consider separate workflow for rejection notifications)

**HITL Configuration**:
```
Sender Name: HR System
Approval Headline: Leave Request
Approval Message:
  Employee: {{employee_name}}
  Leave Type: {{leave_type}}
  Start Date: {{start_date}}
  End Date: {{end_date}}
  Days Requested: {{total_days}}
  
  Current Leave Balance: {{leave_balance}}
  Team Coverage: {{coverage_plan}}

Assignee Type: Custom
Assignee Email: {{manager_email}}
Max Wait Time: 48
Timeout Unit: Hours
Timeout Action: Reassign
Reassign Email: {{hr_manager_email}}
```

## Best Practices

### 1. Clear and Actionable Messages
- Write concise approval headlines
- Include all necessary context in the message
- Use dynamic data to personalize requests
- Highlight critical information

### 2. Appropriate Timeout Settings
- **Urgent requests**: 1-4 hours
- **Standard approvals**: 24-48 hours
- **Non-urgent reviews**: 3-7 days
- Consider business hours and time zones

### 3. Smart Timeout Actions
- Use "Skip and Continue" for non-critical approvals
- Use "End Workflow" for compliance-critical decisions
- Use "Reassign" for time-sensitive but important approvals

### 4. Round-Robin Considerations
- Ensure all users in the role are trained
- Set up user meta filters for specialized approvals
- Monitor distribution for fairness

### 5. Understanding Workflow Continuation
**Important**: Workflow behavior depends on the response:
- **Approved**: Workflow continues to next steps
- **Rejected**: Workflow stops immediately (no further steps execute)
- **Timeout with "Skip and Continue"**: Workflow continues
- **Timeout with "End Workflow"**: Workflow stops
- **Timeout with "Reassign"**: Waits for new approver

For rejection notifications, consider:
- Setting up a separate workflow triggered by HITL rejection events
- Sending a preliminary notification email before the HITL step
- Using webhooks to notify external systems of rejections

### 6. Testing Recommendations
- Test with short timeout periods first
- Verify email delivery to all assignees
- Test all three response scenarios
- Check timeout actions work correctly

## Troubleshooting

### Common Issues and Solutions

**Approval emails not received:**
- Check spam/junk folders
- Verify email address is correct
- Check WordPress email configuration
- Test with a different email provider

**Requests expiring too quickly:**
- Review timeout settings
- Consider timezone differences
- Extend timeout period if needed
- Use reassignment for backup

**Round-robin not distributing evenly:**
- Check user role assignments
- Verify all users are active
- Review user meta filters
- Check last assignment timestamps

**Workflow not continuing after approval:**
- Verify workflow is still active
- Check for errors in subsequent steps
- Review workflow logs
- Ensure proper error handling

**View Details page showing errors:**
- Check REST API is accessible
- Verify permalink settings
- Clear cache if using caching plugin
- Check for plugin conflicts

### Database Maintenance

For large-scale operations:
- Regular cleanup reduces database size
- Set appropriate retention periods
- Monitor database performance
- Consider archiving old approval data

## Advanced Tips

### Using Dynamic Data
Leverage FlowMattic's dynamic data system:
```
Approval Message: 
  Order from {{customer_name}}
  Total: ${{order_total}}
  Items: {{order_items}}
```

### Conditional Reassignment Logic
For complex reassignment scenarios, use a Router step before HITL:
1. Add Router to check conditions (e.g., amount > 1000)
2. Create separate HITL steps for each condition
3. Configure different assignees based on the condition
   - Route 1: Amount > 1000 → HITL with CFO as assignee
   - Route 2: Amount <= 1000 → HITL with Manager as assignee

This approach gives you full control over conditional approval routing.

### Integration with Other Apps
HITL works seamlessly with:
- CRM systems for customer approvals
- Project management for task approvals
- Accounting software for financial approvals
- HR systems for employee requests

## Security Considerations

- Approval URLs are unique and unguessable
- Requests expire after set time
- Each request can only be actioned once
- Database entries are automatically cleaned
- No sensitive data in URL parameters

## Summary

The Human in The Loop module transforms FlowMattic workflows by adding intelligent approval gates. It ensures critical decisions receive human oversight while maintaining automation efficiency. With flexible timeout options, round-robin assignment, and comprehensive tracking, HITL provides enterprise-grade approval management for businesses of all sizes.

Whether you're processing purchase orders, reviewing content, or managing employee requests, HITL ensures the right person reviews the right information at the right time, all while keeping your workflows running smoothly.

---

**Need Help?**
For additional support or questions about the Human in The Loop module, please contact FlowMattic support or visit our community forums.

**Version History**
- v5.3.0: Initial release of Human in The Loop module
- Includes email-based approvals, round-robin assignment, and automatic cleanup features

---

# Image Compressor

Source: https://support.flowmattic.com/kb/article/112/image-compressor

Optimize and compress images automatically in your WordPress workflows with FlowMattic's Image Compressor integration. Reduce image file sizes by up to 80% while maintaining quality, convert images to WebP format for faster loading times, and automatically save compressed images to your WordPress media library. Perfect for e-commerce sites, photography portfolios, news websites, and any WordPress site that needs automated image optimization to improve page speed and reduce bandwidth costs.

## Key Features

Image Compressor provides powerful image optimization capabilities with configurable quality settings (1-100), support for multiple formats (JPEG, PNG, WebP), intelligent resizing while maintaining aspect ratio, and automatic WordPress media library integration. All compression is handled through FlowMattic's optimized compression API, ensuring fast processing and consistent results. The integration works seamlessly with dynamic data from previous workflow steps, making it perfect for automated image processing pipelines.

### When to use Image Compressor

- **Optimize user uploads**: Automatically compress images uploaded by users through forms or submissions
- **Reduce storage costs**: Compress images before storing them in your media library or cloud storage
- **Improve page speed**: Convert and compress images for faster website loading times
- **Batch processing**: Process multiple images from external sources (APIs, webhooks, etc.)
- **Format conversion**: Convert images to modern formats like WebP for better compression
- **Responsive images**: Resize images to specific dimensions for different use cases

---

## How to Use Image Compressor

### 1. Add Image Compressor to Your Workflow

In your workflow builder:
1. Click the **+** button to add a new step
2. Search for and select **Image Compressor** from the core integrations
3. Choose the **Compress Image** action

### 2. Configure Compression Settings

**Image URL** (Required)
- Enter the URL of the image you want to compress
- Can use dynamic data from previous workflow steps
- Supports most common image formats (JPEG, PNG, GIF, WebP, etc.)

**Quality** (Optional, default: 80)
- Set compression quality from 1-100
- Higher values = better quality but larger file size
- Lower values = smaller file size but reduced quality
- Recommended: 70-85 for optimal balance

**Output Format** (Optional, default: Auto)
- **Auto**: Keeps the original image format
- **JPEG**: Convert to JPEG format (best for photos)
- **PNG**: Convert to PNG format (best for graphics with transparency)
- **WebP**: Convert to WebP format (modern format with excellent compression)

**Enable Resize** (Optional, default: No)
- Choose **Yes** to resize images to specific dimensions
- Choose **No** to keep original dimensions

**Max Width** (Optional, default: 1920px)
- Only applies when resize is enabled
- Image will be scaled down if wider than this value
- Maintains aspect ratio

**Max Height** (Optional, default: 1080px)
- Only applies when resize is enabled
- Image will be scaled down if taller than this value
- Maintains aspect ratio

### 3. Use the Compressed Image

After compression, Image Compressor returns the following data:

- `media_id`: WordPress media library ID
- `media_url`: URL of the compressed image
- `media_title`: Image title in media library
- `media_type`: MIME type of the image
- `width`: Image width in pixels
- `height`: Image height in pixels
- `file_size`: File size in bytes
- `compression_quality`: Quality setting used
- `format`: Output format used
- `original_url`: Original image URL

You can use these values in subsequent workflow steps.

---

## Example Use Cases

### Compress User Profile Pictures
When a user uploads a profile picture via a form:
1. **Trigger**: Form Submission
2. **Image Compressor**: Compress to 200x200px, 75% quality
3. **WordPress**: Update user meta with compressed image URL

### Convert Images to WebP
When processing product images from a supplier API:
1. **Trigger**: Webhook/API Call
2. **Image Compressor**: Convert to WebP format, 85% quality
3. **WooCommerce**: Update product with new image

### Batch Resize Gallery Images
When importing images from external source:
1. **Trigger**: Schedule/Manual
2. **Image Compressor**: Resize to 1920x1080, 80% quality
3. **Custom Action**: Save to specific media library folder

---

## Troubleshooting

**Image compression fails**
- Verify the image URL is publicly accessible
- Check that the URL points to a valid image file
- Ensure the source image is not corrupted

**Compressed image is too large/small**
- Adjust the quality setting (try values between 70-85)
- Enable resize and set appropriate max dimensions
- Try converting to WebP format for better compression

**Image quality is poor**
- Increase the quality setting (try 85-95)
- Avoid compressing already-compressed images multiple times
- Use PNG format for graphics/screenshots instead of JPEG

**Resize not working**
- Make sure "Enable Resize" is set to "Yes"
- Verify max width/height values are smaller than the original image
- Images smaller than max dimensions won't be enlarged

**Image not appearing in media library**
- Check WordPress media upload permissions
- Verify sufficient disk space is available
- Check error logs for specific upload errors

---

# Images are not rendering or the Image Builder step fails

Source: https://support.flowmattic.com/kb/article/193/images-are-not-rendering-or-the-image-builder-step-fails

## Symptom

The Image Builder action produces no image, returns an error, or the Download Image test render fails.

## Cause

Image generation runs entirely through **Cloudflare Browser Rendering**. Unlike PDF generation, there is no local fallback engine for images — so if Cloudflare credentials are missing, invalid, or the account has hit its limit, images cannot render at all.

## Fix

**1. Confirm Cloudflare credentials are configured.**
Open **FlowMattic → Settings → Cloudflare**. Both the **Cloudflare Account ID** and the **Cloudflare API Token** must be filled, and the page must show the green "configured" confirmation. If either field is empty, images will not render. See *Set up Cloudflare Browser Rendering*.

![FlowMattic Settings → Cloudflare tab with both fields filled and the green "configured" confirmation](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-cloudflare-01-settings-cloudflare.png)

**2. Check the token's permission.**
The API Token must have **Account → Browser Rendering → Edit** permission. A token created for a different purpose will be rejected. If in doubt, create a fresh token with exactly that permission and paste it in again.

**3. Check your Cloudflare render quota.**
Cloudflare Browser Rendering has a monthly render limit. If you generate images in bulk (for example inside an Iterator over a large list), you can exhaust the quota, after which renders fail until the quota resets or you upgrade the plan.

**4. Check the WordPress error log.**
A failed render records the Cloudflare error in the WordPress error log. The message usually states the exact reason — an authentication failure, a quota limit, or a temporary Cloudflare issue — which tells you which of the steps above to act on.

![The WordPress error log showing a line from the Image Builder that names the Cloudflare error.](https://assets.infidesk.support/kb/inline/2026/07/Ncqur5pDxfhHjD0mD6bBXn5woAl6P5evu6ahmtU9.png)

## Note

The same Cloudflare credentials power the PDF Builder's pixel-accurate mode, the FlowMattic Browser integration, and the AI Agent's browsing tool. If images stopped rendering after those other features also stopped working, the shared credentials are the common cause.

---

# Image Template Builder

Source: https://support.flowmattic.com/kb/article/157/image-template-builder

The Image Template Builder is FlowMattic's visual designer for creating reusable image templates — Open Graph cards, social posts, banners, coupons, and any branded visual. You build a design once on a fixed-size canvas, drop in `{{tokens}}` wherever you want live data to appear, and later a workflow renders the template to a PNG with those tokens filled in. You reach it from **FlowMattic → Image Templates**.

![The Image Templates listing page showing the New Image Template and Generate with AI buttons in the header, the stats row with Total Templates, Images Generated and Render Engine Cloudflare, and the templates table below](https://assets.infidesk.support/kb/inline/2026/07/MFVSPzggIyysDYI1ED32iwZRGZAv36izguiKSKmH.png)

## Creating a template

On the **Image Templates** listing page, click **New Image Template**. A dialog opens with a **Template Name** field (required) and a starter grid. Type a name (for example, "Blog OG Card"), then either:

- Pick one of the prebuilt **starter templates** ("Use This"), or
- Choose a **Start Blank** tile to begin from an empty canvas in one of three base sizes, or
- Click **Generate with AI** to describe the design in words and have AI compose a starter you can refine.

Picking a starter opens the editor with that design preloaded. New blank templates open on the **Blog Post — Social Card** (`og-blog`) starter by default so you always have something to edit instead of a blank screen.

The starters are grouped into categories: **Start** (the three blanks), **Open Graph**, **Social**, **Marketing**, **Ads**, and **Misc.** Examples include "Blog OG Image", "Stat Highlight", "Author Card", "Newsletter Signup", "Social Quote", "Podcast Episode", "Announcement", "Team Spotlight", "Product Launch", "Feature Banner", "Testimonial Banner", "Coupon Code", "Countdown Timer", "Before vs After", "Course Update", and "Feature Checklist". Each tile shows its dimensions (for example, 1200×630 for Open Graph, 1080×1080 for square social posts, 1080×1350 for portrait).

![The "New Image Template" dialog with the Template Name field and the starter grid showing the category sections and a "Generate with AI" tile](https://assets.infidesk.support/kb/inline/2026/07/MfJZ9NrVeoXIuRPyTqBwSKBiduUxG91phnEjKKEl.png)

## The editor layout

The editor has three areas: a **Library** panel on the left, the **canvas** in the center, and a **properties panel** on the right. Across the top is a toolbar.

![The full Image Template Builder editor: left Library panel, the center canvas with a sample design, and the right properties panel with an element selected](https://assets.infidesk.support/kb/inline/2026/07/xHDmcoY9mVxnpV7DWkwyW9qeVfp1sb2mK43EktbP.png).

### Top toolbar

The toolbar shows the product label, an editable **template name** input, and a **Saved · 2m ago** status chip that updates after each save. In the center is a **Design / Code** view switch — **Design** is the visual editor; **Code** shows the generated HTML. On the right are **Undo** and **Redo** buttons, **Edit Sample Values**, **Preview**, a help button, and **Save**.

### Left panel (Library)

The **Library** panel has three tabs and a search box that filters the active tab:

- **Templates** — browse and load any starter (grouped by category), plus a **Generate with AI** tile labeled "Describe your design".
- **Elements** — under the heading **Drag onto canvas**, a grid of element tiles. Click a tile to add that element to the center of the canvas (you can then drag to reposition).
- **Layers** — a list of every element on the canvas, top layer first (matching the Photoshop/Figma stacking order). Each row has the element's name and a visibility toggle (**Hide layer / Show layer**). Drag rows to reorder which elements sit on top. Reordering is disabled while a search filter is active.

![The left Library panel on the Elements tab, showing the "Drag onto canvas" grid of element tiles.](https://assets.infidesk.support/kb/inline/2026/07/4dhO9hzJyHDwKkXpivCiZOAQxG5NXvdOf9Z7IElA.png)

## Element types

Click an element in the **Elements** tab to add it. The original core set is ten element types, joined by a set of layered design elements for richer compositions.

### Core elements

- **Heading** and **Paragraph** (text) — editable text. The **Text** field accepts `{{tokens}}`, with an **Insert placeholder** button to drop one in. Style controls include **Font family**, **Size** (px), **Weight** (Light/Regular/Medium/Semibold/Bold/Extrabold), **Alignment** (Left/Center/Right/Justify), **Line height**, and **Color**.
- **Image** — a photo placeholder. **Source** accepts a URL or a `{{token}}`; **Alt text** for accessibility; **Fit** (Cover/Contain/Fill) and a **Corner radius** slider.
- **Avatar** — a profile photo. **Image URL** (or a token like `{{user_avatar}}`), a **Shape** (Circle/Rounded/Square), plus **Border color** and **Border width**.
- **Button** — a call-to-action shape with a **Label**, **Background** color, and **Text** color.
- **Icon** — a vector icon. The **Icon** dropdown offers Star, Heart, Check, Bolt / Lightning, Arrow Right, Sparkles, Lock, Globe, Chart, Shield, Rocket, Mail, and **Custom SVG…** (paste your own `<svg>` markup). Plus **Color** and **Size**.
- **Shape** — a simple rectangle/circle with a **Fill** color (hex or rgba) and a **Corner radius** slider (set it high for a perfect circle).
- **Divider** — a horizontal rule with a **Style** (Solid/Dashed/Dotted), **Color**, and **Thickness**.
- **Logo** — a logo image with **Source** (URL or token), **Alt text**, **Fit** (Contain/Cover/Fill), and **Corner radius**.
- **QR Code** — a scannable code generated from the **URL / Value** field (which can contain a `{{token}}` such as `{{post_url}}`), with **Foreground** and **Background** colors and an **Error correction** level (**L / M / Q / H**).

### Layered design elements

For more elaborate layouts the builder also includes **Pattern Shape** (dots/stripes/grid/checker fills), **Border Shape** (outlined rings — stack them for a "sonar" effect), **Waves** (decorative SVG wave bands with selectable styles, position, direction, and up to three colors), **Arrow** (curved/straight/elbow/etc. with adjustable head size and line style), **Callout Lines** (sparkle/burst/accent/motion accents), **Ribbon** (banner/folded/corner/pennant/tag/chevron styles with an optional inline stitched border), **Badge** (speech-bubble or starburst), and **Coupon** (plain or notched "ticket" with a dashed border). Each has its own style controls in the right panel.

## Placing and styling elements (the canvas)

The canvas is a fixed-size stage that always shows the template at its exact pixel dimensions. The toolbar above it displays the current **width × height**, a **Sample data / Tokens** preview toggle, and a **zoom** control (10%–200%). When you open a template, the zoom auto-fits the design to your screen.

Working on the canvas:

- **Drag to position** — click and drag any element to move it. Movement tracks your cursor at any zoom level, and final positions snap to whole pixels.
- **Alignment guides and snapping** — while dragging, the builder shows blue guide lines and snaps the element to the edges and centers of other elements and the canvas. Hold **Alt/Option** while dragging to turn snapping off for free placement.
- **Resize handles** — a selected element shows eight handles (four corners, four edges). Corners resize both dimensions; edges resize one axis. Elements won't shrink below 8px.
- **Multi-select** — **Shift-click** to add or remove elements from a selection. Dragging any member moves the whole group together. Click an empty area or press **Esc** to clear the selection.

The right panel always exposes a **Position & size** group (**X**, **Y**, **W**, **H**, **Opacity**, and **Rotation** from −180° to 180°) for the selected element, so you can type exact values instead of dragging.

![The canvas with one element selected, showing the eight resize handles and a blue alignment guide while dragging](https://assets.infidesk.support/kb/inline/2026/07/rMiMvAuqhLyO73ZQuCKn2U9RDkGanl3pt980QvZO.png).

## Setting the background

Open the **Template** tab in the right panel to control the whole canvas.

The **Canvas** group has a **Preset** dropdown — **Open Graph (1200×630)**, **Square (1080×1080)**, **Portrait 4:5 (1080×1350)**, **Story 9:16 (1080×1920)**, **Twitter Header (1500×500)**, or **Custom…** — plus **W** and **H** inputs for custom sizes.

The **Background** group offers a **Type** switch with four options:

- **Gradient** (the default) — pick a **From** and **To** color and an **Angle** (0°–360°). Gradients use exactly two color stops.
- **Solid** — a single **Color**.
- **Pattern** — a repeating **Dots / Stripes / Grid / Checker** pattern with a **Pattern color**, **Background** color, and **Scale**.
- **Image** — an **Image URL** (or token), a **Fit** (Cover/Contain/Stretch), a **Position**, and an **Overlay color** with an **Overlay opacity** slider to darken or tint the photo.

![The right panel on the Template tab, showing the Canvas preset dropdown and the Background type switch with the gradient From/To/Angle controls](https://assets.infidesk.support/kb/inline/2026/07/fPKyUmUVkpGokX9oSTOhdtFHlQP7sPTEvdm3yXBN.png).

## Binding tokens for dynamic data

A **token** is a placeholder written as `{{token_name}}` (for example `{{post_title}}` or `{{user_name}}`). It marks a spot in your design that a workflow fills in with real data at render time. The token name allows letters, numbers, underscores, dots, and hyphens.

There are two ways to add a token:

- **In a text element** — type `{{post_title}}` directly into the **Text** field, or use the **Insert placeholder** button to pick one. URL/value fields on Image, Logo, Avatar, QR Code, and the background image also accept a token directly (their placeholders even suggest examples like `{{user_avatar}}` and `{{post_url}}`).
- **From the Data tab** — the right panel's **Data** tab lists every token the design uses. You can **drag a token onto a text element** to bind it, reorder tokens by their grip handle, remove them with the **×** button, or click **+ New Token** to add one by key (for example `post_title`).

Each token carries a **sample value** — a placeholder used only inside the editor so you can see what the finished image will look like. Toggle the canvas between **Sample data** (shows resolved previews) and **Tokens** (shows the raw `{{...}}`) using the toolbar switch, or open **Edit Sample Values** in the top toolbar to change them.

![The right panel on the Data tab listing the template's tokens with grip handles, preview values, the × remove button, and the "+ New Token" button.](https://assets.infidesk.support/kb/inline/2026/07/UyB1QJkJiR2s8OPFvCqHKcipCiGvYD5AG2iHh6Y9.png)

The saved template stores the raw `{{tokens}}` (they are not replaced until a workflow runs) along with your sample values. That saved sample data is important: it defines which parameters appear when you later use this template in the **Generate Image from Template** workflow action, so always give each token a sensible sample value before saving.

## Previewing and saving

**Preview** opens a full-size view of the rendered design (with a **Sample data / Tokens** toggle and an Export option). **Save** writes the template to FlowMattic. The save status chip confirms each save.

Back on the **Image Templates** listing, each template's row menu lets you **Edit Template**, **Download Image** (renders the design to a PNG on demand, with an option to override sample values first), **Duplicate**, **Copy Template ID**, and **Delete Template**.

![The Preview modal showing the rendered template at full size with the Sample data / Tokens toggle](https://assets.infidesk.support/kb/inline/2026/07/EFEuAQX4jqJuKbnuNB87oPJU2nMrrofggoWFkJp4.png).

---

# Image Template Builder - Short guide

Source: https://support.flowmattic.com/kb/article/191/image-template-builder-short-how-to-guide

The Image Template Builder lets you design an image once and generate dynamic PNGs from it inside any workflow — a social card carrying each new post's title, a coupon with the customer's code, a ticket with a scannable QR.

This is the short, practical version: design a template, then wire it into a workflow. For the full reference on every element type and styling option, see [Image Template Builder](/kb/image-template-builder).

## Before you start

Image rendering runs through **Cloudflare Browser Rendering**, using **your own** Cloudflare account. Nothing will render until you add your Account ID and API token under **FlowMattic → Settings → Cloudflare Browser Rendering**. The token needs the **Browser Rendering → Edit** permission — see [Set up Cloudflare Browser Rendering](/kb/set-up-cloudflare-browser-rendering).

## Step 1: Create the template

Go to **FlowMattic → Image Templates** and create a new template. You can start from one of the **19 prebuilt starters** or from a blank canvas.

**Set your canvas size first.** The rendered PNG always comes out at exactly the template's dimensions, and the workflow action cannot override them — so choose the size now rather than redesigning later. Common ones:

- **1200 × 630** — Open Graph / link previews on most platforms
- **1080 × 1080** — square social post
- **1080 × 1920** — story / vertical

## Step 2: Design the canvas

Add elements from the **Elements** tab of the **Library** panel and style them in the inspector on the right. Ten element types are available: **heading, text, image, avatar, button, icon, shape, divider, logo and QR code**, plus gradient backgrounds and decorative accents.

Drag to position. It is worth keeping anything that will hold dynamic text a little larger than your sample data needs — a longer real value than your sample will otherwise overflow or wrap unexpectedly.

## Step 3: Add tokens for the parts that change

Anywhere the content should come from the workflow, use a `{{token}}`. Tokens work in:

- any **text** element
- the **Source** field of image, avatar and logo elements
- the **URL / Value** field of a **QR code** element

Keep keys simple and flat — `{{post_title}}`, `{{customer_name}}`, `{{coupon_code}}`. Avoid dots or nesting.

Give every token a **sample value** in the **Data** tab. Samples are used for the on-canvas preview and for test renders; real runs use whatever the workflow supplies. Make your samples realistic — a sample of "Name" tells you nothing about how a 60-character product title will actually sit in the layout.

Save the template.

## Step 4: Add the workflow step

In your workflow, add the **Image Builder → Generate Image from Template** action.

**Template** — pick your saved template. FlowMattic reads its tokens and offers them as fields automatically.

**Data mode** — two ways to supply values:

- **Parameters** (the default) — one input per token. Map data from earlier steps into each. This is the easier option and what most people want.
- **JSON** — a single field taking one JSON object, for example `{ "post_title": "Hello", "coupon_code": "SAVE20" }`. Useful when an earlier step already produces the whole object. Invalid JSON fails the step with a message naming the problem.

**Filename** — optional. Leave it empty and FlowMattic names the file after the template plus a timestamp. `.png` is appended if you leave it off.

**Destination** — where the PNG goes:

- **Media Library** (default) — a normal WordPress attachment.
- **Media Library, custom folder** — an attachment filed into a folder path you specify.
- **Browser folder** — a plain file in `uploads/flowmattic-images/`, with no attachment record. Choose this for throwaway images you do not want cluttering the Media Library.

## Step 5: Use the result in later steps

The action returns everything you need to keep going:

| Field | What it is |
|---|---|
| `url` | Public URL of the rendered PNG — the one you usually want |
| `attachment_id` | WordPress attachment ID, for setting a featured image |
| `path` | Absolute file path on the server |
| `filename` | Final filename used |
| `width` / `height` | Rendered pixel dimensions |
| `file_size` | Size in bytes |
| `template_name` | The template it came from |

So a typical follow-on step is *Set Featured Image* using `attachment_id`, or an email or social post using `url`.

## A worked example: an auto-generated social card

1. Design a 1200 × 630 template with a heading bound to `{{post_title}}`, a text element for `{{author_name}}`, and an avatar whose Source is `{{author_avatar}}`.
2. Trigger: **WordPress → Post Published**.
3. Action: **Generate Image from Template**. Pick the template, leave data mode on Parameters, and map the post title, author name and author avatar URL from the trigger.
4. Action: **Set Featured Image**, using the `attachment_id` the previous step returned.

Every published post now gets a branded card without anyone opening a design tool.

## Editing a template later

Templates are referenced by ID, so **editing a template changes every workflow that uses it** — no need to update the workflows themselves. That is usually what you want, but do bear it in mind before restyling a template that several workflows depend on.

Adding a *new* token to an existing template does mean revisiting the workflows to supply it; an unsupplied token renders empty.

## Troubleshooting

**"Template is required."** — no template was selected on the step.

**"Image template not found. It may have been deleted."** — the template the workflow points at no longer exists. Re-select a template on the step.

**Nothing renders, or the step errors on credentials.** — Cloudflare Browser Rendering is not configured, or the API token lacks the **Browser Rendering → Edit** permission. That permission scope is the single most common cause.

**"The JSON data is not valid."** — you are in JSON mode and the field is not a valid JSON object. Switch to Parameters mode if you do not specifically need JSON.

**A token comes out blank.** — the workflow did not supply that key, or the key in the step does not exactly match the one in the template. Token keys are matched exactly.

**Text overflows or wraps badly.** — real data is longer than your sample. Re-check with a realistic worst-case sample value and give the element more room.

## Related

- [Image Template Builder](/kb/image-template-builder) — the full reference
- [Add tokens and sample data to an image template](/kb/add-tokens-and-sample-data-to-an-image-template)
- [Design an image template](/kb/design-an-image-template)
- [Set up Cloudflare Browser Rendering](/kb/set-up-cloudflare-browser-rendering)

---

# IMAP Email Parser

Source: https://support.flowmattic.com/kb/article/117/imap-email-parser

Monitor email accounts and automatically trigger workflows when new emails arrive. Connect Gmail, Outlook, Yahoo, or any IMAP-compatible email service to FlowMattic and automate your email processing. Perfect for creating support tickets, processing invoices, capturing leads, and managing attachments without manual intervention.

---

## Quick Setup

### Connect Your Email Account

1. Go to **FlowMattic Settings → IMAP Email Accounts**
2. Click **Add New Account**
3. Enter your email details:
   - Account Label: Friendly name (e.g., "Support Email")
   - Host: Mail server address (e.g., `imap.gmail.com`)
   - Port: `993` for SSL or `143` for TLS
   - Username: Your email address
   - Password: Your email password (use App Password for Gmail/Outlook)
   - Encryption: SSL (recommended)
4. Click **Test Connection**
5. Click **Add Account**

![IMAP Settings ‹ FlowMattic](/storage/kb-images/e75ad0b7f4-inline.png)

### Create Workflow

1. Create new workflow
2. Select **IMAP Email Parser** as trigger
3. Choose your email account
4. Select folder to monitor (default: INBOX)
5. Choose trigger type
6. Set check frequency (recommended: 5-10 minutes)
7. Click **Save & Capture Email**

![IMAP Email Parser - Workflow example.png](/storage/kb-images/3d51472406-inline.png)

---

## Trigger Types

**Email Received**: Triggers on every new email  
**Email with Subject Contains**: Triggers when subject has specific text  
**Email from Specific Sender**: Triggers for emails from certain addresses  
**Email with Attachment**: Triggers only when emails have attachments

---

## Available Actions

### Import Attachments

Downloads email attachments and saves them to WordPress media library automatically.

**Use Cases**:
- Save invoice PDFs from vendor emails
- Store customer documents from support tickets
- Archive contract attachments from legal correspondence
- Capture lead magnets sent via email
- Backup important files received in emails

**Required Fields**:
- Email folder: Use `folder` from trigger
- Message UID: Use `uid` from trigger

**Returns for Each Attachment**:
- `media_1_id` - WordPress media library ID
- `media_1_url` - Direct file URL
- `media_1_name` - Original file name
- `media_1_type` - MIME type (e.g., application/pdf)

Additional attachments return `media_2_id`, `media_3_id`, etc. Use these IDs in subsequent workflow steps to update posts, send notifications, or process files further.

---

## Available Data

Use these fields in your workflow:

- `subject` - Email subject
- `from_email` - Sender email
- `from_name` - Sender name
- `to` - Recipient
- `body_text` - Plain text
- `body_html` - HTML version
- `date` - Date sent
- `uid` - Unique ID
- `has_attachments` - true/false
- `attachment_count` - Number of attachments

---

## Email Provider Settings

**Gmail**
- Host: `imap.gmail.com`
- Port: 993
- Encryption: SSL
- Note: Must use App Password

**Outlook**
- Host: `outlook.office365.com`
- Port: 993
- Encryption: SSL
- Note: Must use App Password

**Yahoo**
- Host: `imap.mail.yahoo.com`
- Port: 993
- Encryption: SSL

---

## Gmail Setup

1. Enable IMAP: Gmail Settings → Forwarding and POP/IMAP
2. Create App Password:
   - Google Account → Security → 2-Step Verification → App Passwords
   - Select "Mail" and your device
   - Copy generated password
3. Use App Password in FlowMattic (not regular password)

---

## Outlook Setup

1. Enable IMAP: Outlook Settings → Mail → Sync email
2. Create App Password:
   - Microsoft Account → Security → App Passwords
   - Generate new password
3. Use App Password in FlowMattic

---

## Examples

**Support Tickets**: Email received → Create ticket → Send confirmation

**Invoice Processing**: Email with invoice → Import attachment → Create record

**Lead Capture**: Contact form email → Extract data → Add to CRM

---

## Troubleshooting

**Connection Failed**
- Verify host and port
- Use App Password for Gmail/Outlook
- Check if hosting blocks IMAP
- Try disabling "Validate Certificate"

**No Emails Found**
- Ensure emails are unread
- Check emails are within 24 hours
- Verify filters aren't too restrictive

**Processing Twice**
- Enable "Mark as Read"
- Check for duplicate workflows

**Can't Import Attachments**
- Use `uid` from trigger
- Check WordPress upload permissions
- Verify file types are supported

**IMAP Extension Error**
- Contact hosting provider to enable PHP IMAP extension

---

## Settings

**Polling Frequency**: How often to check (5-10 minutes recommended)

**Mark as Read**: Marks processed emails as read

**Email Folder**: Which folder to monitor

---

## How It Works

1. Checks email at set intervals
2. Remembers last processed email
3. Only processes new emails
4. Processes oldest first
5. Never deletes emails

---

## Security

- Use App Passwords
- Enable SSL/TLS
- Use dedicated email accounts
- Review accounts regularly

---

## FAQ

**How often should I check for emails?**  
We recommend checking every 5-10 minutes to balance server load and timely processing. More frequent checks may impact your email provider's rate limits. You can adjust the schedule based on your needs - urgent emails can use 5-minute intervals, while non-critical monitoring can use 15-30 minutes.

**Can I monitor multiple email accounts?**  
Yes, you can add unlimited email accounts. Each account is stored separately with its own credentials. Create separate workflows for each account based on your trigger event requirements - for example, one workflow for support emails and another for sales notifications.

**Does FlowMattic delete emails from my server?**  
No, all emails remain on your mail server. FlowMattic only reads emails without modifying them. You have the option to mark emails as read if needed to avoid duplicate processing, but this is optional. Your original emails stay intact and accessible through your regular email client.

**Can I monitor multiple folders in the same account?**  
Yes, but you'll need one workflow per folder. Each workflow can monitor a different folder (INBOX, Sent, Custom folders, etc.). This gives you flexibility to process different folders with different actions - for example, monitoring INBOX for support tickets and a "Orders" folder for purchase notifications.

**Is my email password secure?**  
Yes, all credentials are encrypted and stored securely in your WordPress database. Passwords are never exposed in workflow data or logs. We recommend using App Passwords (for Gmail/Outlook) instead of your main account password for additional security.

**How do I use this with 2FA-enabled accounts?**  
For accounts with two-factor authentication (Gmail, Outlook, Yahoo), you must generate an App Password. Regular passwords won't work with IMAP when 2FA is enabled. See the Gmail/Outlook/Yahoo setup guides above for step-by-step App Password generation instructions.

---

# Import a CSV into FlowMattic Tables

Source: https://support.flowmattic.com/kb/article/208/import-a-csv-into-flowmattic-tables

Already have data in a spreadsheet? The CSV importer creates a table, detects each column's type, and inserts your rows in fast, fault-tolerant batches.

## Step 1 — Open the importer

On the **FlowMattic → FlowMattic Tables** dashboard, click **Import CSV**, then drag your file in (or click to browse). Files up to 20 MB are supported, including quoted fields, embedded commas, and multi-line values:

![Import from CSV — drag and drop](https://assets.infidesk.support/products/flowmattic/kb-images/tables/08-import-drop.png)

## Step 2 — Confirm names and types

FlowMattic reads your file and proposes a field name and type for every column, with a sample value beside each so you can sanity-check at a glance:

![Field mapping — auto-detected types with samples](https://assets.infidesk.support/products/flowmattic/kb-images/tables/09-import-mapping.png)

The type detection understands real-world data:

| Your data looks like | Detected type |
| --- | --- |
| `yes / no`, `true / false`, `checked / unchecked` | **Checkbox** — values are stored as real booleans |
| A few short labels repeating across rows (e.g. `Starter`, `Pro`, `Business`) | **Dropdown** — seeded with the actual values found in your file |
| `49.99` | **Decimal** |
| `2026-01-14`, `14/01/2026`, `Jan 5, 2026` | **Date** (day/month order is detected per column) |
| `name@example.com` | **Email** |
| `https://example.com` | **URL** (bare domains get `https://` added automatically) |

For **Dropdown** columns, click the options button beside the type to review the detected options — rename them or change their colors in the options editor. If a guess is ever wrong, just switch the type back to **Text**.

## Step 3 — Run the import

Click **Proceed**. FlowMattic creates the table, adds the columns, and inserts your rows in adaptive batches — batch size starts safe and grows up to 1,000 rows per request while your connection keeps up.

Large imports are built to survive hiccups:

- A failed batch is **retried automatically** (up to three attempts with backoff), and the importer re-checks the table's actual row count before each retry so nothing is ever duplicated.
- If the import still can't continue, you'll see the real reason and a **Resume import** button that picks up exactly where the data stopped — no starting over.

> **Writes and your plan:** every imported row counts as one write. The mapping screen warns you up front if the file needs more writes or records than your plan has left this month.

## Optional — Run workflows for each row

The mapping screen includes a **Run workflows for each imported row** switch (off by default). Turn it on only if you want your *New Row* triggers to fire for every imported record — for large files that means one workflow run per row.

---

# Import Actions into Custom Apps from cURL, OpenAPI, Swagger, or Postman

Source: https://support.flowmattic.com/kb/article/162/import-actions-into-custom-apps-from-curl-openapi-swagger-or-postman

FlowMattic can read an API definition and turn it into ready-to-use Custom App **actions** for you, so you don't have to type out every endpoint, parameter, and header by hand. You give it a cURL command, an OpenAPI 3.x spec, a Swagger 2.0 spec, or a Postman 2.1 collection, and FlowMattic parses it, shows you every action it found, lets you pick which ones to keep, and then either creates a brand-new Custom App or adds the actions to one you already have.

## What this feature is

A Custom App in FlowMattic is your own integration: a set of HTTP **actions** that workflows can call. Normally you'd build each action one at a time, filling in the HTTP method, the URL, and every parameter. The import feature short-cuts that. It understands four common ways APIs are described and converts each operation it finds into a complete FlowMattic action with the method, URL, path/query/header parameters, and request body already filled in.

The four supported formats are:

- **From cURL** — a single `curl ...` command copied from an API's documentation. This builds one action.
- **From OpenAPI spec** — an OpenAPI 3.x definition (JSON or YAML). Every operation in the spec becomes an action.
- **From Swagger 2.0** — the older Swagger 2.x specification format (JSON or YAML).
- **From Postman collection** — a Postman 2.1 collection export (JSON). Every saved request becomes an action.

![custom-apps-import-app-button](https://assets.infidesk.support/kb/inline/2026/07/28LnJ1OusKONxXDZgbqhb7NNJmMhyBWtSIfl86Tq.png)

## Where to start the import

There are two places to begin, depending on whether you want a new app or want to add to an existing one.

### Creating a new Custom App from an import

Go to the **Custom Apps** page in the FlowMattic admin. In the page header, click the **Import App** button. A dropdown opens with these choices:

- **From cURL** — "Paste a curl command from any API docs"
- **From OpenAPI spec** — "OpenAPI 3.x JSON or YAML file"
- **From Swagger 2.0** — "Legacy Swagger 2.x specification"
- **From Postman collection** — "Postman 2.1 export JSON"
- **From App JSON** — this is the separate FlowMattic-native export/restore format, not a spec import

Pick the format that matches what you have. (The **Import App** button is disabled until your FlowMattic license is registered.)

![The "Import App" dropdown open, showing From cURL / From OpenAPI spec / From Swagger 2.0 / From Postman collection / From App JSON](https://assets.infidesk.support/kb/inline/2026/07/h85iPGEDM7QRHXuulh4Fyg6R3argwPgCPRcZuXKZ.png)

### Adding actions to an existing Custom App

Open the app you want to add to, then go to its **Actions** tab. In the header there you'll find an **Import Actions** button with the same four format choices (From cURL, From OpenAPI spec, From Swagger 2.0, From Postman collection). Using this entry point imports straight into the app you're already editing instead of creating a new one.

![The Actions tab of a Custom App showing the "Import Actions" button beside "Create New Action"](https://assets.infidesk.support/kb/inline/2026/07/lXLbWKoKI0wHVfKH6sJNWgVyqeZuvFals5089WRF.png)

## The import window

Whichever format and entry point you choose, the same **Import from [format]** window opens. It works in two steps: first you give it the spec, then you preview and confirm.

### Step 1 — Provide the spec

At the top of the window are three source tabs. Pick how you want to hand the spec over:

- **Paste text** — A large text box where you paste the raw cURL command or spec. A live character counter sits below it. This is the only source available for cURL imports.
- **Upload file** — A drag-and-drop zone labeled "Click to choose a file or drag and drop." It accepts **JSON or YAML** files (`.json`, `.yaml`, `.yml`) **up to 5 MB**. Drop a file or click to browse; FlowMattic reads the file's contents into the import. (Not shown for cURL.)
- **Fetch from URL** — A URL field (for example `https://api.example.com/openapi.yaml`). FlowMattic fetches the spec over HTTPS for you — JSON or YAML, up to 5 MB. The remote fetch follows up to a few redirects and times out after about 20 seconds. (Not shown for cURL.)

FlowMattic reads JSON first and falls back to YAML when the content isn't JSON, so either format works for the OpenAPI, Swagger, and Postman importers.

When your input is ready, click **Parse**. FlowMattic processes the spec and moves you to the preview step. If the input is empty or can't be parsed, you'll see a clear error and stay on this step.

![The import window's input step with the Paste text / Upload file / Fetch from URL tabs and the paste area](https://assets.infidesk.support/kb/inline/2026/07/vhgkWUUy9XhHLjS5ajp4yFC8amZvPyt85dHxhNXr.png)

## Step 2 — Preview and select the actions

After parsing, the window shows everything FlowMattic discovered so you can review before committing.

### The summary and the actions table

A summary line reads **"N actions found,"** and if any actions have issues it adds **"· N need attention."** Below that is a table of every discovered action with these columns:

- A checkbox (with a **select-all** checkbox in the header — everything starts checked).
- **Method** — the HTTP method, color-coded (GET, POST, PUT, PATCH, DELETE).
- **Name & Path** — the action name and the endpoint URL beneath it.
- **Params** — a badge counting how many parameters the action has.

Click any **row** to toggle whether that action will be imported (clicking the row toggles its checkbox). Uncheck the ones you don't want. The primary button at the bottom updates its label to match your selection — for a new app it reads **"Create App with N actions,"** and when adding to an existing app it reads **"Import N actions."**

![he preview step showing the "N actions found" summary and the actions table with Method, Name & Path, and Params columns](https://assets.infidesk.support/kb/inline/2026/07/zgWLaUTXB5Ajj3Sl0pQOLXfp91UF4Oi2lh3jUORL.png)

### Auth notice and warnings

If FlowMattic detects an authentication scheme (a bearer token, basic auth, or an API key in cURL; security schemes in OpenAPI/Swagger; auth in Postman), it shows an info banner telling you what it found and that you should **configure auth on the App Settings page**. The import does not set up the connection for you — it only flags it. A "Heads-up" note reminds you to open **App Settings** to set the default **Connect**, and to open each action to review its parameters before using them in workflows.

Some actions can also carry their own warnings (shown as a small pill on the row, with a "Show N warnings" toggle). The most common one is that an endpoint URL is missing its host or still contains a placeholder — which the **Base URL** option below can fix.

### The Base URL option

Some specs describe paths without a full address (for example just `/v1/users`) or use a placeholder host. When FlowMattic notices this, a highlighted **Base URL** panel appears showing how many actions are affected ("(N affected)"). Enter a full base URL like `https://api.example.com`, and FlowMattic substitutes it into every affected endpoint. A live **"Example after apply"** preview shows you exactly how one URL will look once the base is applied, and the URLs in the table update as you type. Actions that already have a complete `https://` address are left untouched.

## Choosing a new app vs. adding to an existing app

What you see at the bottom of the preview step depends on how you started the import.

### New app

If you began from the **Import App** button on the Custom Apps page, you'll see an **App Name** field. Type the name for the new app (FlowMattic pre-fills a sensible default like "OpenAPI App" or "Postman App" based on the format). When you click the create button, FlowMattic creates the new Custom App, adds all your selected actions to it, and redirects you to that app's Actions tab.

### Append to an existing app

If you began from the **Import Actions** button inside an app, the App Name field is hidden (the target app is already chosen) and an **On conflict** control appears instead. This is where duplicate handling comes in.


## How skip / duplicate handling works

Duplicate handling only applies when you're **adding actions to an existing app**, because that's the only time an imported action name could clash with one already there. FlowMattic compares names case-insensitively and uses the **On conflict** toggle to decide what to do:

- **Skip existing** (the default) — If an imported action has the same name as an action already in the app, it's dropped and not imported. After importing, the success message tells you how many were imported and how many were skipped.
- **Create duplicate** — Both are kept. The newly imported action's name gets a numeric suffix (for example "Get User (2)"), and the number increases until the name is unique, so nothing gets overwritten.

When creating a brand-new app there's nothing to conflict with, so every selected action is imported and the skip count is zero.

After the import finishes you'll see a confirmation such as "N action(s) imported" (with "(N skipped)" if any were skipped), and FlowMattic takes you to the app so you can review the results.

![The preview footer for a new app (App Name field) versus appending (On conflict toggle)](https://assets.infidesk.support/kb/inline/2026/07/y0Rs9mnrqfvCL1AtdocHOM14yBEsQJKVqcBIvAjf.png)

## What gets auto-filled in each action

For every action it creates, FlowMattic fills in the same fields you'd otherwise enter by hand in the action editor:

- **Action Name** and **Description** — taken from the operation's name/summary and description (the description is trimmed to fit).
- **HTTP method** — GET, POST, PUT, PATCH, or DELETE. (If a spec uses an unsupported method, FlowMattic falls back to GET.)
- **Endpoint URL** — built from the spec. For OpenAPI it uses the first **server** URL plus the path; for Swagger it combines the scheme, host, and basePath; for Postman it uses the request URL. Path placeholders like `{id}` are converted to FlowMattic's `{{id}}` format.
- **Content type** — detected from the request's `Content-Type` header (JSON, form-encoded, multipart form data, XML, HTML, or plain text), defaulting to JSON.

It also turns the spec's parameters into the action's parameter rows, sorted by where each one belongs:

- **Path and query parameters** — added as action parameters and marked as path/URL variables so they slot into the endpoint URL and query string. Path parameters are treated as required.
- **Header parameters** — added under the action's headers, including any static header values from a cURL command (the `Content-Type` header is handled separately by the content-type setting).
- **Body parameters** — added as parameters and used to build the request body. For JSON bodies, FlowMattic reconstructs the nested body shape, expanding object properties into dotted names (like `user.address.street`) so structured payloads work out of the box. For a cURL command with a JSON body, it preserves your original body structure and replaces the values with `{{placeholder}}` tokens.

Each parameter also carries over its **field label** (made readable from the name), **field type** (text/number/boolean — arrays and objects come in as text), **required** flag, **help text** (from the spec's description), and any **default value**.

Because everything is dropped into the standard action fields, you can open any imported action afterward and edit it exactly like one you built manually. Remember to set the app's **Connect** and authentication in **App Settings** before running these actions in a workflow — the import fills in the request details, not the credentials.

---

# Import CSV Data into an Existing Table (WP Tables & FlowMattic Tables)

Source: https://support.flowmattic.com/kb/article/233/import-csv-data-existing-table

Already have a table full of data and a CSV full of new rows? You don't need to rebuild anything — both **WP Tables** and **FlowMattic Tables** let you import a CSV file straight into an existing table. Upload the file, map its columns to your table's columns, and the rows are appended to whatever is already there.

This guide walks through the import flow in both table types.

> **Tip:** If you want to create a *brand-new* table from a CSV instead, both table types support that too — this article covers adding data to a table that already exists.

## Which one are you using?

- **WP Tables** — tables stored in your own WordPress database. Managed under **FlowMattic → WP Tables**.
- **FlowMattic Tables** — managed database tables hosted on our infrastructure, with usage-based plans. Managed under **FlowMattic → Databases**.

The import experience is the same in spirit for both: **Upload → Map columns → Import**, with automatic column matching and batched processing that can handle large files without timing out.

## Import CSV data into a WP Table

1. Go to **FlowMattic → WP Tables** and open the table you want to add data to.
2. Click **Import CSV** in the top toolbar.

![Import CSV button in the WP Tables toolbar](https://assets.infidesk.support/kb/inline/2026/07/rJNEJGa4vM4in99VLFzs1d5pqQYfU19cragsSFMD.png)

3. Drag and drop your CSV file onto the upload area, or click **Browse Files** to pick it from your computer.

![Upload step of the Import CSV Data modal](https://assets.infidesk.support/products/flowmattic/kb-images/csv-import-existing-table/wp-import-upload.png)

4. On the **Map columns** step, match each CSV column to a table column. Columns with similar names are matched automatically — in the example below, all five columns were mapped without any manual work. Anything left unmapped is simply skipped.

![Column mapping with automatic matching](https://assets.infidesk.support/products/flowmattic/kb-images/csv-import-existing-table/wp-import-mapping.png)

5. The **Review & import** step shows how many rows will be imported, how many columns are mapped, and a preview of the first rows — so you can confirm the data lines up before anything is written.

![Review step with row preview before importing](https://assets.infidesk.support/products/flowmattic/kb-images/csv-import-existing-table/wp-import-review.png)

6. Click **Import data**. Large files are processed in batches automatically to prevent timeouts — keep the browser tab open until the import completes.

## Import CSV data into a FlowMattic Table

*Requires FlowMattic 7.1.0 or later.*

1. Go to **FlowMattic → Databases**. In your tables list, open the actions menu (⋮) for the table and choose **Import CSV Data**.

![Import CSV Data in the table actions menu](https://assets.infidesk.support/products/flowmattic/kb-images/csv-import-existing-table/fmt-import-menu.png)

You can also start an import while viewing a table's records — the **Import CSV** button sits right next to Share:

![Import CSV button in the table records view](https://assets.infidesk.support/products/flowmattic/kb-images/csv-import-existing-table/fmt-grid-import-button.png)

2. Drag and drop your CSV (up to 20 MB), or click to browse.

![Upload stage of the FlowMattic Tables import](https://assets.infidesk.support/products/flowmattic/kb-images/csv-import-existing-table/fmt-import-upload.png)

3. Map your CSV columns onto the table's existing fields. Matching column names are pre-selected automatically, and each row shows a live sample value from your file so you can sanity-check the mapping at a glance. Fields marked with * are required and must be mapped; computed fields (like Calculate or Created By) can't receive imported values, so they don't appear in the list.

![Mapping CSV columns onto existing table fields](https://assets.infidesk.support/products/flowmattic/kb-images/csv-import-existing-table/fmt-import-mapping.png)

The header cards show the rows in your file, the CSV columns detected, and the rows already in the table — imported rows are **appended**, never overwriting existing data.

4. Optional: turn on **Run workflows for each imported row** if you want your New Row triggers to fire for every imported record. It's off by default, because a large file can start a lot of workflow runs at once.

5. Click **Import Data**. Rows are inserted in batches with live progress. If your connection hiccups mid-import, use the **Resume import** button — the import picks up exactly where it stopped, without duplicating rows.

![Import complete confirmation](https://assets.infidesk.support/products/flowmattic/kb-images/csv-import-existing-table/fmt-import-success.png)

That's it — click **View your table** to see the new rows alongside your existing data.

## Good to know

- **Values are converted to match field types.** Dates, numbers, booleans, emails and URLs in your CSV are converted to the field's type automatically. A value that can't be converted is left empty for that field rather than failing the whole import.
- **Only mapped columns are imported.** Extra columns in your CSV are ignored — no need to clean the file first.
- **FlowMattic Tables plan usage:** each imported row counts as one write and one record toward your plan. If the file would exceed what's remaining, the import screen warns you before anything runs.
- **Large files:** both importers insert in batches sized to keep requests fast, so files with thousands of rows import reliably. Keep the tab open until you see the completion message.

## Troubleshooting

- **A column didn't auto-match** — pick it manually from the dropdown; matching compares names ignoring case, spaces and punctuation.
- **Some cells came in empty** — the value likely didn't fit the field type (for example, text in a number field). Fix the CSV values or map that column to a text field instead.
- **The import stopped partway** — click **Resume import**. The importer re-checks the table's row count first, so resuming never creates duplicates.

---

# Including HTTP Response Headers in Your API Action Output

Source: https://support.flowmattic.com/kb/article/166/including-http-response-headers-in-your-api-action-output

The **API by FlowMattic** action lets you call any external API from inside a workflow. By default it gives you back only the response body. When you turn on **Show Response Headers**, the action also includes the HTTP response headers in its output under a **response_headers** key, so you can read values that the API sends in headers instead of the body.

## What HTTP response headers are

Every time an API answers a request, it sends back two things: the **body** (the main data, usually JSON) and the **headers** (small pieces of metadata about the response). Headers carry useful things like:

- Authentication tokens (for example, a refreshed access token)
- Pagination cursors that tell you how to fetch the next page of results
- Rate-limit information, such as how many requests you have left
- Content type, request IDs, and other technical details

Normally FlowMattic only passes the body forward to your next workflow steps. The headers are invisible. The **Show Response Headers** option makes them visible so you can use them.

## Where the option lives

The option is part of the **API by FlowMattic** action settings, which is an **action** app (it runs as a step inside a workflow, not as a trigger).

When you add or edit an **API by FlowMattic** step, scroll down through the action settings. You will pass the **Response Format** section, and just below it you will see the **Show Response Headers** section. Below that is the **Error Handling** section.

![settings-section](https://assets.infidesk.support/kb/inline/2026/07/FBp8LLoeYkl3pLxEPV6e3w4DBXOs478ZvBKddTT9.png)

### The toggle

**Show Response Headers** is a dropdown with two choices:

- **No** — the default. The action returns only the response body.
- **Yes** — the action also captures the response headers and adds them to the output.

The help text under the dropdown reads:

> When enabled, the response headers returned by the API will be available in the response under the "response_headers" key. Useful for APIs that return tokens or metadata in headers.

To enable it, set the dropdown to **Yes** and save the step.

![dropdown-options](https://assets.infidesk.support/kb/inline/2026/07/0wrSPzQgB7PIyFiflyJDKffVQtp9JiNAsJE0DTrK.png)


## What turning it on does to the action output

When **Show Response Headers** is set to **No**, the action output is just the body returned by the API.

When it is set to **Yes**, FlowMattic captures the headers from the API's response and adds a single extra key called **response_headers** alongside your normal response data. Your original response body is untouched; the headers are simply added next to it.

For example, an API response that normally looks like this:

```json
{
  "id": 12345,
  "status": "active"
}
```

will, with **Show Response Headers** turned on, look like this:

```json
{
  "id": 12345,
  "status": "active",
  "response_headers": {
    "Content-Type": "application/json",
    "X-RateLimit-Remaining": "98",
    "X-Next-Cursor": "eyJwYWdlIjoy",
    "Authorization": "Bearer abc123"
  }
}
```

If the API returns a plain list or a non-object response, FlowMattic wraps it so nothing is lost. In that case the body is placed under a **response** key and the headers under **response_headers**:

```json
{
  "response": [ ... original list ... ],
  "response_headers": { ... }
}
```

This wrapping only happens when the original response is not a standard object, so your existing data stays in a predictable shape.

## The shape of response_headers

**response_headers** is a simple map (an object) of **header name → header value**. Each key is the name of a header exactly as the API sent it (for example, `Content-Type` or `X-RateLimit-Remaining`), and each value is that header's value as a single string.

A few details worth knowing:

- **Values are always text.** Even numeric-looking values like `X-RateLimit-Remaining` come through as strings.
- **Repeated headers are joined.** If an API sends the same header more than once, FlowMattic combines the values into one string separated by a comma and a space (for example, two `Set-Cookie` values become `value1, value2`).
- **Header names keep the API's original casing.** Look at a test run to see the exact name a given API uses before relying on it.

Because the exact header names depend on the API you are calling, the best way to see what you will get is to run a test of the step (described below).

## How it works end to end

You do not need to do anything beyond flipping the toggle. Behind the scenes, FlowMattic adjusts how it reads the response so the headers are available:

1. You set **Show Response Headers** to **Yes** and save the step.
2. When the workflow runs the step, FlowMattic makes the API request as usual.
3. It reads the headers that come back with the response and turns them into a clean name → value map.
4. It adds that map to the action output under the **response_headers** key, right next to your normal response data.

This works across the different request methods the API action supports (**GET**, **POST**, **PUT**, **DELETE**, **PATCH**), so the headers are captured no matter which method your step uses.

## How to use header values in later steps

Once **Show Response Headers** is on, the **response_headers** values become available in the FlowMattic data picker just like any other output field from the step, so later steps can read them.

The recommended flow:

1. With **Show Response Headers** set to **Yes**, run a **test** of the API step (or run the workflow once) so FlowMattic captures real sample data, including the headers.
2. In a later step, open the field where you want to use a header value and use the **data picker** to browse the API step's output.
3. Find the **response_headers** group and pick the specific header you need (for example, `X-Next-Cursor` or a refreshed token). FlowMattic inserts a reference to that value into the field.

![The data picker showing the API step's output with the response_headers group expanded and a header value selected for mapping into a later step](https://assets.infidesk.support/kb/inline/2026/07/EVBAfLTtLkVva7VgenvGMBspfY8iWRUqMJtPX8V2.png)

From there you can use the captured header value anywhere a later step accepts mapped data, for example:

- Pass a refreshed **token** from the headers into the authorization field of a following API step.
- Feed a **pagination cursor** (such as a "next page" token from the headers) back into a follow-up API call to fetch the next page.
- Send **rate-limit** values into a condition or a notification so your workflow can react when you are running low on requests.

Because the headers arrive as part of the step's normal output, they behave exactly like the body fields you already map: capture them once with a test run, then pick them wherever you need them.

---

# Installing FlowMattic

Source: https://support.flowmattic.com/kb/article/3/installing-flowmattic

Once you made the purchase, you'll be presented the link to download the plugin on your purchase confirmation page. You can also download the plugin by visiting the account page on FlowMattic website. Download the plugin and follow these instructions to install the plugin on your site.

There are basically two ways to install the plugin on your site.

### Installing Through Dashboard

1. Go to Plugins&nbsp;→ Add New&nbsp;→ Upload

3. Choose the installable ZIP file that you have download in your computer from our website. Upload that file.

5. Now, click on activate link to activate the plugin.

### Installing Through FTP

1. Login to your site FTP using any FTP software like FileZilla etc.

3. Extract the installable ZIP file that you have download in your computer from our website. Upload the extracted folder into wp-content/plugins directory.

5. Activate the plugin through the 'Plugins' menu in WordPress.

Once the plugin is activated, go to the FlowMattic admin dashboard and enter your license key to activate the product. A valid license key is required to download the integrations. To obtain the license key, visit the account page on our website, and switch to the license tab.

---

# Installing Node.js for Claude Desktop MCP Usage

Source: https://support.flowmattic.com/kb/article/86/installing-nodejs-for-claude-desktop-mcp-usage

## Introduction

Node.js is a JavaScript runtime environment that's required to run Model Context Protocol (MCP) servers with Claude Desktop. MCP allows Claude Desktop to connect to external tools and data sources, greatly extending its capabilities. This guide will walk you through installing Node.js on both Mac and Windows systems.

## What You'll Need

- A Mac or Windows computer
- Administrator privileges on your system
- Internet connection for downloading Node.js

## Installation Instructions

### For Mac Users

#### Method 1: Using the Official Installer (Recommended)

1. **Visit the Node.js website**
   - Go to [nodejs.org](https://nodejs.org)
   - Click on the **LTS** (Long Term Support) version download button
   - This will download a `.pkg` file for macOS

2. **Run the installer**
   - Locate the downloaded `.pkg` file in your Downloads folder
   - Double-click the installer to launch it
   - Follow the installation wizard:
     - Click "Continue" through the introduction screens
     - Accept the license agreement
     - Choose the installation location (default is recommended)
     - Click "Install" and enter your admin password when prompted

3. **Verify the installation**
   - Open Terminal (Press `Cmd + Space`, type "Terminal", and press Enter)
   - Type the following commands to verify Node.js and npm are installed:
   ```bash
   node --version
   npm --version
   ```
   - You should see version numbers for both commands

#### Method 2: Using Homebrew (For Advanced Users)

If you have Homebrew installed:

1. **Open Terminal**
2. **Install Node.js using Homebrew**
   ```bash
   brew install node
   ```
3. **Verify the installation**
   ```bash
   node --version
   npm --version
   ```

### For Windows Users

#### Method 1: Using the Official Installer (Recommended)

1. **Visit the Node.js website**
   - Go to [nodejs.org](https://nodejs.org)
   - Click on the **LTS** (Long Term Support) version download button
   - This will download a `.msi` file for Windows

2. **Run the installer**
   - Locate the downloaded `.msi` file in your Downloads folder
   - Double-click the installer to launch it
   - Follow the installation wizard:
     - Click "Next" through the welcome screen
     - Accept the license agreement
     - Choose the installation path (default is recommended: `C:\Program Files\nodejs\`)
     - **Important**: Make sure "Add to PATH" is checked (this is usually enabled by default)
     - Click "Install" and allow the installer to make changes when prompted

3. **Restart your computer** (recommended to ensure PATH changes take effect)

4. **Verify the installation**
   - Open Command Prompt or PowerShell:
     - Press `Win + R`, type `cmd`, and press Enter (for Command Prompt)
     - Or press `Win + X` and select "Windows PowerShell" (for PowerShell)
   - Type the following commands:
   ```cmd
   node --version
   npm --version
   ```
   - You should see version numbers for both commands

#### Method 2: Using Chocolatey (For Advanced Users)

If you have Chocolatey package manager installed:

1. **Open PowerShell as Administrator**
2. **Install Node.js using Chocolatey**
   ```powershell
   choco install nodejs
   ```
3. **Verify the installation**
   ```powershell
   node --version
   npm --version
   ```

## Recommended Node.js Version

For Claude Desktop MCP usage, it's recommended to use:
- **Node.js 18.x LTS** or newer
- The LTS (Long Term Support) version is more stable and recommended for most users

## Verifying Your Installation

After installation, verify that everything is working correctly:

### Check Node.js and npm versions
```bash
node --version
npm --version
```

### Test Node.js functionality
Create a simple test file to ensure Node.js is working:

1. Create a new file called `test.js` with the following content:
   ```javascript
   console.log("Node.js is working correctly!");
   console.log("Node.js version:", process.version);
   ```

2. Run the file:
   ```bash
   node test.js
   ```

3. You should see the output confirming Node.js is working.

## Troubleshooting Common Issues

### Mac Troubleshooting

**Issue**: Command not found after installation
- **Solution**: Restart Terminal or run `source ~/.bash_profile` or `source ~/.zshrc`
- **Alternative**: Check if Node.js is in your PATH by running `echo $PATH`

**Issue**: Permission errors when installing packages globally
- **Solution**: Use `sudo` prefix or configure npm to use a different directory for global packages

### Windows Troubleshooting

**Issue**: 'node' is not recognized as an internal or external command
- **Solution**: 
  1. Restart Command Prompt or PowerShell
  2. Restart your computer
  3. Check if Node.js is in your PATH:
     - Open System Properties → Advanced → Environment Variables
     - Look for `C:\Program Files\nodejs\` in the PATH variable

**Issue**: Permission errors
- **Solution**: Run Command Prompt or PowerShell as Administrator

### General Troubleshooting

**Issue**: Installation fails or Node.js doesn't work
- **Solution**: 
  1. Uninstall Node.js completely
  2. Download the latest LTS version from the official website
  3. Run the installer as Administrator (Windows) or with sudo (Mac if needed)

## Next Steps

Once Node.js is successfully installed, you can:

1. **Configure Claude Desktop MCP**: Follow Claude Desktop's documentation to set up MCP servers
2. **Install MCP packages**: Use npm to install specific MCP server packages as needed
3. **Create custom MCP servers**: Develop your own MCP servers using Node.js

## Additional Resources

- [Official Node.js Documentation](https://nodejs.org/docs/)
- [npm Documentation](https://docs.npmjs.com/)
- [Claude Desktop MCP Documentation](https://docs.anthropic.com/) (for specific MCP setup instructions)

## Summary

You now have Node.js installed and ready for use with Claude Desktop's MCP functionality. The installation provides you with both Node.js (the runtime) and npm (the package manager), which are essential for running and managing MCP servers. If you encounter any issues, refer to the troubleshooting section above or consult the official Node.js documentation.

---

# Iterator End

Source: https://support.flowmattic.com/kb/article/19/iterator-end

Iterator End is an action module in FlowMattic - a workflow automation tool, that allows the user to end the execution of an iterator in a workflow. Iterators are used in workflows to loop through a given JSON array, process each individual item in the array, and map the data with subsequent steps in a workflow, and Iterator End is used to mark the end of the iteration process.

Once the iterator has completed its execution, the subsequent steps in the workflow are then executed. The Iterator End feature ensures that the workflow does not continue with its subsequent steps until the iteration process is complete.&nbsp;

To learn more about the Iterator Module, [click here](https://support.flowmattic.com/kb/article/17/iterator-module/ "Iterator Module").

## When to use Iterator End?

You don't always need to use the Iterator End module, even if you're using the Iterator within your workflow. Here's why -

The Iterator End module is required only when you want to execute some action steps after the Iteration process is completed. When you have no actions to perform after the iteration is done, you don't need to use the Iterator End.

---

# Iterator Module

Source: https://support.flowmattic.com/kb/article/17/iterator-module

#### Detailed Guide to FlowMattic Iterator Module

The **FlowMattic Iterator Module** is a core feature that helps users loop through a given JSON array, process each individual item in the array, and map the data with subsequent steps in a workflow. This is particularly useful when handling multiple similar data items, like a list of orders, product details, or any repeated data within a JSON structure.

Below is a detailed guide explaining what the FlowMattic Iterator is, how it works, and when you should use it, followed by a real-world example.

* * *

### What is the FlowMattic Iterator?

The **FlowMattic Iterator** is a module designed to handle JSON arrays in a workflow. It allows you to:

- Loop through each item in a JSON array.

- Extract individual items one by one.

- Use the data of the extracted item to map it to subsequent steps in the workflow.

The Iterator works in two parts:

1. **Iterator (Start)**: The module where looping through the JSON array begins. This is where the first item from the array is processed in test mode.

3. **Iterator End**: The module that marks the end of the iteration loop. All steps between the Iterator and Iterator End will be repeated for each item in the array.

* * *

### How Does the FlowMattic Iterator Work?

#### Step-by-Step Process:

1. **Add the Iterator to Your Workflow**

- In your workflow, drag and drop the **Iterator** module where you need to process a JSON array. This should be placed after the trigger step (e.g., receiving JSON data from an API or webhook).

1. **Input the JSON Array**

- In the Iterator configuration, map the JSON array you want to loop through. This could be an array of objects received from the previous workflow step, such as a list of orders, contacts, or products.

1. **Save and Test Action**

- After mapping the JSON array, click on the **Save and Test Action** button.

- When testing, FlowMattic will return the **first item** of the array as a response. This allows you to map the fields of the first item with the rest of the workflow steps. For example, if you are looping through a list of orders, you can map details like `order ID`, `customer name`, and `order total`.

1. **Add Steps After the Iterator**

- Now, add any additional steps that should be repeated for each item in the JSON array. These could include actions like sending an email, updating a database, or triggering another service.

- The values from the first item in the JSON array will be used in these steps during testing.

1. **Add the Iterator End Module**

- To mark the end of the loop, add the **Iterator End** module after the steps you want to iterate. This tells FlowMattic when to stop repeating the steps for each item in the array.

1. **Execution in Live Mode**

- When the workflow is executed in live mode, FlowMattic will loop through the entire JSON array. Each item will be processed individually, and the steps between the Iterator and Iterator End will be repeated for each one.

- The entire workflow continues beyond the Iterator End once the looping completes.

* * *

### Example Use Case: Processing a List of Orders

#### Scenario:

You receive a webhook with a JSON array containing a list of customer orders. The JSON data looks like this:

```
{
  "orders": [
    {
      "order_id": "1001",
      "customer_name": "John Doe",
      "total": "$150"
    },
    {
      "order_id": "1002",
      "customer_name": "Jane Smith",
      "total": "$200"
    }
  ]
}
```

#### Workflow Steps:

1. **Webhook Trigger**: Receive the JSON array containing the list of orders via a webhook.

3. **Iterator Module**: Place the Iterator after the webhook trigger and map the `orders` array to the Iterator module.

5. **Save and Test**: FlowMattic will display the first order (John Doe) during testing. You can map fields like `order_id`, `customer_name`, and `total` to further actions.

7. **Action Step 1**: Add an action to send an email confirming the order. Map the data fields from the first item (John Doe) into the email content.

9. **Iterator End**: Add the Iterator End module after the email action to mark the end of the loop.

11. **Live Execution**: Once live, FlowMattic will loop through the array and process each order individually. First, it will handle John Doe's order, and then repeat the same steps for Jane Smith's order.

* * *

### When to Use the FlowMattic Iterator?

The Iterator is useful in situations where you need to process multiple similar data items, such as:

- Handling **bulk orders** received from an e-commerce system.

- Processing a **list of subscribers** in an email marketing tool.

- Looping through a **collection of products** or **inventory items**.

- Iterating through a **set of API responses** with repeated data, such as a list of tasks, users, or transactions.

By using the Iterator, you eliminate the need to manually process each item in the array and automate repetitive tasks efficiently.

* * *

### Key Takeaways:

- **The Iterator** is crucial for looping through and processing JSON arrays.

- **Save and Test Action** only processes the first item, allowing you to map fields to subsequent steps.

- In live execution, the **Iterator automatically loops** through all items in the JSON array, performing each step for every item between the Iterator and Iterator End.

- Ideal for processing lists, bulk data, or any repeated elements within a JSON structure.

The Iterator simplifies your workflows by automating the processing of multiple items without manually handling each one, improving efficiency and scalability.

If you need further clarification or a specific example, feel free to ask!

Iterator Storage and Iterator End are two additional modules that can be used in conjunction with the Iterator module in the FlowMattic application. These modules are different in nature and have different functions.

**Iterator Storage:** The Iterator Storage module is used to store the values from the Iterator in an array or string to use it outside the Iterator action step. When using the Iterator module, it may be necessary to save the values generated by the Iterator and use them later in the workflow. This is where the Iterator Storage module comes into play. This module allows users to store the values generated by the Iterator in an array or string, which can be accessed and used later in the workflow. This provides greater flexibility and functionality to the workflow, allowing users to perform more complex actions.

**Iterator End:** The Iterator End module is used to stop the Iterator process where this action step is inserted and only let the Iterator loop through the action steps between the Iterator and Iterator End modules. When using the Iterator module, it is necessary to define the end of the loop. This is where the Iterator End module comes into play. This module is used to indicate the end of the loop and ensure that the Iterator only loops through the action steps between the Iterator and Iterator End modules. This ensures that the workflow runs smoothly and efficiently, and prevents any errors or issues that may arise from an infinite loop.

---

# Iterator Storage

Source: https://support.flowmattic.com/kb/article/20/iterator-storage

The **Iterator Storage** module in FlowMattic allows users to store and manage data from each iteration within the Iterator loop. This data can be stored in two formats: **Array (JSON)** or **String**. However, it's important to note that the user needs to explicitly **set the array parameters** or **define the string format** in the Iterator Storage configuration. Only the data defined in these parameters will be stored and accumulated as the loop processes each item.

Iterator Storage works in two storage formats:

1. **Store as Array** (JSON format)

3. **Store as String** (String format)

Below is a detailed explanation of both storage formats, along with examples to illustrate how they function.

* * *

### 1\. Store as Array (JSON Format)

#### Functionality:

When **"Store as Array"** is selected, you need to define the **data parameters** (fields) that you want to store from each iteration of the loop. These parameters will form the array items, and new data from each loop iteration will be appended to the previously stored array within the same workflow execution.

The data is not automatically stored—**you must explicitly map each field** to be stored.

#### Example:

Let's say you're working with an e-commerce workflow where you're processing a JSON array of products that contain the product name and price:

```
{
  "products": [
    {
      "name": "Addidas",
      "price": 4000
    },
    {
      "name": "Nike",
      "price": 3500
    }
  ]
}
```

#### Workflow Steps:

1. **Iterator Module**: The JSON array (products) is passed into the Iterator module, and the loop processes each product individually.

3. **Iterator Storage Configuration**: In the **Iterator Storage** module, choose **Store as Array**. Then, **set the data parameters** for the array:

- **Parameter 1**: Name (e.g., `{iterator.name}`)

- **Parameter 2**: Price (e.g., `{iterator.price}`)

- Click on **Add More** to add any additional parameters if needed.

1. **Save and Test**: Click on **Save & Test Action** to see how the first product (Addidas) is stored in the array.

3. **Live Execution**: When the workflow runs in live mode, each product is added to the array as a separate element, resulting in the following output:

```
[
  {
    "name": "Addidas",
    "price": 4000
  },
  {
    "name": "Nike",
    "price": 3500
  }
]
```

#### Key Points:

- **Defining Array Parameters**: The array won't automatically store each item; you must define the fields (parameters) that should be included in the array.

- The array will continue to append data from each iteration within the same workflow session and is reset when a new session begins.

* * *

### 2\. Store as String

#### Functionality:

When **"Store as String"** is selected, you also need to define the string format by specifying which data fields from the loop iterations should be concatenated. Each new string data is appended to the previously stored string, creating a cumulative output across all iterations in the loop.

Again, the string format is **not automatically stored**—**you must define** the string structure for it to work.

#### Example:

You want to process the same list of products, but this time, you wish to store the name and quantity of each product as a concatenated string.

Input data:

```
{
  "products": [
    {
      "name": "Addidas",
      "quantity": 2
    },
    {
      "name": "Nike",
      "quantity": 5
    }
  ]
}
```

#### Workflow Steps:

1. **Iterator Module**: The Iterator processes each product in the array.

3. **Iterator Storage Configuration**: In the **Iterator Storage** module, select **Store as String**. Then, define the format of the string:

- String format: `{iterator.name} x {iterator.quantity}` (for example, "Addidas x 2")

1. **Save and Test**: When testing, the first string will be:

```
   Addidas x 2
```

4. **Live Execution**: During live execution, the second product (Nike) will be processed and appended to the stored string, resulting in:

```
   Addidas x 2
   Nike x 5
```

#### Key Points:

- **Defining String Format**: Similar to the array, the string is not automatically created. You must specify the format for how each iteration’s data is stored.

- The string is appended with each iteration and resets with each new workflow execution.

* * *

### Conclusion

The **Iterator Storage** module is a flexible tool for storing data as either a JSON array or a concatenated string during workflow execution. By setting the parameters or defining the string format, you can control precisely what data is stored and how it is accumulated during iterations. This ensures that only the required data is processed and used in subsequent workflow steps.

If you need further clarification or examples for a specific use case, feel free to ask!

---

# Jaadu: the AI copilot in FlowMattic

Source: https://support.flowmattic.com/kb/article/211/jaadu-the-ai-copilot-in-flowmattic

Jaadu is FlowMattic's AI copilot. It sits in a drawer beside whatever you are building, reads what you already have on screen, and works on it with you in conversation — adding steps, rewriting blocks, fixing a condition — over as many turns as you need.

That "over as many turns" part is what separates Jaadu from **Generate with AI**, which produces a finished draft in a single pass and then stops. If you are deciding which to reach for, see [Jaadu vs Generate with AI: which one should you use?](/kb/jaadu-vs-generate-with-ai).

![The Jaadu drawer open beside a workflow in the FlowMattic Workflow Builder, showing the AI provider picker with Claude and OpenAI](https://assets.infidesk.support/products/flowmattic/kb-images/v70/211-jaadu-drawer.png)

## Where you can use Jaadu

Jaadu is available in:

- **The Workflow Builder** — it can pick a trigger, search the integration catalogue for the right app and event, add steps, configure their fields, and set up routers and conditions.
- **The Form Builder** — it can add and reorder fields, edit labels and options, set validation, write conditional logic, and restyle the form.
- **The Email Template Builder**
- **The PDF Template Builder**
- **The Image Builder**

Open it from the Jaadu button in the builder you are working in. The drawer stays open beside your canvas, so you can watch changes land as you talk.

## What you need before you start

Jaadu needs an **AI provider connection** — your own API key, held in a FlowMattic Connect. There is no FlowMattic AI credit system and nothing to buy from us for it: you are billed by your AI provider directly, at their rates.

**Jaadu currently works with Anthropic (Claude) and OpenAI.** Support for more providers is being added gradually, so if yours is not on the list yet, it is worth checking again after an update.

This is narrower than the rest of FlowMattic's AI features on purpose — **Generate with AI**, the AI Agent action and the other AI surfaces work with ten providers including Google, Groq, Mistral, xAI, Perplexity, DeepSeek, OpenRouter and Straico. So if you already have, say, a Google connection and Jaadu will not accept it, that is expected today. Add an Anthropic or OpenAI connection under **FlowMattic → Connects** and Jaadu will pick it up.

## How to work with it

Talk to Jaadu the way you would brief a colleague who can see your screen. It already knows what is on the canvas, so you rarely need to describe it.

Useful things to ask for:

- "Add a step after the trigger that looks the customer up in our CRM."
- "This router only handles paid orders — add a branch for refunds."
- "Change the heading block to something friendlier and shorter."
- "Why isn't this condition matching?"

Because it works in turns, the productive pattern is small and specific. Ask for one change, look at what it did, then ask for the next. A single enormous instruction is more likely to need unpicking than three focused ones.

Jaadu edits what you have open. It does not run your workflow, and nothing it does is live until you save.

## If Jaadu will not load or respond

Jaadu talks to your AI provider **directly from your browser**, rather than routing through your WordPress server. That design keeps responses streaming smoothly, but it means the things that break Jaadu are usually on the browser side:

- **An ad-blocker or privacy extension** blocking the request. Try in a private window with extensions disabled.
- **A corporate network, VPN or firewall** that blocks `api.anthropic.com` or `api.openai.com`.
- **A content-security-policy plugin** on your site restricting outbound connections.

A quick way to confirm: **if Generate with AI works but Jaadu does not, the problem is almost certainly in the browser or network**, not your site or your key. Generate with AI runs on the server, so it takes a completely different path. Open your browser's developer console and check the Network tab for a blocked or failed request.

The reverse also happens: if your server has locked-down outbound traffic, Generate with AI can fail while Jaadu keeps working.

## If Jaadu cannot find the right app or event

Jaadu searches the integration catalogue to find apps and events. If it is consistently missing something you know exists, the catalogue index on your site can be rebuilt — get in touch with support and we will walk you through it.

## Related

- [Jaadu vs Generate with AI: which one should you use?](/kb/jaadu-vs-generate-with-ai)
- [Generate with AI in the Workflow Builder](/kb/generate-with-ai-in-the-workflow-builder)
- [Generate with AI in the Email Template Builder](/kb/generate-with-ai-in-the-email-template-builder)

---

# Jaadu vs Generate with AI

Source: https://support.flowmattic.com/kb/article/212/jaadu-vs-generate-with-ai

FlowMattic has two AI features that look similar in the interface and do genuinely different jobs. Picking the right one saves a lot of back-and-forth.

**Generate with AI** is a one-shot generator. You write a description, it produces a finished draft in a single pass, and it is done.

**Jaadu** is a copilot. It stays open beside your builder, sees what you already have, and edits it with you over as many turns as you need.

The short version: **use Generate with AI to get from nothing to something. Use Jaadu to change something that already exists.**

## Side by side

| | Generate with AI | Jaadu |
|---|---|---|
| Best for | Starting from a blank canvas | Refining what you have |
| Interaction | One description, one result | Back-and-forth conversation |
| Sees your current work | No — it creates something new | Yes — it reads what is on screen |
| Where it runs | On your server | In your browser |
| AI providers | 10 | Anthropic and OpenAI today, more being added |
| Where you'll find it | Workflow Builder, Email, PDF, Image, Forms | Workflow Builder, Email, PDF, Image |

## When to use Generate with AI

- You have an idea and no workflow yet: "when someone submits my contact form, add them to Mailchimp and notify me in Slack."
- You want a complete email drafted — layout, subject, pre-header and all — from a description of the campaign.
- You would rather start from a rough draft and edit by hand than start from an empty canvas.

Because it builds something new, running it on a template that already has content **replaces** what is there. It is a starting point, not an editor.

## When to use Jaadu

- You already have a workflow and want to add, remove or reconfigure a step.
- Something is not behaving and you want to talk through why.
- You want a series of small changes, checking each one as it lands.
- You want the AI to work *with* what you have rather than replace it.

## The practical differences that catch people out

**Provider support.** Generate with AI works with ten providers — OpenAI, Anthropic, Google, Groq, Mistral, xAI, Perplexity, DeepSeek, OpenRouter and Straico. **Jaadu currently works with Anthropic and OpenAI only, with more being added over time.** If you have a Google or Groq connection and Jaadu will not accept it, that is why. Add an Anthropic or OpenAI connection under **FlowMattic → Connects**.

**Where they run, and therefore how they fail.** Generate with AI runs on your server. Jaadu runs in your browser, talking to the AI provider directly. So:

- If **Jaadu fails but Generate with AI works**, look at your browser — ad-blockers, VPNs, corporate firewalls or a content-security-policy plugin.
- If **Generate with AI fails but Jaadu works**, look at your server's outbound connectivity.

That asymmetry is a genuinely useful diagnostic. Trying the other one tells you which side the problem is on.

**Neither uses FlowMattic credits.** Both use your own API key through a Connect, so your AI provider bills you directly. There is nothing to buy from FlowMattic to enable either.

## Using them together

The two work well in sequence, and this is the pattern we would recommend:

1. **Generate with AI** to get a complete first draft on the canvas.
2. Review it — remember that AI-generated workflows are saved switched **off** so you can check them before anything runs.
3. **Jaadu** to refine: fix the step that guessed wrong, add the branch it missed, tighten the copy.
4. Switch the workflow on.

## Related

- [Jaadu: the AI copilot in FlowMattic](/kb/jaadu-the-ai-copilot-in-flowmattic)
- [Generate with AI in the Workflow Builder](/kb/generate-with-ai-in-the-workflow-builder)
- [Generate with AI in the Email Template Builder](/kb/generate-with-ai-in-the-email-template-builder)

---

# Join Branch and Router Paths to Continue Your Workflow

Source: https://support.flowmattic.com/kb/article/242/join-branch-router-paths

Routers and Branches split your workflow into parallel paths — but sometimes those paths should come back together. The **Join** step merges every route of a Router (or both sides of a Branch) into a single chain, so the steps after it run once, no matter which path was taken.

Typical use: a Router decides *how* to handle an order (say, retail vs. wholesale), but every order should end with the same "log it and notify the team" steps. Build those steps once, after a Join. And when those shared steps need data from inside the routes — an order summary, a user email — [Merged Fields](#merged-fields--use-route-data-after-the-join) carry it across under one tag, whichever route ran.

## Join Router routes

### Step 1 — Build your Router as usual

Add a Router and put the steps for each route in place. Each route ends with a **+** button.

![A Router with two routes, each ending with a + button](https://assets.infidesk.support/products/flowmattic/kb-images/join-branch-router/rj-01-routes-open-3.png)

### Step 2 — Add the Join step

Click the **+** at the end of any route, and search for **Join** in the app picker.

![Searching for the Join step in the app picker](https://assets.infidesk.support/products/flowmattic/kb-images/join-branch-router/rj-02-join-picker-2.png)

Select it — no configuration is needed. Join has a single event, **Join Paths**, which is selected automatically.

### Step 3 — Every route converges

The Join connects itself to the end of **every** route in the Router — you don't wire the other routes manually. The **+** buttons after each route let you keep extending the routes individually.

![The Join step converging both Router routes](https://assets.infidesk.support/products/flowmattic/kb-images/join-branch-router/rj-03-joined-3.png)

### Step 4 — Continue your workflow after the Join

Add steps after the Join exactly like anywhere else. These are your common steps — they run once per execution, whichever route was taken.

![Steps continuing after the Join](https://assets.infidesk.support/products/flowmattic/kb-images/join-branch-router/rj-04-continue-2.png)

## Join Branch paths

The Branch works the same way: build your **Yes** and **No** sides, then add a **Join** at the end of either side. Both paths converge into it, and the workflow continues with shared steps.

![A Branch with Yes and No paths converging into a Join](https://assets.infidesk.support/products/flowmattic/kb-images/join-branch-router/bj-01-branch-joined-3.png)

## Merged Fields — use route data after the Join

Here's the catch with converging paths: on any given run, **only one route actually executed**. If a step after the Join mapped a tag from a step inside Retail orders, that tag would be empty every time the Wholesale route ran. That's why the dynamic tags picker doesn't offer the routes' internal steps after a Join.

**Merged Fields** solve this. On the Join step you define a field once — say `order_summary` — and map it separately for each route. At run time the Join fills it from whichever route executed, and every step after the Join reads it through a single tag like `{join7.order_summary}`, no matter which path the run took.

### Step 1 — Define your fields on the Join

Open the Join step and go to the **Configure** tab. Click **+ Add merged field**, give the field a name, and you'll see one mapping row per route. The chip next to the name shows the tag your later steps will use.

![The Merged Fields section on the Join's Configure tab, with per-route mapping rows](https://assets.infidesk.support/products/flowmattic/kb-images/join-branch-router/jm-01-merged-fields.png)

### Step 2 — Map each route

Each row maps one route. Type a static value, or click the **+** button to pick from that route's own steps — the picker opens scoped to that route, so you can't accidentally map data from a different one.

![The + button opens the dynamic tags picker scoped to that route's steps](https://assets.infidesk.support/products/flowmattic/kb-images/join-branch-router/jm-02-route-picker-2.png)

**Suggestions:** when every route's test data shares the same fields (for example, each route creates or updates a user and returns `user_id` and `user_email`), the Join shows a note — *"2 common fields found across all routes' test data"* — with a **Review & add** button. Nothing is added automatically; you tick the fields you want and FlowMattic maps each one from the route's step closest to the Join.

### Step 3 — Use the fields after the Join

In any step after the Join, open the dynamic tags picker as usual. The Join is listed like any other step, exposing your merged fields plus `executed_route` — the name of the route or path that ran, handy for logging and conditions.

![After the Join, the picker lists the Join's merged fields and executed_route](https://assets.infidesk.support/products/flowmattic/kb-images/join-branch-router/jm-04-after-join-picker-2.png)

### Testing your setup

The Join's **Test** tab shows everything at a glance: **Data in** is your per-route mapping, and **Data out** is a sample response built from each route's test data — so steps after the Join can resolve `{joinN.…}` tags in their own tests without running the workflow.

![The Join's Test tab showing the per-route mapping as Data in](https://assets.infidesk.support/products/flowmattic/kb-images/join-branch-router/jm-03-test-data-in.png)

### What a run records

In **Task History**, the Join's entry shows which route executed (by its name) and the final value of every merged field, while the Request Payload tab keeps the mapping you configured — so you can always see where a value came from.

![Task History showing the Join's response with executed route and merged field values](https://assets.infidesk.support/products/flowmattic/kb-images/join-branch-router/jm-05-task-history-2.png)

## How it runs

- The Router evaluates route conditions and runs the matching route's steps; the Branch runs its Yes or No side.
- When the executed path reaches its end, the run jumps to the Join and continues with the common steps — they execute **once**.
- If no Router route matches at all, the run still jumps to the Join, so your common steps always happen.
- Each merged field takes the executed route's value. If that route left the field empty (or unmapped), the first route with a value wins — so you can use another route's static value as a fallback.
- Steps **inside** the routes aren't offered in the tags picker after the Join — only the route that ran has values, so a route-specific tag would break on other runs. Use Merged Fields to carry route data across.

## Good to know

- **One Join per Router or Branch.** A scope can only converge once — add your shared steps after the existing Join.
- **Merged Fields work with Branches and nesting too.** A Branch's Join maps its **Yes** and **No** sides the same way, and when a route contains its own Branch with a Join, that inner Join's merged fields are offered when mapping the outer one.
- **Nested structures need their own Join first.** If a route contains its own Branch, give that Branch its own Join (and at least one step after it) before joining the outer Router — the builder guides you with a message if it's too early.
- **Deleting a Join removes everything below it.** Past the merge point there is no single route to reattach those steps to, so they're removed with it, and every route gets its **+** button back.
- **A joined Router or Branch can't be deleted directly** — delete its Join first, then the Router or Branch.

---

# JSON Parser Integration in FlowMattic

Source: https://support.flowmattic.com/kb/article/130/json-parser-integration-in-flowmattic

The JSON Parser is a built-in FlowMattic application that provides powerful JSON data manipulation, validation, and transformation capabilities within your workflows. No external connection or API key is required — it works entirely within your WordPress environment.

---

## Overview

JSON (JavaScript Object Notation) is the most common data format used by APIs, webhooks, and web services. The JSON Parser app lets you parse, validate, extract, merge, transform, and export JSON data as part of your automated workflows.

---

## Connection Setup

The JSON Parser is a **core utility app** — no connection setup is needed.

- No API key required
- No external service to configure
- Available immediately in all FlowMattic installations

Simply select **JSON Parser** when adding an action step to your workflow.

![JSON parser actions.png](/storage/kb-images/b3180e314f-inline.png)

---

## Available Actions

The JSON Parser provides **9 actions** for working with JSON data:

### 1. Parse JSON

Parses a JSON string and extracts all keys as individual output fields. Nested objects are automatically flattened using underscore notation.

**Input:**

| Field | Required | Description |
|-------|----------|-------------|
| JSON Data | Yes | The JSON string or data to parse. |

**Output:**

| Field | Description |
|-------|-------------|
| status | `success` or `error` |
| message | Status message |
| *Individual fields* | Each key in the JSON becomes a separate output field. |

**How Flattening Works:**

Nested JSON structures are flattened with underscores as separators:

```json
// Input
{
  "user": {
    "address": {
      "city": "New York",
      "zip": "10001"
    }
  }
}

// Output fields
user_address_city = "New York"
user_address_zip  = "10001"
```

This makes it easy to reference deeply nested values in subsequent workflow steps using `{JSONParser1.user_address_city}`.

![json parser - parse json.png](/storage/kb-images/60adff5137-inline.png)

---

### 2. Validate JSON

Checks whether a provided string is valid JSON and returns structure details.

**Input:**

| Field | Required | Description |
|-------|----------|-------------|
| JSON String | Yes | The JSON string to validate. |

**Output:**

| Field | Description |
|-------|-------------|
| status | `success` or `error` |
| is_valid | `true` or `false` |
| json_type | `array`, `object`, or `empty` |
| items_count | Number of top-level items |
| error_code | PHP JSON error code (if invalid) |
| message | Human-readable validation result |

> **Use Case:** Validate JSON received from a webhook or API before processing it, and use a Branch step to handle invalid data gracefully.


---

### 3. Stringify JSON

Converts an array or object into a JSON string.

**Input:**

| Field | Required | Description |
|-------|----------|-------------|
| Data to Stringify | Yes | Array, object, or any value to convert to a JSON string. |

**Output:**

| Field | Description |
|-------|-------------|
| status | `success` or `error` |
| json_string | The resulting JSON string |

> **Use Case:** Convert workflow data into a JSON string for sending in an HTTP request body or storing in a database.

---

### 4. Minify JSON

Removes all whitespace and formatting to produce the smallest possible JSON string.

**Input:**

| Field | Required | Description |
|-------|----------|-------------|
| JSON to Minify | Yes | JSON string to compress. |

**Output:**

| Field | Description |
|-------|-------------|
| status | `success` or `error` |
| minified_json | Compressed JSON output |
| original_size | Size of original JSON in bytes |
| minified_size | Size of minified JSON in bytes |
| saved_bytes | Number of bytes saved |

> **Use Case:** Optimize JSON data before storing it in a database or sending it over an API to reduce bandwidth and storage.

---

### 5. Prettify JSON

Formats JSON with proper indentation for human readability.

**Input:**

| Field | Required | Description |
|-------|----------|-------------|
| JSON to Prettify | Yes | JSON string to format. |

**Output:**

| Field | Description |
|-------|-------------|
| status | `success` or `error` |
| prettified_json | Formatted JSON with indentation |

> **Use Case:** Format JSON for display in emails, logs, or reports where readability matters.

---

### 6. Get JSON Value by Path

Extracts a specific value from a JSON structure using dot or slash path notation.

**Input:**

| Field | Required | Description |
|-------|----------|-------------|
| JSON Data | Yes | The JSON object to query. |
| JSON Path | Yes | Path to the value you want to extract. |

**Path Syntax:**

Both dot notation and slash notation are supported:

| Syntax | Example | Result |
|--------|---------|--------|
| Dot notation | `user.address.city` | Value at `user → address → city` |
| Slash notation | `user/address/city` | Same result |
| Array index (dot) | `items.0.name` | First item's `name` field |
| Array index (slash) | `items/0/name` | Same result |

**Output:**

| Field | Description |
|-------|-------------|
| status | `success` or `error` |
| value | The extracted value |
| path | The path that was queried |
| type | Data type of the value (`string`, `integer`, `array`, `object`, etc.) |

**Example:**

```json
// Input JSON
{
  "order": {
    "items": [
      { "name": "Widget", "price": 9.99 },
      { "name": "Gadget", "price": 19.99 }
    ],
    "total": 29.98
  }
}

// Path: order.items.1.name → "Gadget"
// Path: order.total → 29.98
// Path: order/items/0/price → 9.99
```

![json parser - get value by path.png](/storage/kb-images/a2a76914fd-inline.png)

---

### 7. Merge JSON Objects

Combines two JSON objects into a single object. Values from the second object override the first when keys match.

**Input:**

| Field | Required | Description |
|-------|----------|-------------|
| First JSON | Yes | The base JSON object. |
| Second JSON | Yes | The JSON object to merge in (overrides matching keys). |

**Output:**

| Field | Description |
|-------|-------------|
| status | `success` or `error` |
| merged_json | The combined JSON object |

**Merge Behavior:**

- Uses deep recursive merging — nested objects are merged, not replaced.
- When the same key exists in both objects, the second object's value wins.
- Arrays are preserved as-is (not merged element by element).

**Example:**

```json
// First JSON
{ "name": "John", "settings": { "theme": "light", "lang": "en" } }

// Second JSON
{ "email": "john@example.com", "settings": { "theme": "dark" } }

// Merged Result
{ "name": "John", "email": "john@example.com", "settings": { "theme": "dark", "lang": "en" } }
```

> **Use Case:** Merge user-provided data with default values, or combine responses from multiple API calls.

---

### 8. JSON to Query String

Converts a JSON object into a URL-encoded query string.

**Input:**

| Field | Required | Description |
|-------|----------|-------------|
| JSON Data | Yes | JSON object to convert. |

**Output:**

| Field | Description |
|-------|-------------|
| status | `success` or `error` |
| query_string | URL-encoded query string |

**Example:**

```json
// Input
{ "name": "John Doe", "city": "New York", "page": 1 }

// Output
name=John+Doe&city=New+York&page=1
```

> **Use Case:** Build URL parameters for API calls, redirect URLs, or form submissions dynamically within your workflow.

---

### 9. Create File from JSON

Saves JSON data as a `.json` file and uploads it to the WordPress Media Library.

**Input:**

| Field | Required | Description |
|-------|----------|-------------|
| JSON Data | Yes | The JSON data to save as a file. |
| File Name | No | Custom file name. Defaults to `json-export-{date}.json`. |

**Output:**

| Field | Description |
|-------|-------------|
| status | `success` or `error` |
| message | Success or error message |
| file_url | URL to the created file |
| attachment_id | WordPress attachment ID |
| file_name | Actual file name used |
| file_size | File size in bytes |
| records | Number of records in the JSON |

**File Naming:**
- The `.json` extension is added automatically if not provided.
- File names are sanitized using WordPress standards.
- If a file with the same name exists, a number suffix is appended (e.g., `export-1.json`, `export-2.json`).
- Default naming pattern: `json-export-2026-02-17-123456.json`

> **Use Case:** Export workflow data as a JSON file for download, email attachment, or archival purposes.

![json-parser - create file from json.png](/storage/kb-images/a26cb9f963-inline.png)

---

## Workflow Examples

### Example 1: Parse an API Response

Parse a JSON response from an HTTP request and use individual fields in subsequent steps.

1. **HTTP Request** — Call an external API that returns JSON.
2. **JSON Parser > Parse JSON** — Parse the response body.
3. **Email** — Send an email using `{JSONParser1.user_name}` and `{JSONParser1.user_email}`.

### Example 2: Validate and Route Data

Validate incoming JSON from a webhook and route the workflow based on validity.

1. **Webhook Trigger** — Receive JSON data.
2. **JSON Parser > Validate JSON** — Check if the data is valid.
3. **Branch** — If `{JSONParser1.is_valid}` is `true`, continue processing. Otherwise, send an error notification.

### Example 3: Merge and Export

Combine data from multiple sources and export as a file.

1. **HTTP Request** — Fetch user data from API.
2. **HTTP Request** — Fetch order data from another API.
3. **JSON Parser > Merge JSON** — Combine both responses.
4. **JSON Parser > Create File from JSON** — Save as a downloadable JSON file.
5. **Email** — Send the file URL to the admin.

### Example 4: Extract Nested Values

Extract specific values from complex nested JSON structures.

1. **Webhook Trigger** — Receive deeply nested JSON.
2. **JSON Parser > Get Value by Path** — Extract `order.items.0.name`.
3. **JSON Parser > Get Value by Path** — Extract `order.billing.address.city`.
4. **WooCommerce** — Use extracted values to create an order.

---

## Error Handling

| Error Message | Action | Cause | Solution |
|---------------|--------|-------|----------|
| "Invalid JSON format" | Parse JSON, Get Value | Malformed JSON string | Use Validate JSON first to check the data. |
| "Path not found in JSON" | Get Value by Path | Path doesn't exist in the data | Verify the path using Parse JSON to see all available keys. |
| "Both JSON objects are required" | Merge JSON | One or both inputs are empty | Ensure both fields have valid JSON data. |
| "Failed to encode JSON data" | Create File | Encoding issue | Validate the JSON data before creating a file. |
| "Failed to write JSON file" | Create File | File system permissions | Check WordPress uploads directory permissions (should be 755). |

---

## Tips

- **Chain multiple JSON Parser actions** — You can use Parse JSON, then Get Value by Path, then Stringify in sequence for complex transformations.
- **Use Validate JSON defensively** — Before processing JSON from external sources (webhooks, APIs), validate it first and use a Branch to handle invalid data.
- **Dynamic path extraction** — The path in "Get Value by Path" supports dynamic variables, so you can use `{Trigger1.field_name}` as the path itself.
- **File exports for reporting** — Use Create File from JSON to generate downloadable reports that can be emailed or stored.

---

## Summary

| Feature | Details |
|---------|---------|
| **Connection Required** | No (built-in core app) |
| **Available Actions** | 9 |
| **Triggers** | None |
| **Input Formats** | JSON strings, arrays, objects |
| **Path Notation** | Dot (`user.name`) and slash (`user/name`) |
| **File Export** | Creates files in WordPress Media Library |
| **Nested JSON** | Full support with flattening and path extraction |

---

# License Activated, but Still Shows Not Active on Integrations Page

Source: https://support.flowmattic.com/kb/article/11/license-activated-but-still-shows-not-active-on-integrations-page

If you've activated your FlowMattic license but still see a "License Not Active" message on the **Integrations** or other admin pages, this issue may be caused by cached license responses in WordPress. Here's an explanation and step-by-step guide to resolve it.

* * *

### **The Problem**

When users access the **Integrations Page** before activating the license, FlowMattic fetches the license status from the server and stores it in **WordPress transients** (temporary cache) for up to **24 hours**. Even after activating the license, the cached response might not clear immediately, causing the "License Not Active" message to persist.

* * *

### **The Solution**

To ensure the license status is updated and the transient cache is cleared, follow these steps:

1. **Go to the License Admin Page**:
    - In your WordPress dashboard, navigate to the **FlowMattic License Settings** page.

3. **Deactivate the License**:
    - Click the **Deactivate License** button to deactivate your current license.

5. **Wait for a Few Minutes**:
    - Allow some time (around 5-10 minutes) for the WordPress transient cache to clear.

7. **Re-Activate the License**:
    - Enter your license key again and click the **Activate License** button.

9. **Verify the License Status**:
    - After reactivating the license, revisit the **Integrations Page** or any other admin pages to confirm the license is now recognized as active.

* * *

### **Why This Works**

Deactivating and reactivating the license forces FlowMattic to fetch the latest license status directly from the server. This process also clears the outdated transient cache, ensuring the license status is updated across all admin pages.

* * *

### **Prevention Tips**

- Always activate your FlowMattic license before accessing the **Integrations Page** or other admin features.

- If you encounter this issue frequently, consider clearing WordPress transients manually using a plugin like **WP-Optimize** or directly through your database.

* * *

### **Conclusion**

This issue arises from cached license responses but can be quickly resolved by deactivating and reactivating your license. Following these steps ensures the transient cache is refreshed, and your license status is accurately reflected across all FlowMattic admin pages. If the issue persists, feel free to contact our support team for further assistance!

---

# Link Shortener

Source: https://support.flowmattic.com/kb/article/113/link-shortener

Automatically shorten long URLs in your WordPress workflows with FlowMattic's built-in Link Shortener integration. Create clean, shareable fmtk.in short links for social media posts, email campaigns, SMS messages, and marketing materials. Perfect for affiliate marketers, social media managers, email marketers, and content creators who need to transform lengthy URLs into concise, branded short links that are easier to share and track across multiple platforms.

## Key Features

Link Shortener provides instant URL shortening using FlowMattic's own fmtk.in domain with automatic URL validation, error handling, and seamless integration with your WordPress workflows. The integration works with dynamic data from previous workflow steps, making it ideal for automated marketing campaigns, social media posting, and email notification systems. All shortened links use the fmtk.in domain for consistency and brand recognition.

### When to Use Link Shortener

- **Social media automation**: Shorten product URLs before posting to Twitter, Facebook, or LinkedIn
- **Email campaigns**: Create clean, short links for email newsletters and promotional campaigns
- **SMS messaging**: Reduce character count in text messages by shortening URLs
- **Affiliate marketing**: Convert long affiliate links into short, shareable URLs
- **QR code generation**: Create shorter URLs that generate cleaner QR codes
- **Link tracking**: Prepare URLs for tracking and analytics in marketing workflows

---

## How to Use Link Shortener

### 1. Add Link Shortener to Your Workflow

In your workflow builder:
1. Click the **+** button to add a new step
2. Search for and select **Link Shortener** from the core integrations
3. Choose the **Shorten URL** action

### 2. Configure URL Settings

**URL to Shorten** (Required)
- Enter the long URL you want to convert to a short link
- Can use dynamic data from previous workflow steps
- Must be a valid URL format (including http:// or https://)
- Supports any web URL regardless of length or complexity

**Examples of valid URLs:**
```
https://example.com/products/category/subcategory/item-name?utm_source=email&utm_campaign=spring-sale
https://yourstore.com/blog/2024/01/15/ultimate-guide-to-product-reviews-and-comparisons
https://affiliate-program.com/tracking/refer?id=12345&campaign=Q1-2024&source=website
```

### 3. Use the Shortened Link

After shortening, Link Shortener returns the following data:

- `status`: Success or error status
- `long_url`: Original long URL that was shortened
- `short_url`: The new fmtk.in shortened URL

You can use these values in subsequent workflow steps.

---

## Example Use Cases

### Shorten Product URLs for Social Media
When sharing new products automatically on social media:
1. **Trigger**: New WooCommerce Product
2. **Link Shortener**: Shorten product URL
3. **Twitter**: Post product announcement with short URL

### Create Short Links for Email Campaigns
When sending promotional emails with long tracking URLs:
1. **Trigger**: Schedule (Weekly)
2. **Link Shortener**: Shorten campaign URL with UTM parameters
3. **Email**: Send newsletter with clean short link

### Automate Affiliate Link Shortening
When processing affiliate product feeds:
1. **Trigger**: API Polling (Product Feed)
2. **Link Shortener**: Shorten affiliate tracking URL
3. **WordPress**: Create post with shortened affiliate link

### SMS Notifications with Short URLs
When sending text message notifications:
1. **Trigger**: Order Confirmation
2. **Link Shortener**: Shorten order tracking URL
3. **SMS**: Send tracking link via SMS with Twillio (saves character count)

---

## Response Data Details

### Success Response
```json
{
  "status": "success",
  "long_url": "https://example.com/very-long-url-with-parameters",
  "short_url": "https://fmtk.in/abc123"
}
```

### Error Response
```json
{
  "status": "error",
  "error": "Invalid URL format provided."
}
```

---

## Important Notes

**Security Consideration**
Link shortening is intended to provide convenience, not security. Do not use shortened links for:
- Sensitive or private content
- Password reset links
- Payment or financial transaction URLs
- Personal or confidential information

**Best Use Cases**
Link Shortener is best used for:
- Public marketing and promotional content
- Social media sharing
- General content distribution
- Non-sensitive tracking and analytics

**URL Validation**
- All URLs are validated before shortening
- URLs must include protocol (http:// or https://)
- Invalid URLs will return an error message
- Empty or missing URLs will be rejected

---

## Troubleshooting

**URL shortening fails**
- Verify the URL includes http:// or https://
- Check that the URL is properly formatted and valid
- Ensure the URL is publicly accessible
- Make sure the URL field is not empty

**Invalid URL format error**
- Add http:// or https:// to the beginning of your URL
- Remove any special characters or spaces from the URL
- Verify the domain name is valid and properly formatted
- Use dynamic data tags correctly if pulling from previous steps

**Short URL not working**
- Verify the original long URL is still valid and accessible
- Check that the short URL was successfully created (status: success)
- Test the short URL in a browser to confirm it redirects properly
- Ensure you're using the complete short URL including https://

---

# Manage FlowMattic from WP-CLI

Source: https://support.flowmattic.com/kb/article/216/manage-flowmattic-from-wp-cli

FlowMattic ships WP-CLI commands for managing workflows and task history from the command line — useful for headless installs, deployment scripts, and routine maintenance you would rather not click through.

You need SSH access to the site and WP-CLI installed. All commands live under the `wp flowmattic` namespace.

## Workflow commands

```bash
# List workflows
wp flowmattic workflows list
wp flowmattic workflows list --status=on --limit=20
wp flowmattic workflows list --format=ids

# Inspect one
wp flowmattic workflows get abc1234567
wp flowmattic workflows get abc1234567 --format=json

# Check and change state
wp flowmattic workflows status  abc1234567
wp flowmattic workflows enable  abc1234567
wp flowmattic workflows disable abc1234567
wp flowmattic workflows toggle  abc1234567

# Delete
wp flowmattic workflows delete abc1234567
wp flowmattic workflows delete abc1234567 --yes
```

`--format` accepts `table` (the default), `json`, `csv` and `ids`.

### Finding a workflow ID

The ID is the short alphanumeric string like `abc1234567` — **not** the WordPress post ID. You will find it in the workflow's URL in the admin, or by running `wp flowmattic workflows list`.

## Task history commands

```bash
# How many task records exist
wp flowmattic tasks count
wp flowmattic tasks count --workflow=abc1234567

# List them
wp flowmattic tasks list --workflow=abc1234567
wp flowmattic tasks list --workflow=abc1234567 --limit=100 --format=json

# Clear history for one workflow
wp flowmattic tasks clear --workflow=abc1234567
wp flowmattic tasks clear --workflow=abc1234567 --yes

# Delete records older than N days
wp flowmattic tasks purge --older-than=30
wp flowmattic tasks purge --older-than=7 --yes
```

## Keeping task history under control

On a busy site the task history table grows quickly, and a very large table can slow the admin down and bloat your backups. A scheduled purge is the tidiest fix:

```bash
wp flowmattic tasks purge --older-than=30 --yes
```

Run from a nightly system cron, that keeps a rolling 30 days of history and stops the table growing without limit. Pick a retention window that suits how far back you actually need to debug.

## Please back up first

`tasks clear` and `tasks purge` **permanently delete task history, and there is no undo.** Take a database backup before running either the first time, and double-check the `--workflow` ID and the `--older-than` value before adding `--yes`.

Both commands prompt for confirmation unless you pass `--yes`. Leaving the prompt in place is a good safety net for interactive use; only add `--yes` in scripts where you are certain of the arguments.

## Scripting examples

Disable every workflow before a maintenance window:

```bash
for id in $(wp flowmattic workflows list --status=on --format=ids); do
  wp flowmattic workflows disable "$id"
done
```

Export a workflow's definition for version control:

```bash
wp flowmattic workflows get abc1234567 --format=json > workflow-abc1234567.json
```

Check how much history a specific workflow has accumulated:

```bash
wp flowmattic tasks count --workflow=abc1234567
```

---

# Managing Content Sources for Your AI Assistant Chatbot

Source: https://support.flowmattic.com/kb/article/139/ai-assistant-content-sources

Your AI Assistant is only as good as the knowledge you give it. The **Content** tab lets you feed your chatbot with information from multiple sources — uploaded files, web pages, FlowMattic Tables, and WordPress posts. The more relevant content you add, the better your chatbot answers.

## How It Works

When you add content, FlowMattic uploads it to your OpenAI Vector Store. The chatbot then searches this knowledge base every time a visitor asks a question, finding the most relevant information to craft its response.

## Source 1: Upload Files

Upload documents directly to your chatbot's knowledge base.

### Supported File Types

You can upload PDFs, text files, markdown files, and other document formats supported by OpenAI.

### How to Upload

1. Open the **Content** tab in your AI Assistant
2. Expand the **Upload Files** section
3. Click **Add Source**
4. Select your file and upload it
5. Wait for the status to show **Completed**

![AI Assistants - add content source - files.png](/storage/kb-images/58ae661cf9-inline.png)

### Managing Uploaded Files

Once you have files uploaded, you can:

- **View All Files** — Opens a file manager showing all uploaded documents with their status
- **Search** — Filter files by name in the file manager
- **Delete** — Select files and remove them from the knowledge base

Each file shows a status badge:
- **Completed** — File is processed and available to the chatbot
- **In Progress** — File is being processed
- **Failed** — Upload or processing failed — try again

## Source 2: Crawl Web Pages

Add knowledge from any publicly accessible web page. This is useful for FAQ pages, help centers, product pages, or any content hosted outside WordPress.

### How to Add URLs

1. Expand the **Crawl Webpages** section
2. Enter a URL in the input field (e.g., `https://yoursite.com/help-center`)
3. Click **Add URL** to add more URLs
4. Click **Crawl All** to start crawling all URLs at once

![AI Assistant - content source - webpage.png](/storage/kb-images/8faffe3952-inline.png)


### Tips

- Add your most important pages — FAQ, pricing, product descriptions, terms of service
- Each URL is crawled independently, so you can add as many as you need
- The crawled content is automatically uploaded to your Vector Store
- If a page changes, re-crawl it to update the knowledge base

## Source 3: Connect FlowMattic Tables

If you store data in FlowMattic Tables (customer records, product catalogs, inventory, etc.), you can connect them directly to your chatbot.

### How to Connect a Table

1. Expand the **Connect Tables** section
2. Select a table from the dropdown — it shows all your FlowMattic Tables with row counts
3. Configure **Auto Sync** to keep data up to date:

| Auto Sync Option | Behavior |
|------------------|----------|
| Manual only | Table data only syncs when you click "Sync Table Now" |
| When new rows are added | Automatically syncs when new data is inserted |
| When rows are updated | Automatically syncs when existing rows change |
| When rows are added or updated | Syncs on both inserts and updates |

4. Click **Sync Table Now** to do the initial sync

> **Note:** Auto sync has a 5-minute cooldown to prevent rapid repeated syncs when multiple rows change in quick succession.

### How It Works

FlowMattic exports your table data and uploads it to the Vector Store in chunks (10,000 rows per chunk). The dropdown shows you how many chunks will be created based on your row count.

## Source 4: Sync WordPress Posts

Connect your WordPress content directly — pages, posts, and any custom post type.

### How to Sync Posts

1. Expand the **Sync WordPress Posts** section
2. Click **Add Post Type**
3. Select a post type from the dropdown (Pages, Posts, Products, or any registered custom post type)
4. Add more post types if needed
5. Click **Sync Now** to start syncing

![AI Assistant - content source - wordpress.png](/storage/kb-images/7333bbd622-inline.png)

### What Gets Synced

FlowMattic exports the content of all published posts for each selected post type and uploads them to your Vector Store. This includes the post title, content, and key metadata.

### Keeping Content Updated

After the initial sync, click **Sync Now** again whenever you publish new content or make significant updates. The status display shows when the last sync was completed.

## Source 5: Google Docs & Notion (Coming Soon)

Direct integrations with Google Docs and Notion are currently in development. These will allow you to connect documents and databases from these platforms as content sources.

## Best Practices

1. **Start with your most-asked questions** — Upload FAQ documents, help articles, and product guides first
2. **Be specific** — The more focused your content, the better the chatbot's answers. A targeted help doc beats a generic brochure.
3. **Keep it updated** — Re-sync tables and re-crawl pages when your content changes
4. **Test after adding content** — Ask your chatbot questions about the newly added content to verify it's working
5. **Don't overload** — Quality matters more than quantity. Adding irrelevant content can confuse the chatbot.

## What's Next?

With your knowledge base set up, your chatbot can now answer questions intelligently. Next steps:

- [Collect leads and schedule meetings from your chatbot](/kb/collect-leads-and-schedule-meetings-from-your-chatbot) — capture contact details and let visitors book a slot
- [Customize your chatbot's appearance](/kb/customize-your-chatbots-appearance) — make your chatbot match your brand

---

# Managing Integration Updates in FlowMattic

Source: https://support.flowmattic.com/kb/article/134/managing-integration-updates-in-flowmattic

FlowMattic provides five different methods to keep your integrations up to date. Whether you manage a single site or 50+ sites, there is an update method tailored to your workflow.

---

## Overview of Update Methods

| Method | Best For | Requires |
|--------|----------|----------|
| [Individual Update](#1.-individual-update) | Updating a specific integration | Dashboard access |
| [Update All Button](#2.-update-all-button) | Updating everything at once from the dashboard | Dashboard access |
| [WP CLI Commands](#3.-wp-cli-commands) | Server scripts, MainWP, bulk site management | SSH or terminal access |
| [Auto-Update (Cron)](#4.-auto-update-(cron)) | Hands-free daily updates | Settings toggle |
| [Helper Function (Developer)](#5.-helper-function-for-developers) | Custom plugins, workflows, or automation scripts | PHP code access |

All methods require an **active FlowMattic license** on the site.

---

## 1. Individual Update

Update a single integration from the FlowMattic Integrations page.

### How to Use

1. Go to **FlowMattic > Integrations** in your WordPress dashboard.
2. If an integration has an update available, the **Update** button appears on its card.
3. Click the **Update** button on the integration you want to update.
4. A loading indicator will appear while the update is being installed.
5. Once complete, the card will be removed from the updates list confirming the update was successful.

### What Happens Behind the Scenes

- FlowMattic downloads the latest version of the integration from the update server.
- The integration ZIP file is extracted to `/wp-content/flowmattic-apps/`.
- The old version is replaced with the new version.
- The temporary ZIP file is automatically cleaned up.

### Notes

- Only integrations with available updates will show the Update button.
- If the license is not active, the Update button will be disabled.
- The page filters allow you to view only integrations with updates available using the **Update Available** filter.

---

## 2. Update All Button

Update every integration that has an available update with a single click.

### How to Use

1. Go to **FlowMattic > Integrations** in your WordPress dashboard.
2. If any integrations have updates available, the **Update All** button appears in the top-right corner of the filter navigation bar (highlighted in yellow/warning color).
3. Click the **Update All** button.
4. A confirmation dialog will ask: *"This will update all installed integrations to the latest version."*
5. Click **Update All** to confirm.
6. A loading indicator will appear — this may take a few moments depending on how many integrations need updating.
7. Once complete, a summary will show the number of integrations updated, failed, and already up to date.
8. The page will automatically reload to reflect the changes.

### Update Summary

After the update completes, you will see a breakdown:

- **Updated** — Number of integrations successfully updated.
- **Failed** — Number of integrations that failed to update (e.g., download issues).
- **Already up to date** — Number of integrations that were skipped because they are already on the latest version.

### Notes

- The Update All button only appears when there is at least one integration with an update available AND the license is active.
- The process has a 5-minute timeout to accommodate sites with many integrations.
- If some integrations fail, the successful ones will still be applied.

---

## 3. WP CLI Commands

Manage integration updates from the command line. This is ideal for agencies using tools like MainWP, server management scripts, or automated deployment pipelines.

### Prerequisites

- [WP-CLI](https://wp-cli.org/) must be installed on the server.
- SSH or terminal access to the WordPress installation.
- FlowMattic must be activated with a valid license.

### Available Commands

#### List Integrations

View all installed integrations with their version and update status.

```bash
wp flowmattic integrations list
```

**Example Output:**

```
+---------------------+---------------------+-----------+-----------+------------------+
| slug                | name                | installed | available | status           |
+---------------------+---------------------+-----------+-----------+------------------+
| airtable            | Airtable            | 1.2.0     | 1.3.0     | Update available |
| slack               | Slack               | 2.1.0     | 2.1.0     | Up to date       |
| google-spreadsheets | Google Spreadsheets | 3.0.0     | 3.1.0     | Update available |
| mailchimp           | Mailchimp           | 1.5.0     | 1.5.0     | Up to date       |
+---------------------+---------------------+-----------+-----------+------------------+
```

**Options:**

| Option | Description |
|--------|-------------|
| `--updates-only` | Only show integrations that have updates available |
| `--format=<format>` | Output format: `table` (default), `json`, or `csv` |

**Examples:**

```bash
# Show only integrations with updates
wp flowmattic integrations list --updates-only

# Output as JSON (useful for scripts)
wp flowmattic integrations list --format=json

# Output as CSV
wp flowmattic integrations list --format=csv
```

#### Update Integrations

Update specific integrations or all integrations at once.

```bash
# Update all integrations
wp flowmattic integrations update --all

# Update specific integrations by slug
wp flowmattic integrations update airtable slack google-spreadsheets
```

**Example Output:**

```
Updating all integrations...
Success: airtable updated from v1.2.0 to v1.3.0.
Skipped slack: Already up to date.
Success: google-spreadsheets updated from v3.0.0 to v3.1.0.
Skipped mailchimp: Already up to date.

Summary: 2 updated, 0 failed, 2 skipped.
Success: Done.
```

**Options:**

| Option | Description |
|--------|-------------|
| `<slug>...` | One or more integration slugs to update |
| `--all` | Update all integrations that have updates available |

### Using with MainWP

If you use [MainWP](https://mainwp.com/) to manage multiple WordPress sites, you can run these commands across all your child sites:

1. Go to **MainWP > Sites** and select the sites you want to update.
2. Use the **WP CLI** feature to run the commands remotely.
3. Run `wp flowmattic integrations update --all` on each site.

### Using in Shell Scripts

You can create a simple shell script to update integrations across multiple sites:

```bash
#!/bin/bash
# Update FlowMattic integrations on multiple sites

SITES=(
    "/var/www/site1/public_html"
    "/var/www/site2/public_html"
    "/var/www/site3/public_html"
)

for site in "${SITES[@]}"; do
    echo "Updating integrations on: $site"
    wp --path="$site" flowmattic integrations update --all
    echo "---"
done
```

### Using in Cron Jobs (Server Level)

Add a server-level cron job to update integrations automatically:

```bash
# Run daily at 3:00 AM
0 3 * * * cd /var/www/yoursite/public_html && wp flowmattic integrations update --all >> /var/log/flowmattic-updates.log 2>&1
```

---

## 4. Auto-Update (Cron)

Enable automatic daily updates so your integrations stay current without any manual intervention.

### How to Enable

1. Go to **FlowMattic > Settings** in your WordPress dashboard.
2. Scroll down to the **General Settings** section.
3. Find the **Auto-Update Integrations** setting.
4. Change the dropdown from **Disabled** to **Enabled**.
5. Click **Save Settings**.

![FlowMattic - auto-update integrations settings.png](/storage/kb-images/a0524c9f16-inline.png)

### How It Works

- When enabled, FlowMattic registers a daily WordPress cron event.
- Once per day, the cron checks all installed integrations for available updates.
- Any integration with a newer version available is automatically downloaded and installed.
- The cron only runs if the site has an active FlowMattic license.

### How to Disable

1. Go to **FlowMattic > Settings**.
2. Change **Auto-Update Integrations** back to **Disabled**.
3. Click **Save Settings**.
4. The daily cron event is immediately removed.

### Notes

- **Default:** Disabled. You must explicitly enable this feature.
- The cron runs via WordPress's built-in cron system (`wp-cron`). If your site has WP-Cron disabled (using `DISABLE_WP_CRON`), you will need a server-level cron to trigger `wp-cron.php`.
- Updates happen silently in the background — no dashboard notifications are sent.
- Failed updates for individual integrations do not affect other integrations in the same batch.

---

## 5. Helper Function for Developers

FlowMattic provides PHP helper functions that developers can use in custom plugins, custom code snippets, or FlowMattic workflows.

### `flowmattic_update_all_integrations()`

Updates all installed integrations (or specific ones) that have new versions available.

**Function Signature:**

```php
flowmattic_update_all_integrations( $slugs = '' )
```

**Parameters:**

| Parameter | Type | Default | Description |
|-----------|------|---------|-------------|
| `$slugs` | `string\|array` | `''` (empty) | Specific slug(s) to update. Leave empty to update all. |

**Return Value:**

Returns an associative array with the following structure:

```php
array(
    'status'  => 'success',          // 'success' or 'error'
    'message' => '2 updated, ...',   // Human-readable summary
    'updated' => 2,                  // Count of successfully updated
    'failed'  => 0,                  // Count of failed updates
    'skipped' => 3,                  // Count of skipped (up to date)
    'details' => array(              // Per-integration breakdown
        array(
            'slug'   => 'airtable',
            'status' => 'updated',   // 'updated', 'skipped', or 'failed'
            'from'   => '1.2.0',     // Previous version
            'to'     => '1.3.0',     // New version
        ),
        array(
            'slug'   => 'slack',
            'status' => 'skipped',
            'reason' => 'Already up to date.',
        ),
    ),
)
```

**Usage Examples:**

```php
// Update all integrations.
$result = flowmattic_update_all_integrations();

if ( 'success' === $result['status'] ) {
    echo $result['updated'] . ' integrations updated.';
}

// Update specific integrations only.
$result = flowmattic_update_all_integrations( array( 'airtable', 'slack' ) );

// Update a single integration.
$result = flowmattic_update_all_integrations( 'google-spreadsheets' );
```

### `flowmattic_update_integration()`

Updates a single integration by its slug. This is the low-level function used internally by all other update methods.

**Function Signature:**

```php
flowmattic_update_integration( $slug, $app_url )
```

**Parameters:**

| Parameter | Type | Description |
|-----------|------|-------------|
| `$slug` | `string` | The integration slug (e.g., `airtable`) |
| `$app_url` | `string` | The remote URL containing the integration metadata |

**Return Value:**

```php
array(
    'status'  => 'success',  // 'success' or 'error'
    'message' => '...',      // Error message if failed
)
```

### Using in a FlowMattic Workflow

You can call the update function from a FlowMattic PHP Functions action step:

```php
// In a PHP Functions action step -
function name - flowmattic_update_all_integrations
Function Parameters - slug = <integration_slug>
```

### Action Hook for Automation

Developers can trigger integration updates via a WordPress action hook:

```php
// In your custom plugin or functions.php.
add_action( 'my_custom_update_trigger', function() {
    if ( function_exists( 'flowmattic_update_all_integrations' ) ) {
        $result = flowmattic_update_all_integrations();
        // Log or process the result as needed.
    }
} );
```

---

## Troubleshooting

### Updates Are Not Appearing

- Verify your FlowMattic license is active under **FlowMattic > License**.
- Clear the integration cache by visiting the **Integrations** page — the cache refreshes automatically.
- Check that your server can reach the FlowMattic update server (no firewall blocking outgoing requests).

### Update Fails for a Specific Integration

- Check that the `/wp-content/flowmattic-apps/` directory is writable by the web server.
- Ensure sufficient disk space is available on the server.
- Try updating the individual integration using the single Update button on its card.
- If the issue persists, delete the integration and reinstall it fresh from the Integrations page.

### Auto-Update Is Not Running

- WordPress cron (`wp-cron`) must be functional. If `DISABLE_WP_CRON` is set to `true` in `wp-config.php`, you need a server-level cron job hitting `wp-cron.php`.
- Verify the setting is set to **Enabled** under **FlowMattic > Settings > Auto-Update Integrations**.
- Low-traffic sites may experience delayed cron execution since WordPress cron runs on page visits. Consider setting up a real server cron.

### WP CLI Command Not Found

- Make sure FlowMattic is activated on the site.
- Run `wp plugin list` to confirm FlowMattic shows as active.
- The CLI commands are only registered when `WP_CLI` is defined, which happens automatically in WP-CLI environments.

---

## Frequently Asked Questions

**Do updates affect my workflows or connections?**
No. Integration updates only replace the integration files. Your workflows, connections, settings, and task history remain untouched.

**Can I roll back an integration update?**
There is no built-in rollback feature. If an update causes issues, you can delete the integration and reinstall the previous version by contacting support.

**How often does auto-update check for new versions?**
Once per day, using WordPress's daily cron schedule.

**Will the Update All button update core integrations too?**
No. The Update All button and bulk update functions only update integrations installed in the `/wp-content/flowmattic-apps/` directory. Core integrations bundled with the plugin are updated with plugin updates.

**Can I use WP CLI commands with Multisite?**
Yes. Use the `--url` flag to target a specific site in a WordPress Multisite network:

```bash
wp --url=site1.example.com flowmattic integrations update --all
```

---

# Maths

Source: https://support.flowmattic.com/kb/article/25/maths

Maths by FlowMattic is a module that allows users to perform mathematical calculations based on the input provided within a workflow. It is a tool designed to make workflow automation more efficient and streamlined by providing a simple and user-friendly interface for performing calculations.

This module is particularly useful for businesses that deal with large as well as small volumes of data and require quick and accurate calculations. It eliminates the need for manual calculations, reducing the risk of errors and saving time. Additionally, it can be integrated with other modules in FlowMattic, allowing users to create complex workflows that include multiple calculations.

**Step by Step Documentation for Maths by FlowMattic:**

1. To create a new workflow on FlowMattic in WordPress, you need to first log in to your WordPress dashboard and navigate to the FlowMattic -> Workflows. Now, click on the "New Workflow" button

 ![new-workflow.jpeg](/storage/kb-images/3430a09ed7-inline.png)

2. By default, the trigger step is added with webhook module selected. Click on the trigger step and then in “Setup” tab, click the “Change” button, Then, choose the “Maths” module from the FlowMattic Built-in Tools-
 
 ![choose-maths-module.jpeg](/storage/kb-images/13beaad81c-inline.png)

3. Once you've selected the Maths module, choose "Execute Maths Equation" as the Action Event. Currently, there's only one action event available for the Maths module.

4. In the "Enter Math Equation" field, you can enter the equation you want to calculate. For example, if you want to add 10 to the total price of a WooCommerce order, you could enter "{woocommerce1.total} + 10". This will add 10 to the total price of the order.
 
 ![maths-write-equation.jpeg](/storage/kb-images/34658dea6b-inline.png)

You can use a wide range of mathematical operators and functions in your equations. For example, you can use "+", "-", "\*", "/", "%", and "^" to perform addition, subtraction, multiplication, division, modulo, and exponentiation, respectively. You can also use functions like "sqrt()", "sin()", "cos()", "tan()", "log()", and "exp()" to perform more advanced calculations.

5. Once you've entered your equation, click the "Continue" button at the bottom, and move to the "Test" tab. Now, click the Test Action to see the final result of your maths equation. The Maths module will perform the calculations based on your equation and return the result as an output.

6. Finally, click on the "Save and Close" button to save the Maths module settings and close the settings popup - 
 
 ![maths-save-close.jpeg](/storage/kb-images/89e68ee962-inline.png)

## **Conclusion:**

Using the Maths module by FlowMattic, you can easily perform calculations and data manipulation within your workflow. With its user-friendly interface and support for a wide range of mathematical operators and functions, the Maths module is a powerful tool for automating your calculations and saving time.The Maths module by FlowMattic allows users to perform calculations based on the input within the workflow. This can be useful for automating calculations and data manipulation within your workflow.

---

# MCP Client Integration in FlowMattic

Source: https://support.flowmattic.com/kb/article/135/mcp-client-integration-in-flowmattic

FlowMattic's MCP Client allows you to connect to any external Model Context Protocol (MCP) server and execute its tools — either as a direct workflow step or as an AI Agent tool. This turns FlowMattic into a universal MCP client that can interact with thousands of MCP-compatible services.

![flowmattic mcp client.png](/storage/kb-images/476ba07148-inline.png)

---

## How the MCP Client Works

The MCP Client uses the **Streamable HTTP** transport protocol to communicate with MCP servers:

1. You provide the MCP server's **endpoint URL** and optional **authentication**.
2. FlowMattic sends a `tools/list` request to discover available tools on the server.
3. You select a tool and configure its parameters (or let the AI Agent choose dynamically).
4. FlowMattic sends a `tools/call` request to execute the selected tool.
5. The server processes the request and returns the result.

The client supports session management via `Mcp-Session-Id` headers, automatic reconnection, and configurable timeouts.

---

## Two Usage Contexts

The MCP Client works in two different contexts depending on where you use it:

| Context | Description | Tool Selection | Parameters |
|---------|------------|----------------|------------|
| **AI Agent Tool** | Added as a tool inside an AI Agent component | AI chooses from available tools dynamically | AI fills parameters based on its reasoning |
| **Regular Workflow Step** | Used as a standard action step in a workflow | You select one specific tool from a dropdown | You configure static or dynamic tag values |

---

## Setting Up the MCP Client

### Basic Configuration

Every MCP Client configuration requires:

1. **Endpoint URL** — The MCP server's Streamable HTTP endpoint (e.g., `https://your-server.com/mcp`)
2. **Authentication** — Choose from None, Bearer Token, API Key, or Custom Headers
3. **Tool Selection** — Pick a specific tool (workflow step) or configure tool filtering (AI Agent)
4. **Timeout** — Connection timeout in seconds (default: 60)

### Authentication Methods

| Method | Fields | Use Case |
|--------|--------|----------|
| **None** | — | Public MCP servers with no auth |
| **Bearer Token** | Token value | OAuth2 / JWT bearer authentication |
| **API Key (Custom Header)** | Header name + Header value | API key passed in a custom header (e.g., `X-API-Key`) |
| **Custom Headers** | Key-value pairs | Multiple custom headers for complex auth scenarios |

> **Tip:** You can use dynamic tags in auth fields to pull tokens from previous workflow steps, stored options, or environment variables.

---

## Using MCP Client as an AI Agent Tool

When added as a tool inside an AI Agent, the MCP Client expands into individual tools that the AI can call autonomously.

### Configuration

1. Open your AI Agent in the Visual Workflow Builder.
2. Add a new tool and select **MCP Client > Execute Tool**.
3. Enter the MCP server **Endpoint URL**.
4. Configure **Authentication** if required.
5. Set the **Tools to Include** mode:

| Mode | Behavior |
|------|----------|
| **All Tools** | All tools from the MCP server are available to the AI |
| **Selected Tools Only** | Only the tools you check are available |
| **All Except** | All tools except the ones you check are available |

6. For **Selected** or **Except** modes:
   - Click **Fetch & Select Tools** to load the tool list from the server.
   - Use the **search box** to filter tools by name or description.
   - Check/uncheck tools as needed.
7. Click **Continue** and then **Save & Close**.

### How It Works at Runtime

When the AI Agent executes:

1. FlowMattic connects to the MCP server and fetches the tool list.
2. Based on your tools mode, it filters the available tools.
3. Each MCP tool is converted into a function the AI model can call (with name, description, and input schema).
4. The AI decides which tool(s) to call and provides the required parameters.
5. FlowMattic executes the tool call against the MCP server and returns the result to the AI.
6. The AI can chain multiple tool calls across iterations.

> **Note:** MCP tools are expanded alongside any other tools configured in the AI Agent. The AI can use both MCP tools and regular FlowMattic tools in the same conversation.

### Token Usage Optimization

MCP servers can expose tools with large input schemas. FlowMattic automatically optimizes tool schemas to reduce token usage by:

- Stripping non-essential metadata fields (`$schema`, `title`, `examples`, `default`, `pattern`, `format`)
- Truncating tool descriptions to 200 characters
- Collapsing deeply nested schemas (beyond 3 levels)

---

## Using MCP Client as a Workflow Step

When used as a regular workflow step, you select a single tool and configure its parameters manually.

### Configuration

1. Add a new action step in your workflow.
2. Select **MCP Client > Execute Tool**.
3. Enter the MCP server **Endpoint URL**.
4. Configure **Authentication** if required.
5. Click the **refresh button** next to the Tool dropdown to fetch available tools.
6. Select the tool you want to execute.
7. Fill in the **Tool Parameters** that appear based on the tool's input schema.
8. Set the **Timeout** value if needed.

### Parameter Types

Parameters are dynamically generated based on the selected tool's `inputSchema`:

| Schema Type | Input Field | Notes |
|-------------|------------|-------|
| `string` | Text input | Supports dynamic tags |
| `number` / `integer` | Text input | Enter numeric values |
| `boolean` | Dropdown (true/false) | — |
| `enum` | Dropdown with options | Options from the schema |
| `object` / `array` | Textarea (JSON) | Enter valid JSON, supports dynamic tags |

> **Tip:** Use dynamic tags (the `+` button) to insert values from previous workflow steps into tool parameters.

### Response Data

The MCP Client returns the tool's response as structured data that can be used in subsequent workflow steps via dynamic tags. The response typically includes:

- `content` — Array of content blocks (text, images, resources)
- `isError` — Whether the tool execution resulted in an error

---

## Connecting to Popular MCP Servers

### FlowMattic MCP Server

Connect one FlowMattic site to another's MCP server:

```
Endpoint URL: https://your-site.com/wp-json/flowmattic/v1/mcp-server/{server-id}
Auth: Bearer Token or API Key (as configured on the server)
```

### GitHub MCP Server

```
Endpoint URL: https://api.githubcopilot.com/mcp/
Auth: Bearer Token (GitHub Personal Access Token)
```

### Zapier MCP Server

```
Endpoint URL: https://actions.zapier.com/mcp/{your-id}/sse
Auth: Bearer Token (Zapier API Key)
```

> **Important:** Each MCP server has its own endpoint format and authentication requirements. Refer to the server's documentation for the correct configuration.

---

## Troubleshooting

### Common Issues

**"Failed to connect to MCP server"**
- Verify the endpoint URL is correct and accessible from your WordPress server.
- Check that your server can make outbound HTTPS requests.
- Ensure the MCP server is running and responding.

**"Failed to fetch tools" / Empty tool list**
- The MCP server may require authentication. Check your auth configuration.
- The server might not support `tools/list`. Verify it implements the MCP protocol.
- Check the timeout value — some servers need more time to respond.

**"Tool execution failed"**
- Verify the parameters match the tool's expected input schema.
- Check that your authentication token has the required permissions.
- Review the MCP server's logs for detailed error messages.

**AI Agent not using MCP tools**
- Ensure the tools mode is set correctly (not "All Tools" with an unreachable server).
- Check that the endpoint URL and auth are configured in the tool settings.
- Verify the MCP server is accessible at the time of AI Agent execution.

**High token usage with MCP tools**
- Use **Selected Tools Only** mode to limit the number of tools exposed to the AI.
- MCP servers with many tools (30+) will increase prompt token usage for tool definitions.
- Tool response data from MCP servers contributes to completion tokens — large responses (e.g., full contact lists) will use more tokens.

---

## Summary

| Feature | Details |
|---------|---------|
| **App Name** | MCP Client |
| **Action** | Execute Tool |
| **Transport** | Streamable HTTP (JSON-RPC 2.0) |
| **Auth Methods** | None, Bearer Token, API Key, Custom Headers |
| **AI Agent Support** | Yes — expands into individual callable tools |
| **Workflow Step Support** | Yes — single tool with configured parameters |
| **Tool Filtering** | All, Selected Only, All Except |
| **Session Management** | Automatic via Mcp-Session-Id header |
| **Schema Optimization** | Automatic — reduces token usage for AI agents |
| **Timeout** | Configurable (default: 60 seconds) |
| **Since** | FlowMattic 6.0 |

---

# Migrating Facebook Pages Authentication to REST API Endpoint

Source: https://support.flowmattic.com/kb/article/137/migrating-facebook-pages-authentication-to-rest-api-endpoint

Starting from **Facebook Pages integration v1.1**, the authentication flow has been migrated from the external FlowMattic API server (`https://api.flowmattic.com/facebook-pages`) to a local **WordPress REST API endpoint** on your own site. This means the entire OAuth flow now happens directly between your WordPress site and Facebook — no third-party server involved.

This guide walks you through updating your existing Facebook Pages connection to use the new REST API-based authentication.

---

## What Changed?

In **v1.0**, the Facebook Pages authentication was routed through the FlowMattic API server (`https://api.flowmattic.com/facebook-pages`). This could sometimes be blocked by Cloudflare, security plugins, or firewall rules on certain sites.

In **v1.1**, the authentication now happens directly on your own WordPress site using a local REST API endpoint. This means:

- **No external server dependency** — the OAuth flow runs entirely on your site, so Cloudflare and security plugins won't interfere with authentication.
- **Longer-lasting tokens** — short-lived tokens are now automatically exchanged for long-lived tokens (~60 days), so your connection stays active longer before needing re-authentication.
- **New callback URL** — your redirect URI changes from the FlowMattic API server to your own site's REST API (e.g., `https://yoursite.com/wp-json/flowmattic/v1/auth/facebook-pages`).

---

## Prerequisites

- FlowMattic plugin (latest version)
- **Facebook Pages integration v1.1** or later (installed via FlowMattic > Integrations)
- An existing Facebook App (or you can create a new one)
- Admin access to your WordPress site
- Admin access to [Facebook Developers](https://developers.facebook.com/)

---

## Step 1: Update the Facebook Pages Integration

The Facebook Pages integration is **not bundled** with the FlowMattic core plugin — it is installed and updated separately from the Integrations page.

1. In your WordPress admin, go to **FlowMattic > Integrations**.
2. Search for **Facebook Pages**.
3. If you already have it installed, click **Update** to get version 1.1 (or later). If you don't have it installed yet, click **Install**.
4. Once updated, the integration version should show **1.1** or higher.

After updating, the connect dialog will automatically show the new REST API callback URL.

---

## Step 2: Get Your New Redirect URI

1. In your WordPress admin, go to **FlowMattic > Connects**.
2. Click **Add New Connect** and search for **Facebook Pages**.

![new integration connect for facebook pages .png](/storage/kb-images/89726e5471-inline.png)

3. Click on **Facebook Pages**. You will see the **Connect App** dialog with the new **Callback or Redirect URL** pre-filled.

![FlowMattic connects new facebook pages connect.png](/storage/kb-images/52ab424900-inline.png)

4. **Copy the Callback URL** shown in the dialog. It will look like:
   ```
   https://yoursite.com/wp-json/flowmattic/v1/auth/facebook-pages
   ```
   > **Note:** The exact URL depends on your site domain. For example, if your site is `https://tryflowmattic.work`, the callback URL will be `https://tryflowmattic.work/wp-json/flowmattic/v1/auth/facebook-pages`.

---

## Step 3: Update Facebook App OAuth Settings

1. Go to [Facebook Developers](https://developers.facebook.com/) and open your Facebook App.
2. Navigate to **App Settings > Basic** or find **Facebook Login > Settings** in the left sidebar.
3. Under **Client OAuth Settings**, locate the **Valid OAuth Redirect URIs** field.

![FlowMattic - Facebook Login for Business - Meta for Developers oauth URIs.png](/storage/kb-images/dea2538f65-inline.png)

4. **Add your new redirect URI** (the one you copied in Step 2):
   ```
   https://yoursite.com/wp-json/flowmattic/v1/auth/facebook-pages
   ```
5. You can optionally **remove the old redirect URI** (`https://api.flowmattic.com/facebook-pages`) if you no longer need it.
6. Click **Save Changes**.

> **Important:** The redirect URI must match **exactly** — including the protocol (`https://`), domain, and path. Make sure there are no trailing slashes or extra characters.

---

## Step 4: Note Your App Credentials

While you are in the Facebook Developers dashboard:

1. Go to **App Settings > Basic**.
2. Note down your **App ID** (this is the Client ID).
3. Note down your **App Secret** (this is the Client Secret). Click "Show" to reveal it.

---

## Step 5: Create a New Connection in FlowMattic

1. Back in the FlowMattic **Connect App: Facebook Pages** dialog (from Step 2):
   - **Connect Name**: Enter a name (e.g., `Facebook Pages`).
   - **Client ID**: Paste your Facebook App ID.
   - **Client Secret**: Paste your Facebook App Secret.
2. Click **Authenticate & Save Connect**.
3. A popup window will open and redirect you to Facebook's authorization page.
4. **Log in** to your Facebook account (if not already logged in).
5. **Select the Facebook Pages** you want to grant access to.
6. **Grant the requested permissions** (manage posts, read engagement, manage metadata, etc.).
7. The popup will show a success message and close automatically.

---

## Step 6: Update Existing Workflows

If you had workflows using the old Facebook Pages connection:

1. Go to **FlowMattic > Workflows**.
2. Open each workflow that uses Facebook Pages.
3. In the Facebook Pages step, update the **Connect** dropdown to select the new connection you created in Step 5.
4. Save the workflow.
5. Repeat for **all workflows** that use the old Facebook Pages connection.

---

## Step 7: Delete the Old Connection

After you have successfully updated **all** your workflows to use the new connection, you **must** delete the old connection to avoid conflicts.

1. Go to **FlowMattic > Connects**.
2. Find the old Facebook Pages connection (the one created with the previous v1.0 authentication method).
3. Click the **Delete** button on the old connection.
4. Confirm the deletion when prompted.

> **Note:** Any scheduled token refresh cron jobs associated with the old connection will be automatically cleaned up when the connection is deleted — no manual action needed.

> **Important:** Do **not** delete the old connection until you have updated all workflows to use the new one. Deleting a connection that is still in use by active workflows will cause those workflows to fail.

---

## Troubleshooting

### "URL Blocked" or "Redirect URI mismatch" error
- Make sure the redirect URI in your Facebook App settings **exactly matches** the one shown in the FlowMattic connect dialog.
- Ensure your site uses HTTPS (Facebook requires it).
- Check that **Use Strict Mode for redirect URIs** is set to **Yes** in Facebook App settings, and the URI is added correctly.

### "Can't Load URL" error
- Verify that your site's domain is added to the **Allowed Domains for the JavaScript SDK** in your Facebook App settings.
- Make sure the WordPress REST API is accessible on your site (not blocked by security plugins or server rules).

### Authentication popup closes without connecting
- Check your browser's popup blocker settings.
- Look in the WordPress debug log (`wp-content/debug.log`) for any PHP errors.
- Ensure your site's REST API is working by visiting `https://yoursite.com/wp-json/flowmattic/v1/auth/facebook-pages` directly — you should see an error message about missing parameters (this confirms the endpoint is active).

### Token expired after ~60 days
- Long-lived user tokens last approximately 60 days. When they expire, you will need to re-authenticate by editing the connection and clicking **Authenticate & Save Connect** again.
- **Page access tokens** derived from a long-lived user token do not expire, so your workflows will continue working as long as the user token is valid.

---

## FAQ

**Q: Do I need to create a new Facebook App?**
A: No. You can use your existing Facebook App. You just need to add the new redirect URI to the Valid OAuth Redirect URIs list.

**Q: Will my existing workflows stop working?**
A: Your existing workflows will continue to work with the old connection until the access token expires. However, we recommend migrating to the new connection as soon as possible, since the old API server endpoint may be deprecated in the future.

**Q: What permissions does the integration request?**
A: The integration requests the following Facebook permissions:
- `pages_show_list` — View your list of Pages
- `pages_read_engagement` — Read Page engagement data
- `pages_manage_posts` — Create, edit, and delete Page posts
- `pages_manage_engagement` — Manage Page engagement
- `pages_read_user_content` — Read user-generated content on Pages
- `pages_manage_metadata` — Manage Page metadata and subscribe to webhooks

**Q: Why was the authentication method changed?**
A: The previous method routed the OAuth flow through the FlowMattic API server, which could sometimes be blocked by Cloudflare, security plugins, or firewall rules on your site. The new REST API-based method handles the entire authentication directly on your own WordPress site, bypassing these potential blocking issues and ensuring a more reliable connection experience.

---

# My generated PDF looks different from the editor preview

Source: https://support.flowmattic.com/kb/article/198/my-generated-pdf-looks-different-from-the-editor-preview

## Symptom

The PDF your workflow generates does not match what you designed in the PDF Template Builder. Fonts, spacing, gradients, charts, or complex layouts look slightly different in the finished file than they did on the canvas.

## Cause

FlowMattic can render PDFs with two different engines, and they lay pages out slightly differently:

- **Cloudflare Browser Rendering** uses a real Chrome browser, so it reproduces modern CSS — gradients, flexbox, web fonts, charts — exactly as the editor shows it.
- **The bundled mPDF engine** is a self-contained PHP renderer used when Cloudflare credentials are not configured, or as an automatic fallback when a Cloudflare render fails. It is reliable and needs no setup, but it interprets complex CSS, custom fonts, and gradients more conservatively than Chrome.

If your credentials are not set, every PDF is produced by mPDF, which is the most common reason the output differs from the on-screen design.

## Fix

**1. Configure Cloudflare Browser Rendering for pixel-accurate output.**
Add a Cloudflare Account ID and API Token under **FlowMattic → Settings → Cloudflare**. Once configured, PDF generation uses real Chrome and matches the editor. See *Set up Cloudflare Browser Rendering*. The Cloudflare tab shows a green confirmation when the credentials are valid.

**2. Confirm which engine ran.**
When a Cloudflare render fails mid-run, FlowMattic automatically falls back to mPDF so your workflow still produces a file, and it records the Cloudflare error in the WordPress error log. If output quality changed unexpectedly, check the error log for a Cloudflare failure — a temporary API issue or an exhausted render quota can trigger the fallback.

![The WordPress error log (or a logging plugin's viewer) showing a line that mentions the Cloudflare PDF renderer falling back to mPDF.](https://assets.infidesk.support/kb/inline/2026/07/uCRKEQRth7gzFmCHeuujPN5ABWrYOw8tQo5YS4N8.png)

**3. Use the bundled fonts.**
Set the document's fonts from the built-in catalog under **Page settings → Fonts** (the **Body**, **Heading**, and **Mono** dropdowns) rather than relying on a system font name. The bundled Google Fonts have their font files shipped with the plugin, so they render identically in both engines. A font that is not bundled may be substituted by mPDF.

**4. Re-test after any change.**
Regenerate the PDF from the workflow after changing settings — the editor preview and the mPDF fallback are separate rendering paths, so the only way to confirm the final result is to run the step that produces the file.

## When mPDF is the right choice

If you do not need pixel-perfect output — for example a plain text-and-table invoice — the mPDF engine is perfectly usable and requires no external service. In that case the small layout differences are expected, and no action is needed.

---

# My workflow does not run when a form is submitted

Source: https://support.flowmattic.com/kb/article/187/my-workflow-does-not-run-when-a-form-is-submitted

## Symptom

A form submission is stored in the form's Responses, but the workflow you built on it does not run.

## Cause and fix

### The workflow is scoped to a different form

The New Form Submission trigger is usually scoped to a specific form. If the trigger points at a different form than the one being submitted, it will not fire.

**Fix:** open the workflow's trigger settings and confirm the selected form matches the form you are testing. If you want the workflow to run for every form, set the trigger to **Any Form**.

### The workflow is turned off

A workflow only runs when it is enabled.

**Fix:** open the workflow and confirm it is turned on. A newly built workflow is often left off until you finish it.

### No test submission was captured

If you never captured a sample submission, the trigger has no field structure to work with and downstream steps have nothing to map.

**Fix:** submit a test entry, then click **Capture Response** so the workflow sees the fields. Re-map any action fields against the captured data.

### The submission did not actually complete

If a submission failed validation, was blocked by reCAPTCHA, or hit a submission limit, no trigger fires because there is no stored submission.

**Fix:** confirm the entry appears on the form's **Responses** screen. If it is not there, the submission did not complete — check required fields, reCAPTCHA keys, and any submission caps or close date.

![Workflow trigger settings with the selected form and the enabled toggle](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-form-builder-wf-form-trigger-settings.png)

## How to confirm the trigger works

Submit a test entry and open the workflow's run history. A completed submission on the correctly scoped, enabled workflow produces a run there. If a run appears but a later step failed, the issue is in that step's configuration, not the trigger.

---

# New Item in Multiple RSS Feeds Trigger (RSS Feed Integration)

Source: https://support.flowmattic.com/kb/article/165/new-item-in-multiple-rss-feeds-trigger-rss-feed-integration

The **New Item in Multiple RSS Feeds** trigger lets a single FlowMattic workflow watch many RSS feeds at once and fire whenever any of them publishes a new item. It belongs to FlowMattic's built-in **RSS Feed** app, and it replaces the old "one workflow per feed" approach so you can manage dozens of feeds from one place.

## What the RSS Feed app provides

The **RSS Feed** integration is a core FlowMattic app (no external account required). It offers two triggers and two actions:

- **New Item in RSS Feed** — watches a single feed URL.
- **New Item in Multiple RSS Feeds** — watches several feed URLs from one workflow (the focus of this guide).
- **Create New Item in RSS Feed** (action) — publishes an item into a custom feed hosted by your site.
- **Retrieve RSS Feed Items** (action) — fetches the current items from a feed on demand.

Both triggers use **API polling**, meaning FlowMattic checks the feeds on a schedule rather than waiting for the feed to notify it (RSS feeds have no way to push notifications).

![The RSS Feed app trigger picker showing "New Item in RSS Feed" and "New Item in Multiple RSS Feeds](https://assets.infidesk.support/kb/inline/2026/07/sP0WotyRKcX0gUnZIOmJ77mtoqZRBhczJBZkdTzz.png)

## How it differs from the single-feed trigger

The single **New Item in RSS Feed** trigger has one **RSS Feed URL** text box and remembers only the last seen item for that one feed. If you wanted to watch ten blogs, you needed ten workflows.

The **New Item in Multiple RSS Feeds** trigger instead gives you one large **RSS Feed URLs** box where you paste many feed addresses. On every poll it loops through all of them, tracks each feed separately, and runs the workflow once per new item found in any feed. It also adds a **feed_url** field to the data so each run tells you which feed the new item came from.

## Setting up the trigger

### Choosing the app and event

When you add the trigger step, select the **RSS Feed** app, then choose **New Item in Multiple RSS Feeds** as the event.

### RSS Feed URLs

This is the only required field. It is a multi-line text area (not a repeatable row), and the rule is simple: **enter one RSS Feed URL per line.** The in-app helper text states *"Enter one RSS Feed URL per line. All feeds will be checked on each polling interval."*

For example:

```
https://example.com/blog/feed
https://news.example.org/rss
https://podcast.example.net/feed.xml
```

Blank lines and surrounding spaces are ignored, so accidental empty lines won't break anything. Each URL should be a publicly reachable RSS or Atom feed.

![The trigger configuration panel with the "RSS Feed URLs" textarea filled with several feed URLs, one per line](https://assets.infidesk.support/kb/inline/2026/07/mibAG6sxHJA7vhE2wmOlO77anhrQ2f3AVHcZkQDz.png)

### Connection (Connect)

The trigger requires a **Connect** to be selected. For most public feeds you can pick the **None / no-auth** option. If your feeds sit behind authentication (Bearer token, Basic auth, an API key header, or OAuth), choose a matching Connect and FlowMattic will attach the right authorization header to every feed request. The same Connect is applied to all feeds in the list.

### Polling Frequency

Because this is a polling trigger, FlowMattic shows a **polling frequency** option that controls how often all the feeds are checked. The available choices are **1 Minute, 2 Minutes, 5 Minutes, 10 Minutes, 15 Minutes, 30 Minutes, 1 Hour, 2 Hours, 3 Hours, 6 Hours, 12 Hours, and 1 Day** (the default is 10 minutes). Every feed in the box is checked on each run of this schedule, so set it to a comfortable interval if you list many feeds.

![The polling frequency dropdown showing options from 1 Minute up to 1 Day](https://assets.infidesk.support/kb/inline/2026/07/tCubmXkpQ4EZFsBfVzgwwrhD6XNYApW7aoj7ruI1.png)

### Save & Capture response

After entering the URLs, click **Save & Capture response** (it reads **Re-capture response** if you've captured before). During capture, FlowMattic fetches the **first** feed in your list and shows its newest item as sample data so you can map fields in later steps. At the same time, it quietly records the current newest item of **every** feed so that none of the existing items are treated as "new" on the first real run.

## How polling and duplicate detection work

### The first run sets a baseline

The very first time a feed is seen (during capture, or the first scheduled poll for a feed that has no record yet), FlowMattic stores the **title of that feed's current newest item** and does **not** trigger. This baseline prevents a flood of runs for items that already existed before you built the workflow.

### Per-feed tracking by URL

FlowMattic keeps a separate "last seen" record for each feed. Internally each feed is keyed by a hash of its URL, and the saved record holds the feed's URL plus its last newest-item title. Because tracking is per-feed, a busy feed and a quiet feed never interfere with each other.

### Detecting new items

On each scheduled poll, for every URL in the list FlowMattic:

1. Downloads and parses the feed's items (newest first).
2. Walks the items from the top and collects every item until it reaches the **title that matches the stored last-seen title** for that feed. That stored title is the stopping point, so only items newer than it are collected.
3. Updates the stored last-seen title for that feed to the new newest item.
4. Runs the workflow once for each new item, oldest-new-first (the collected items are reversed before running), so your downstream steps process them in chronological order.

This title-based comparison is how **already-seen items are skipped**: anything at or below the remembered title is ignored, so the same item never triggers twice. If a single feed fails to load on a given poll, FlowMattic simply skips that feed and continues checking the rest.

## What data each new item returns

Each new item runs the workflow with that item's fields flattened from the feed's XML. Field names are prefixed with **channel_item_**, and the exact set depends on what tags the source feed includes. Common fields you can map in later steps:

- **channel_item_title** — the item's title (also the value used for duplicate detection).
- **channel_item_link** — the item's URL.
- **channel_item_description** — the summary/excerpt.
- **channel_item_content_encoded** — the full HTML content, when the feed provides `content:encoded`.
- **channel_item_pubDate** — the published date.
- **channel_item_dc_creator** — the author, when the feed provides `dc:creator`.
- **channel_item_category** — the item's category/categories.
- **channel_item_guid** — the item's unique identifier.

Media-rich feeds (podcasts, image feeds) also surface enclosure or `media:content` / `media:thumbnail` details when present. Namespaced tags like `content:encoded`, `dc:creator`, and `media:thumbnail` are converted to underscore names (`content_encoded`, `dc_creator`, `media_thumbnail`) so they map cleanly.

In addition to the item fields, the multi-feed trigger always includes:

- **feed_url** — the exact feed URL (from your list) that this item came from.

Use **feed_url** to branch your workflow by source, label notifications, or route different feeds to different destinations.

![A captured item showing channel_item_title, channel_item_link, channel_item_description, channel_item_pubDate, and feed_url in the data list](https://assets.infidesk.support/kb/inline/2026/07/MYJBn7uzK8sDKnwaG8kfdYEF9RobP6Q839eaHps1.png)

## Things to keep in mind

- New items are matched by **title**. If a feed reuses or changes item titles, detection accuracy depends on those titles being distinct.
- Each feed must be **publicly reachable** (or reachable with the Connect you selected); a feed that 404s or errors is skipped for that poll, and FlowMattic moves on to the next one.
- All listed feeds share the **same polling frequency** and the **same Connect**. If different feeds need different authentication, use separate workflows.
- The sample data shown after capture comes from the **first** feed in your list, but at runtime any feed can trigger the workflow.

---

# Number Formatter

Source: https://support.flowmattic.com/kb/article/43/number-formatter

FlowMattic’s Number Formatter is a versatile tool designed to handle various number formatting requirements within your workflows. Whether you need to reformat numbers, process currency values, adjust decimal places, or modify phone number styles, the Number Formatter streamlines the process. By integrating this tool into your workflows, you can ensure that numerical data is consistently and correctly formatted for your specific needs.

The Number Formatter provides multiple action events, allowing you to tailor the formatting process based on the type of data you’re working with. This flexibility makes it a valuable addition to any automation involving numerical data.

#### **Step by Step Documentation for Text Formatter by FlowMattic:**

### 1\. Create a New Workflow

Go to the FlowMattic Dashboard, where you can manage and create workflows. To start a new workflow, click the **“New Workflow”** button located in the top-right corner of the Dashboard. This will begin the process of creating your new workflow

### 2\. Add the Number Formatter as an Action Step

- Click the “+” icon in your workflow to add a new action step.

- In the search bar that appears, type “Number Formatter” and select it from the list of available actions. This will add the Number Formatter to your workflow, allowing you to proceed with its configuration.

### 3\. Action Events Available in Number Formatter

Select an Action Event. In the “Action Event” section, choose from the following options:

**3.1 Format Number** : This action reformats the given number into a new style. Use this when you need to change the appearance or structure of numerical data to fit specific requirements.

**3.2 Format Phone Number** : This action formats a given phone number, allowing you to include or exclude the country code. It’s ideal for standardizing phone numbers in your database or communications.

**3.3 Format Currency** : This action adjusts the format of currency values, ensuring consistency across different workflows or applications. It’s particularly useful for financial data processing.

**3.4 Decimal Converter** : This action converts a given number to a different decimal format, allowing you to control the number of decimal places for your data. It’s helpful in calculations or data presentation.

**3.5 Minor Unit Conversion** : This action converts a given number to a different minor unit. For example, it can transform major currency units into minor units (e.g., dollars to cents), making it easier to perform specific calculations or analyses.

---

# OpenAI API + FlowMattic MCP Server Integration Guide

Source: https://support.flowmattic.com/kb/article/88/openai-api-and-flowmattic-mcp-server-integration-guide

## Overview

This guide demonstrates how to integrate FlowMattic MCP (Model Context Protocol) server with OpenAI's API, enabling your AI applications to access FlowMattic's powerful automation tools directly through OpenAI's Responses API. This integration allows you to combine OpenAI's language models with FlowMattic's workflow automation capabilities.

## Prerequisites

Before you begin, ensure you have:

- **OpenAI API account** with valid API key
- **FlowMattic MCP server** configured and running (Server ID: 72)
- **FlowMattic authentication token** for API access
- **Basic knowledge** of REST APIs and HTTP requests
- **Development environment** (for testing API calls)

## What You'll Achieve

After completing this integration, you'll be able to:
- Use OpenAI models with direct access to FlowMattic tools
- Execute FlowMattic workflows through natural language commands
- Combine AI reasoning with FlowMattic's automation capabilities
- Build applications that leverage both OpenAI and FlowMattic seamlessly
- Access FlowMattic data and triggers through conversational interfaces

---

## Integration Methods

### Method 1: Direct API Call (cURL Example)

This method uses direct HTTP requests to OpenAI's Responses API with FlowMattic MCP server configuration.

#### Step 1: Configure the API Request

Use the OpenAI Responses API with your FlowMattic MCP server by making a POST request to the responses endpoint:

```bash
curl --location 'https://api.openai.com/v1/responses' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer $OPENAI_API_KEY' \
--data '{
    "model": "gpt-4.1",
    "tools": [{
        "type": "mcp",
        "server_label": "flowmattic",
        "server_url": "{{flowmattic_mcp_server}}",
        "require_approval": "never",
        "headers": {
            "Authorization": "Bearer YOUR_TOKEN_HERE"
        }
    }],
    "input": "Run the tool to get my recent posts",
    "tool_choice": "required"
}'
```

#### Configuration Parameters Explained:

- **`model`**: Specifies the OpenAI model to use (gpt-4.1 recommended for complex tasks)
- **`tools`**: Array of available tools, including your FlowMattic MCP server
  - **`type`**: Always "mcp" for Model Context Protocol servers
  - **`server_label`**: Identifier for your FlowMattic server ("flowmattic")
  - **`server_url`**: Your FlowMattic MCP server endpoint
  - **`require_approval`**: Set to "never" for automatic tool execution
  - **`headers`**: Authentication headers for FlowMattic access
- **`input`**: Natural language instruction for the AI
- **`tool_choice`**: Set to "required" to ensure tool usage

#### Step 2: Customize Your Request

**Replace placeholders with your actual values:**

1. **OpenAI API Key**: Replace `$OPENAI_API_KEY` with your actual OpenAI API key
2. **FlowMattic Token**: Replace `YOUR_TOKEN_HERE` with your FlowMattic authentication token
3. **Server URL**: The `{{flowmattic_mcp_server}}` will be automatically populated with your server URL
4. **Input Message**: Modify the input to match your specific use case

**Example customized request:**
```bash
curl --location 'https://api.openai.com/v1/responses' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer sk-your-openai-api-key-here' \
--data '{
    "model": "gpt-4.1",
    "tools": [{
        "type": "mcp",
        "server_label": "flowmattic",
        "server_url": "https://yoursite.com/wp-json/flowmattic/v1/mcp",
        "require_approval": "never",
        "headers": {
            "Authorization": "Bearer your-flowmattic-token"
        }
    }],
    "input": "Create a new workflow to send welcome emails to new subscribers",
    "tool_choice": "required"
}'
```

---

### Method 2: Python SDK Integration

This method uses the OpenAI Python SDK for easier integration in Python applications.

#### Step 1: Install the OpenAI Python SDK

First, install the OpenAI Python library:

```bash
pip install openai
```

#### Step 2: Implement the Integration

Create a Python script to integrate OpenAI with FlowMattic MCP server:

```python
import openai

# Initialize the OpenAI client
client = openai.OpenAI(api_key="your-openai-api-key")

# Make a request with FlowMattic MCP server integration
response = client.responses.create(
    model="gpt-4.1",
    tools=[{
        "type": "mcp",
        "server_label": "flowmattic",
        "server_url": "{{flowmattic_mcp_server}}",
        "require_approval": "never",
        "headers": {
            "Authorization": "Bearer YOUR_TOKEN_HERE"
        }
    }],
    input="Use FlowMattic to get my recent posts",
    tool_choice="required"
)

# Process the response
print(response)
```

#### Step 3: Enhanced Python Implementation

For production applications, consider this more robust implementation:

```python
import openai
import os
from typing import Dict, List, Optional

class FlowMatticOpenAIIntegration:
    def __init__(self, openai_api_key: str, flowmattic_token: str, flowmattic_server_url: str):
        """
        Initialize the FlowMattic-OpenAI integration
        
        Args:
            openai_api_key: Your OpenAI API key
            flowmattic_token: Your FlowMattic authentication token
            flowmattic_server_url: Your FlowMattic MCP server URL
        """
        self.client = openai.OpenAI(api_key=openai_api_key)
        self.flowmattic_config = {
            "type": "mcp",
            "server_label": "flowmattic",
            "server_url": flowmattic_server_url,
            "require_approval": "never",
            "headers": {
                "Authorization": f"Bearer {flowmattic_token}"
            }
        }
    
    def execute_flowmattic_task(self, 
                               instruction: str, 
                               model: str = "gpt-4.1",
                               additional_tools: Optional[List[Dict]] = None) -> Dict:
        """
        Execute a task using FlowMattic tools through OpenAI
        
        Args:
            instruction: Natural language instruction for the AI
            model: OpenAI model to use
            additional_tools: Optional additional tools to include
            
        Returns:
            Response from OpenAI API
        """
        tools = [self.flowmattic_config]
        if additional_tools:
            tools.extend(additional_tools)
        
        try:
            response = self.client.responses.create(
                model=model,
                tools=tools,
                input=instruction,
                tool_choice="required"
            )
            return response
        except Exception as e:
            print(f"Error executing FlowMattic task: {e}")
            return {"error": str(e)}

# Usage example
if __name__ == "__main__":
    # Initialize with your credentials
    integration = FlowMatticOpenAIIntegration(
        openai_api_key=os.getenv("OPENAI_API_KEY"),
        flowmattic_token=os.getenv("FLOWMATTIC_TOKEN"),
        flowmattic_server_url=os.getenv("FLOWMATTIC_MCP_SERVER_URL")
    )
    
    # Execute a task
    result = integration.execute_flowmattic_task(
        "Check my recent WordPress posts and create a summary report"
    )
    
    print("Task Result:", result)
```

---

## Advanced Configuration

### Environment Variables Setup

For security and flexibility, use environment variables:

```bash
# .env file
OPENAI_API_KEY=sk-your-openai-api-key-here
FLOWMATTIC_TOKEN=your-flowmattic-authentication-token
FLOWMATTIC_MCP_SERVER_URL=https://yoursite.com/wp-json/flowmattic/v1/mcp
```

### Tool Configuration Options

#### Approval Settings
```json
{
    "require_approval": "never",    // Automatic execution
    "require_approval": "always",   // Manual approval required
    "require_approval": "auto"      // AI decides based on context
}
```

#### Custom Headers
```json
{
    "headers": {
        "Authorization": "Bearer YOUR_TOKEN_HERE",
        "X-Custom-Header": "custom-value",
        "User-Agent": "MyApplication/1.0"
    }
}
```

#### Multiple Tool Integration
```python
tools = [
    {
        "type": "mcp",
        "server_label": "flowmattic",
        "server_url": "{{flowmattic_mcp_server}}",
        "require_approval": "never",
        "headers": {"Authorization": "Bearer FLOWMATTIC_TOKEN"}
    },
    {
        "type": "mcp",
        "server_label": "other_service",
        "server_url": "https://other-service.com/mcp",
        "require_approval": "auto",
        "headers": {"Authorization": "Bearer OTHER_TOKEN"}
    }
]
```

---

## Use Cases and Examples

### 1. Content Management
```python
# Get recent posts and create social media content
instruction = "Get my 5 most recent WordPress posts from FlowMattic and create engaging social media posts for each one"

response = integration.execute_flowmattic_task(instruction)
```

### 2. Workflow Automation
```python
# Trigger a FlowMattic workflow based on conditions
instruction = "Check if there are any new contact form submissions in the last hour, and if so, trigger the welcome email workflow"

response = integration.execute_flowmattic_task(instruction)
```

### 3. Data Analysis
```python
# Analyze FlowMattic data and generate reports
instruction = "Analyze the performance data from my e-commerce workflows in FlowMattic and create a monthly performance report"

response = integration.execute_flowmattic_task(instruction)
```

### 4. Integration Management
```python
# Manage integrations through natural language
instruction = "Create a new FlowMattic workflow that connects my contact form to my email marketing service and Slack notifications"

response = integration.execute_flowmattic_task(instruction)
```

---

## Error Handling and Troubleshooting

### Common Issues and Solutions

#### Authentication Errors
```python
# Handle authentication issues
try:
    response = client.responses.create(...)
except openai.AuthenticationError as e:
    print(f"OpenAI Authentication failed: {e}")
except Exception as e:
    if "unauthorized" in str(e).lower():
        print("FlowMattic token may be invalid or expired")
```

#### Connection Issues
```python
# Handle connection problems
import requests
from requests.exceptions import ConnectionError, Timeout

def test_flowmattic_connection(server_url: str, token: str) -> bool:
    """Test if FlowMattic MCP server is accessible"""
    try:
        headers = {"Authorization": f"Bearer {token}"}
        response = requests.get(f"{server_url}/health", headers=headers, timeout=10)
        return response.status_code == 200
    except (ConnectionError, Timeout):
        return False
```

#### Rate Limiting
```python
import time
from openai import RateLimitError

def execute_with_retry(client, **kwargs):
    """Execute request with retry logic for rate limits"""
    max_retries = 3
    for attempt in range(max_retries):
        try:
            return client.responses.create(**kwargs)
        except RateLimitError:
            if attempt == max_retries - 1:
                raise
            wait_time = (2 ** attempt) * 1  # Exponential backoff
            time.sleep(wait_time)
```

### Debugging Tips

1. **Enable verbose logging**:
   ```python
   import logging
   logging.basicConfig(level=logging.DEBUG)
   ```

2. **Test components separately**:
   - Test OpenAI API access independently
   - Verify FlowMattic MCP server connectivity
   - Validate authentication tokens

3. **Monitor API usage**:
   - Track OpenAI API usage and costs
   - Monitor FlowMattic server performance
   - Log successful and failed requests

---

## Security Best Practices

### API Key Management
- Store API keys in environment variables or secure vaults
- Never commit API keys to version control
- Rotate keys regularly
- Use different keys for development and production

### Token Security
- Secure FlowMattic authentication tokens
- Implement token refresh mechanisms
- Monitor for unauthorized API usage
- Use HTTPS for all communications

### Access Control
```python
# Implement access control for sensitive operations
ALLOWED_OPERATIONS = [
    "get_posts",
    "create_workflow",
    "send_notification"
]

def validate_operation(instruction: str) -> bool:
    """Validate if the requested operation is allowed"""
    # Implement your validation logic
    return any(op in instruction.lower() for op in ALLOWED_OPERATIONS)
```

---

## Performance Optimization

### Caching Strategies
```python
import functools
import time

@functools.lru_cache(maxsize=100)
def cached_flowmattic_request(instruction_hash: str):
    """Cache FlowMattic responses for repeated requests"""
    # Implementation depends on your caching strategy
    pass
```

### Batch Operations
```python
def batch_flowmattic_operations(instructions: List[str]) -> List[Dict]:
    """Process multiple FlowMattic operations efficiently"""
    results = []
    for instruction in instructions:
        result = integration.execute_flowmattic_task(instruction)
        results.append(result)
        time.sleep(0.1)  # Rate limiting
    return results
```

### Async Processing
```python
import asyncio
import aiohttp

async def async_flowmattic_request(instruction: str):
    """Asynchronous FlowMattic request processing"""
    # Implement async version for high-throughput applications
    pass
```

---

## Monitoring and Analytics

### Request Tracking
```python
import uuid
from datetime import datetime

class RequestTracker:
    def __init__(self):
        self.requests = []
    
    def log_request(self, instruction: str, response: Dict):
        """Log request for analytics"""
        self.requests.append({
            "id": str(uuid.uuid4()),
            "timestamp": datetime.now(),
            "instruction": instruction,
            "success": "error" not in response,
            "response_size": len(str(response))
        })
```

### Performance Metrics
```python
def calculate_metrics(requests: List[Dict]) -> Dict:
    """Calculate performance metrics"""
    total_requests = len(requests)
    successful_requests = sum(1 for r in requests if r["success"])
    success_rate = successful_requests / total_requests if total_requests > 0 else 0
    
    return {
        "total_requests": total_requests,
        "success_rate": success_rate,
        "average_response_time": calculate_avg_response_time(requests)
    }
```

---

## Additional Resources

- [OpenAI API Documentation](https://platform.openai.com/docs/api-reference) - Complete OpenAI API reference
- [FlowMattic MCP Documentation](https://support.flowmattic.com/kb/article/72/) - FlowMattic MCP integration guide
- [MCP Protocol Specification](https://modelcontextprotocol.io/specification) - Technical details about Model Context Protocol
- [OpenAI Python SDK](https://pypi.org/project/openai/) - Official Python library documentation

---

## Next Steps

After successfully integrating OpenAI API with FlowMattic MCP server:

1. **Explore advanced AI applications** - Build conversational interfaces for workflow management
2. **Implement custom tools** - Create specialized FlowMattic tools for your specific use cases
3. **Scale your integration** - Deploy to production with proper monitoring and error handling
4. **Build user interfaces** - Create web or mobile apps that leverage this integration
5. **Share your experience** - Contribute to the community with your implementations and use cases

Your OpenAI-powered applications can now seamlessly interact with FlowMattic's automation capabilities, opening up endless possibilities for AI-driven workflow management and automation.

---

# Outgoing Webhook

Source: https://support.flowmattic.com/kb/article/23/outgoing-webhook

An outgoing webhook is a way for a web application to send automated messages or information to another web application or third-party service. It allows the user to specify what data should be sent, when it should be sent, and how it should be formatted. Outgoing webhooks are typically used to trigger external events or perform specific actions in response to changes within a web application.

For example, a user can create a workflow that triggers when a new order is created on their website. They can set up an outgoing webhook to send the order details to a shipping provider or a customer relationship management (CRM) system, automating the process and reducing manual work.

**Step-by-Step Documentation for Outgoing Webhook:**

1. To create a new workflow on FlowMattic in WordPress, you need to first log in to your WordPress dashboard and navigate to the FlowMattic -> Workflows. Now, click on the “New Workflow” button

 ![new-workflow.jpeg](/storage/kb-images/3430a09ed7-inline.png)

2. Configure your trigger app, eg. Webhook and capture the response.
3. Next, add a new step by clicking the plus icon and choose the app as "Outgoing Webhook" -

 
 ![choose-webhook-outgoing.jpeg](/storage/kb-images/33f19cb2b2-inline.png)

5. After selecting "Outgoing Webhook," choose "Submit Data to Webhook" as the action event you want to perform.

4. Enter the URL of the 3rd party app that accepts webhooks in the provided field. This is where the data will be sent.

 
 ![outgoing-webhook-url.jpeg](/storage/kb-images/0aaf6174f5-inline.png)

5. Enter the data parameters as key and value pairs. These parameters can include information you want to send to the 3rd party app, such as names, addresses, or other data points.

 
 ![outgoing-webhook-parameters.jpeg](/storage/kb-images/e6c6a9d323-inline.png)

6. Once you have entered the webhook URL and data parameters, save the action and test it to ensure that data is being sent successfully to the 3rd party app. If the test is successful, you have successfully set up an outgoing webhook.

7. Finally, click on the “Save and Close” button to save the Outgoing Webhook module settings and close the settings popup
 
 ![outgoing-webhook-save-test.jpeg](/storage/kb-images/1f1b052f9b-inline.png)

## **Conclusion**

outgoing webhooks are a powerful tool that enables users to send data out from a workflow to a third-party application. With FlowMattic, the process of creating an outgoing webhook is straightforward and can be completed in a few simple steps. By choosing the application, selecting the webhook outgoing option, entering the webhook URL, and configuring the data parameters, users can quickly and easily create and test outgoing webhooks to enhance their workflows. Overall, outgoing webhooks offer a streamlined way to automate and integrate various applications and workflows, saving time and improving efficiency.

---

# Parse PDF Files in Your Workflows

Source: https://support.flowmattic.com/kb/article/245/parse-pdf-files-in-workflows

The **PDF Parser** integration reads PDF files inside your workflows — extract their text, read their metadata, search them, or pull out the images. A typical pairing: an email trigger with a PDF attachment, PDF Parser to read it, and an AI step to act on the contents.

## The four actions

Add a **PDF Parser** step and pick the action:

![The PDF Parser's four actions in the Action Event picker](https://assets.infidesk.support/products/flowmattic/kb-images/release-72-apps/pdfp-01-actions.png)

- **Parse PDF** — extracts the document's text, with an optional per-page breakdown and the document metadata included.
- **Get PDF Metadata** — reads the title, author, subject, keywords, producer, dates and page count *without* extracting text. Fast, and works on scanned files too.
- **Search PDF Text** — finds a term or phrase in the document and reports each match with its page number and surrounding context.
- **Extract Images from PDF** — pulls embedded images out and saves them to the Media Library.

## Pointing it at a PDF

Every action takes the same source field: a **PDF file URL or a Media Library attachment ID**. Map it from a previous step — an email attachment URL, a form upload, a webhook field — or paste a fixed URL.

![Parse PDF configured with a file URL and a page range](https://assets.infidesk.support/products/flowmattic/kb-images/release-72-apps/pdfp-02-configure.png)

**Parse PDF** options: a **Page Range** (`1-3`, `2,5,7`, or empty for the whole document) and **Include Per-Page Text**, which adds a page-by-page breakdown next to the combined text.

**Search PDF Text** options: the term, **Match Type**, **Case Sensitive**, how many **Context Characters** to include around each hit, and a page range.

## Scanned PDFs — read this before you rely on it

PDF Parser reads the **text layer** of a PDF. A scanned document is a photograph of a page — it has no text layer, and **there is no OCR**, so Parse PDF and Search cannot read it. Instead of failing silently, the parser tells you: the response comes back with `status_code: scanned_pdf` and a message explaining the situation.

The workflow-friendly way around it:

1. Run **Extract Images from PDF** — this works on scanned files, since the scan itself is an image.
2. Pass the extracted images to an **AI vision step** (an AI Agent or AI action with a vision-capable model) and let it read the pages.

**Get PDF Metadata** also works fine on scanned files — the metadata lives outside the text layer.

## Good to know

- **Check `status_code` in your workflow.** `parsed` means text was read; `scanned_pdf` means there was nothing to read — a Router can branch on it and take the vision path automatically.
- **Extract Images recovers JPEG, RGB, grayscale and palette images.** Exotic encodings — CMYK, JPEG 2000, fax-encoded — are reported as skipped rather than failing the step.
- **Password-protected PDFs cannot be read** — remove the protection first.

---

# PDF Builder

Source: https://support.flowmattic.com/kb/article/196/pdf-builder

PDF Builder is FlowMattic's document engine. You design a PDF once in the visual PDF Template Builder, then any workflow can fill that template with live data and produce a finished PDF file — an invoice, receipt, quote, contract, certificate, or report — and drop it into the WordPress Media Library for the next step to use.

## How it works

PDF Builder has two parts that work together:

1. **The PDF Template Builder** — a visual editor under **FlowMattic → PDF Templates**. You lay out the document, add the elements it needs, and mark the parts that change per run as `{{tokens}}`.
2. **The PDF Builder workflow action** — a step you add to any workflow. It takes one of your saved templates, fills the tokens with data captured from earlier steps, renders the PDF, and returns the file's `url`, `path`, `attachment_id`, `file_size`, and `filename` for downstream steps.

Because the template is saved by ID, you design it once and reuse it across as many workflows as you like. Editing the template updates every workflow that renders it.

## What you can put on a template

The builder canvas supports a full set of document elements:

- **Text elements** — headings, paragraphs, and key-value pairs.
- **Tables and totals** — a Table element iterates over array data such as invoice line items, and a Totals element computes values with formulas like `sum`, `mul`, `count`, `avg`, `min`, and `max`.
- **Media and marks** — logos, images, dividers, signatures, QR codes, and barcodes.
- **Data visuals** — charts, alerts, and badges.

Any text element can contain `{{path.to.value}}` tokens, so a single element like `Invoice #{{invoice.number}}` renders with real data at run time.

## Rendering engines

FlowMattic renders PDFs one of two ways:

- **Cloudflare Browser Rendering** — a real Chrome browser on Cloudflare's edge. This is the pixel-accurate engine and is recommended for anything with complex CSS, gradients, charts, or custom fonts. See *Set up Cloudflare Browser Rendering*.
- **Bundled mPDF engine** — used automatically when Cloudflare credentials are not configured, and used as an automatic fallback if a Cloudflare render fails mid-run. It is fully self-contained and needs no setup.

## Page sizes and fonts

Templates use a Letter, A4, A5, or Legal page in portrait or landscape (the AI generator additionally offers Tabloid and A3). The builder ships with a curated set of Google Fonts (including Inter, Roboto, Open Sans, Lato, Poppins, Montserrat, Playfair Display, Merriweather, Lora, IBM Plex Serif, IBM Plex Mono, JetBrains Mono, and Fira Code) whose font files are bundled, so text renders identically in both engines.

## Where generated PDFs go

The workflow action gives you three save destinations:

- **Media Library** — creates an attachment post you can reuse in later steps (email attachment, cloud upload, CRM file field).
- **Media Library with a custom folder** — the same, organised into a folder path you define, which can include captured data.
- **Raw file** — written to `uploads/flowmattic-pdfs/` and returned as a URL, without creating an attachment post.

![The PDF Template Builder editor with a sample invoice open — the Components panel on the left, the canvas in the centre, and a table of line items on the page](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-pdf-template-builder-pdf-editor-overview.png)

---

# PDF Template Builder

Source: https://support.flowmattic.com/kb/article/159/pdf-template-builder

The PDF Template Builder is FlowMattic's visual, drag-and-drop designer for creating reusable PDF layouts such as invoices, receipts, quotes, certificates, and reports. You arrange content blocks on pages, fill them with elements (text, tables, images, charts, and more), connect those elements to live data using tokens, and then any workflow can render the template into a finished PDF with real values. You manage templates under **FlowMattic → PDF Templates**.

## How the builder is organized

When you open a template for editing, the screen is split into four areas:

- **Toolbar** (top): template name, the Templates browser, the Edit/Preview switch, Jaadu (the in-builder AI assistant), Undo/Redo, Export, Save, and Close.
- **Left panel**: two tabs — **Components** (the blocks and elements you drag onto the page) and **Pages** (a tree of every page plus the document Header and Footer).
- **Canvas** (centre): the page(s) you are designing, with a page thumbnail strip along the side.
- **Right panel**: the **Inspector** (settings for whatever is selected), **Styles**, and **Data** tabs.

![The full PDF Template Builder editor with the toolbar on top, Components/Pages panel on the left, the page canvas in the middle, and the Inspector panel on the right](https://assets.infidesk.support/kb/inline/2026/07/vgWUNsFSZIbayvneGyuhSEYJ2WHLkNtl7iwdzBuC.png).

## Creating a template

From **FlowMattic → PDF Templates**, click **New PDF Template**, give it a **Template Name** (for example "Invoice"), then choose a **Starting Point** — either a prebuilt template, a blank/sample layout, or **Generate with AI** (describe the document in plain English and the AI drafts a starter for you). The template then opens in the builder.

![The "New PDF Template" modal showing the Template Name field and the grid of starting points, including the "Generate with AI" title](https://assets.infidesk.support/kb/inline/2026/07/jZswAh2QCOrZfDrCdBXsoWdlyji1LWnNgmMgMotd.png).

## The document structure: pages, blocks, cells, elements

Every template is built from a simple hierarchy:

- A template has one or more **pages**.
- Each page holds a stack of **blocks**. A block is a horizontal row.
- Each block is split into **cells** (columns).
- Each cell holds one or more **elements** (the actual content).

This structure is what lets you build clean, column-based layouts — for example a logo on the left and invoice details on the right.

### Adding a block (row layout)

Open the **Components** tab in the left panel. At the top are the row layouts you drag onto the page:

- **Single** — one full-width column.
- **Two column** — two equal columns.
- **Three column** — three equal columns.
- **Uneven** — a wider column next to a narrower one (2 : 1).

Drag a layout from the panel onto the canvas. A drop zone appears between existing blocks so you can place it exactly where you want.

![The Components panel showing the row layout options (Single, Two column, Three column, Uneven) at the top, with a block being dragged onto the canvas](https://assets.infidesk.support/kb/inline/2026/07/SR116TkionesZ94IyPeiQpufeAdR6bib3m3zZd8P.png).

### Adding elements

Below the row layouts is the element palette, grouped into categories. Drag any element onto an empty cell, or onto a cell that already has content (cells can hold a stack of elements). You can also drag a block by its handle to reorder it, and use the row toolbar to **Duplicate** or **Delete** a block.

## The element types

The builder includes 26+ element types. Here is what each one does:

**Basics**
- **Heading** — a large title line.
- **Sub-heading** — a smaller secondary heading.
- **Text** — a paragraph of body copy. Supports inline `{{tokens}}`.
- **Link** — clickable text with a destination URL.
- **List** — a bulleted or numbered list; items can be typed or pulled from a data array.
- **Image** — an image by URL (the URL can be a token, so the image changes per run).
- **Logo** — your brand mark, either as a text **wordmark** or an uploaded/linked **image**.
- **Icon block** — an icon next to a title and description (handy for contact details like phone or email).
- **Pattern shape** — a decorative shape filled with a dots/stripes/grid/checker pattern, with an optional soft edge fade.
- **Waves** — a decorative wave band with selectable styles and colours.
- **Divider** — a thin horizontal rule.
- **Shape** — a rectangle, circle, or line you can colour and size.
- **Signature** — a signature line with a name and title.
- **Quote** — a styled pull quote with an optional citation.
- **Spacer** — adjustable vertical empty space.

**Data**
- **Table** — a multi-column table. Can repeat rows automatically from a data array, or use fixed static rows.
- **Totals** — a stacked list of label/value rows (subtotal, tax, total). Values can be tokens or live formulas.
- **Key / Value** — paired label-and-value lines, shown inline or stacked.
- **Graph** — a bar or line chart, from custom values or a bound data array.
- **Address** — a labelled block of address lines.

**Feedback**
- **Alert** — a coloured callout box (info, success, warn, danger).
- **Badge** — a small coloured pill label.
- **Card** — a bordered box grouping a title and body text.

**Codes**
- **QR code** — a QR code with an optional caption.
- **Barcode** — a barcode (Code 128 by default) with an optional caption.

![The element palette in the Components panel showing the grouped element tiles (Heading, Text, Table, Totals, QR code, etc.)](https://assets.infidesk.support/kb/inline/2026/07/plVBGaciLXWRkXUvO05nxDOvVk6GASLdjeVTKS4t.png).

## Editing an element with the Inspector

Click any element on the canvas. The right panel's **Inspector** tab shows the settings for that element. Settings vary by type, for example:

- **Text / Heading / Sub-heading** have a **Content** box plus **Size**, **Weight**, **Color**, and alignment (left/center/right/justify) controls.
- **Table** has a **Data binding** section (the **Repeat from** dropdown), a **Columns** editor (each column has a label, a data **key**, a **width**, and alignment), and — when not bound — a **Static rows** editor. Its **Style** section offers a **Header style** option and a **Zebra** striping toggle.
- **Totals** lets you add rows, each with a label and either a token value or a formula such as `sum(line_items.amount)`.
- **Spacing** (available on most elements) sets top and bottom padding.

![The Inspector panel for a Table element, showing the Repeat from binding and the Columns list with label, key, width, and alignment](https://assets.infidesk.support/kb/inline/2026/07/SHdpeGBKTuixLsfAYciRk1MyoxaLepyiFBDv6PRL.png).

## Binding dynamic data with tokens

Static text is fine for fixed labels, but most of a PDF should change per record. The builder uses **tokens** written as `{{path.to.value}}` — for example `{{invoice.number}}` or `{{company.email}}`. At render time each token is replaced with the matching value from the data passed in.

The **Data** tab in the right panel shows your template's sample data as a tree. The header reads `invoice.json · live sample`.

- **Drag** any field from the tree onto a text area, a table, an image, or the visibility "Field" box to bind it.
- **Click** a field to copy its `{{path}}` token to your clipboard so you can paste it anywhere.
- Use the **Edit** button to edit the full sample JSON, or **Upload** to load a `.json` file.

For tables, instead of dragging a single field you set **Repeat from** to a data array (such as `line_items`); the table then renders one row per array item, mapping each column's **key** to a field on the item.

This sample data does double duty: it drives the live Preview, and its top-level keys become the parameters your workflow fills in later. (See the companion guide on generating PDFs in workflows.)

![The Data tab showing the sample data tree with object, array, and field nodes, and the Edit/Upload buttons in the toolbar](https://assets.infidesk.support/kb/inline/2026/07/74wVhD8g2m7PmLgcfdJ9IWwWbzrEa3bCwyVowjLX.png).

To check your bindings, flip the toolbar switch from **Edit** to **Preview**. In Edit mode tokens appear as small chips; in Preview mode they resolve to the actual sample values.

## Conditional visibility (Show if)

Any element can be shown or hidden based on the data. At the bottom of an element's Inspector is the **Show if** section. Set the **Condition** dropdown to one of:

- **Always show** (the default) or **Never show (hidden)**.
- **Field is set (not empty)** / **Field is empty**.
- **Field is truthy** / **Field is falsy**.
- **Field equals…** / **Field does not equal…** (with a value to compare).
- **Field > value**, **Field ≥ value**, **Field < value**, **Field ≤ value**.

For any condition other than Always/Never, type or drag a data field into the **Field** box (for example `totals.coupon`). A live hint shows whether the element is currently **visible** or **hidden** with the sample data. This is how you hide a "Discount" row when there is no discount, or show a "Paid" badge only when the balance is zero.

![The "Show if" section in the Inspector with the Condition dropdown open and a Field path entered.](https://assets.infidesk.support/kb/inline/2026/07/uPQ3EWa0TabTbyNigBf76dqQFWZYqQskpqjhbWqH.png)

## Page settings

Click a page (or its entry in the Pages tab) to open **Page settings** in the Inspector. These are document-wide defaults:

- **Paper → Size**: Letter, A4, A5, or Legal.
- **Paper → Orientation**: Portrait or Landscape.
- **Margins**: Top, Bottom, Left, and Right, each in millimetres.
- **Fonts**: choose the **Body** font (body text, tables, addresses), the **Heading** font (headings, sub-headings, graph titles), and the **Mono** font (barcode captions and code-style labels).
- **Default Typography**: per-style defaults for Heading, Sub-heading, and Text (size, weight, colour, etc.), each with a Reset.
- **Header / footer**: quick **Show header** and **Show footer** toggles.

![The Page settings Inspector showing Paper (size + orientation), Margins in mm, and the Fonts dropdowns.](https://assets.infidesk.support/kb/inline/2026/07/ViuEkPcb3Xl6q2tYjv9QrPOemay0Gr3STjvz0PUM.png)

## Working with pages

Use the **Pages** tab (or the thumbnail strip) to navigate. You can **Add page**, and from a page's menu you can **Duplicate** or **Delete** it. The builder also auto-paginates: if a page's content grows past the page height, blocks that overflow are pushed onto the next page automatically (a new page is created if needed).

## Headers and footers

Headers and footers are managed separately from the page body. Open the **Pages** tab and click **Header** or **Footer** to edit them in the Inspector.

A header or footer is built from **rows**, and each row is split into **cells** — the same rows-and-cells idea as the page body. Each cell holds one element. The element types allowed in a header/footer are a curated subset: **Text**, **Icon block**, **Logo**, **Image**, **Divider**, **Spacer**, **Link**, and **Page number**.

Key controls in the header/footer Inspector:

- **Show** toggle — turn the header or footer on or off.
- **Add row**, then set each row's column count (1–4), and reorder, duplicate, or delete rows.
- For each cell, set its content element, horizontal alignment, and vertical alignment (top/middle/bottom).
- A **background** option (None, Solid, Gradient, Pattern, or Waves) for the whole band.
- A band-wide **text colour** that cascades into every text/icon element (leave empty to keep per-element colours).
- **Apply to** — which pages the band appears on: **All pages**, **Odd pages**, **Even pages**, or **First only**. The footer additionally offers **Last only** and **First and last only**.

For page numbering, add the **Page number** element (its format defaults to "Page {page} of {pages}"), or type the `{{page}}` and `{{pages}}` tokens inside a text element.

![The Footer Inspector showing a row with two cells, the Apply to dropdown, the background picker, and a Page number element](https://assets.infidesk.support/kb/inline/2026/07/tynfy6FElD7MXW9bqYz8JadBqXTb5yqtQXaHaXWE.png).

Cells in a header/footer can be bound to data too — drag a data field onto a text or logo/image field, or type a `{{path}}` token, so the band can show, for example, `{{company.name}}` on the left and an invoice number on the right.

## Saving and exporting

Click **Save** (or press Cmd/Ctrl + S) to store the template. Saving writes both the design and the current sample data, so the template is ready to be used in workflows. Use **Export** to download a PDF of the current design (rendered with the sample data) so you can check the final output. Press **Undo**/**Redo** (or Cmd/Ctrl + Z) to step through your changes; closing and reopening the builder starts a fresh history.

![The toolbar with the Save, Export, Edit/Preview switch, and Undo/Redo buttons highlighted.](https://assets.infidesk.support/kb/inline/2026/07/5mAHYK5ibTgMEncV1xuQDhhINAr0o7HYxzOHghKm.png)

---

# Plugin Structure

Source: https://support.flowmattic.com/kb/article/30/plugin-structure

FlowMattic is built to be a modular plugin, so it has two main parts - Core plugin and Integrations.

## Core Plugin

FlowMattic core plugin is packed with all the required features and core functionalities that are required to run the workflow, workflow editor, admin pages, Chatbot, Variables, Connects, Custom Apps, Task History and settings, etc.

The FlowMattic core has some core integrations as well that are part of the plugin and are pre-installed with FlowMattic. The core integrations includes -

- Maths

- Iterator Storage

- Iterator End

- PHP Functions

- RSS Feed

- Email Parser

- API Module

- Plugin Actions

- Text Formatter

- Filters

- Webpage Parser

- Schedule

- Iterator

- Email

- Webhooks

- Webhook Response

- Webhook Outgoing

- HARO Email Parser

- FlowMattic Tools

- CSV Parser

- API Polling

- FlowMattic Chatbot

- Delay

- Counter

- WordPress

- Router

- Date/Time Formatter

- Custom Action

- PHP Array

When you update the core plugin, all of the above integrations and features gets updated, as being part of the Core plugin.

## FlowMattic Integrations

Now, coming to the part that drives your interest - Integrations. FlowMattic integrations except the core ones, are not part of the plugin file you install. Meaning, no external integration is installed by default and is not available until you install it manually. To install the integration, you need to go to the Integrations admin page under the FlowMattic admin menu, then search for the integration you're looking for, and click the "Install" button. This will install the integration on your site. Once the integration is installed, it will be part of the FlowMattic ecosystem, and you can see the instances of the integration in Connect, Workflows, Task History, etc. where it is used.

Being separate from the Core plugin, you have the ability to delete or uninstall the integration that you don't need or you are no longer using. To make it simple, let's consider you installed an integration for Typeform, which you're using previously to collect submissions from your users. Now, you got a forms plugin installed in your site, like FluentForms, and created your forms using the forms plugin. Now, you switched your workflow trigger to the FluentForms ( Form plugin ), so you don't need the Typeform integration anymore, right? Just go to the integrations page and delete the integration. It will have no impact on your workflows unless you have not switched all your workflows. In case a workflow is still using that integration, it will be set to draft mode for the safer side and to avoid any workflow executions from failing due to the integration not available.

It helps us to maintain the integration updates without releasing the entire plugin update when we need to update any integration with new actions/triggers or bug fixes and improvements. We can update the integration without the entire plugin update. You just need to go to the Integrations page and click the update button next to the integration in the Updates tab if any is available. You will see a notification of the integration update availability in the dashboard.

---

# Real-world MCP Use Cases and Examples

Source: https://support.flowmattic.com/kb/article/93/real-world-mcp-use-cases-and-examples

# Real-world MCP Use Cases and Examples

FlowMattic MCP Server helps you automate everyday business tasks using FlowMattic workflows and popular service integrations. These practical examples use no coding - just FlowMattic's visual workflow builder and API connections.

## Overview

These use cases focus on common business automation using FlowMattic's existing integrations with popular services like Gmail, Slack, Google Drive, social media platforms, and more. Each example can be set up using FlowMattic's visual workflow builder - no coding required.

## Email and Communication Automation

### 1. Smart Email Notifications

**What it does**: Send professional email updates when important events happen on your site.

**Time saved**: 10-15 minutes per notification (5+ daily = 75 minutes saved)

**Setup**: FlowMattic Workflow + Gmail/SMTP integration

**MCP Tool**:
- **Name**: "Send Project Update Email"
- **Type**: Workflow
- **Integrations**: Gmail API + WordPress
- **Workflow**: Format data → Send via Gmail → Log to database

**Real Usage**:
```
You: "Send project update email to client about the website redesign - we completed the homepage design and it's ready for review"

AI: "✅ Project update email sent!

Email Details:
• To: client@company.com
• Subject: Website Redesign Update - Homepage Design Complete
• Content: Professional project update with:
  - Homepage design completion confirmation
  - Next steps (client review process)
  - Timeline for feedback (3 business days)
  - Direct link to preview the design

Email delivered successfully at 2:34 PM"
```

**Why it's useful**: Professional client updates without manually writing emails each time.

### 2. Slack Team Notifications

**What it does**: Send formatted notifications to Slack channels when specific events occur.

**Time saved**: 5 minutes per notification (8+ daily = 40 minutes saved)

**Setup**: FlowMattic Workflow + Slack integration

**MCP Tool**:
- **Name**: "Send Slack Alert"
- **Type**: Workflow  
- **Integrations**: Slack Webhook + WordPress
- **Workflow**: Format message → Send to Slack channel → Update log

**Real Usage**:
```
You: "Send alert to team that we have a new high-priority support ticket from VIP customer TechCorp"

AI: "🚨 Slack alert sent to #support-team:

VIP Customer Alert 🔥
• Customer: TechCorp (VIP)
• Priority: HIGH
• Issue: Login problems affecting 50+ users
• Ticket: #12847
• Assigned: Next available agent
• SLA: 1 hour response time

@channel please prioritize - VIP customer needs immediate attention

Sent to #support-team at 3:15 PM"
```

**Why it's useful**: Instant team alerts without manually posting to Slack.

### 3. Automated Follow-up Emails

**What it does**: Send follow-up emails based on customer actions or timelines.

**Time saved**: 8 minutes per follow-up (15+ weekly = 120 minutes saved)

**Setup**: FlowMattic Workflow + Email service integration

**MCP Tool**:
- **Name**: "Send Follow-up Email"
- **Type**: Workflow
- **Integrations**: Mailchimp/Gmail + CRM integration
- **Workflow**: Check timeline → Personalize content → Send email → Update CRM

**Real Usage**:
```
You: "Send follow-up email to Sarah Johnson - she downloaded our pricing guide 3 days ago but hasn't responded to our proposal"

AI: "📧 Follow-up email sent to Sarah Johnson:

Email Strategy: Soft follow-up with value add
• Subject: 'Quick question about your pricing requirements'
• Content highlights:
  - Referenced her downloaded pricing guide
  - Offered free 15-minute consultation
  - Included 2 relevant case studies
  - Clear, non-pushy call-to-action

• Delivery: Successful at 11:30 AM
• CRM updated: Follow-up #2 logged
• Next follow-up: Scheduled for 5 days (if no response)"
```

**Why it's useful**: Consistent follow-up without manually tracking timelines and writing emails.

## Social Media and Content Automation

### 4. Multi-Platform Social Media Posting

**What it does**: Post content to multiple social media platforms simultaneously with platform-optimized formatting.

**Time saved**: 15 minutes per post (5+ weekly = 75 minutes saved)

**Setup**: FlowMattic Workflow + Social media API integrations

**MCP Tool**:
- **Name**: "Post to Social Media"
- **Type**: Workflow
- **Integrations**: Twitter API + Facebook API + LinkedIn API
- **Workflow**: Format for each platform → Post simultaneously → Track engagement

**Real Usage**:
```
You: "Post about our new blog article 'WordPress Security Tips' - emphasize it's a free guide with 10 actionable tips"

AI: "📱 Multi-platform social media post published:

Twitter (240 chars):
'🔒 NEW: WordPress Security Guide! 10 actionable tips to protect your site from hackers. Free download ↓
#WordPressSecurity #WebSecurity'

LinkedIn (Professional):
'We've just published a comprehensive WordPress security guide. As cyber threats evolve, protecting your website has never been more critical. Our free guide covers 10 essential security measures every site owner should implement.'

Facebook (Engaging):
'Worried about website security? 🔐 Our new WordPress security guide gives you 10 simple steps to protect your site. Best part? It's completely free! Check it out and keep your website safe.'

✅ Posted to all platforms at 2:00 PM
📊 Tracking engagement across all channels"
```

**Why it's useful**: Reach all audiences without manually posting to each platform and reformatting content.

### 5. Content Calendar Updates

**What it does**: Automatically update your content calendar when new content is published or scheduled.

**Time saved**: 5 minutes per update (10+ weekly = 50 minutes saved)

**Setup**: FlowMattic Workflow + Google Sheets/Airtable integration

**MCP Tool**:
- **Name**: "Update Content Calendar"
- **Type**: Workflow
- **Integrations**: Google Sheets API + WordPress
- **Workflow**: Get post data → Format for calendar → Update spreadsheet → Notify team

**Real Usage**:
```
You: "Update content calendar - just published 'Email Marketing Best Practices' and scheduled 'Social Media Trends 2024' for next Tuesday"

AI: "📅 Content calendar updated:

Google Sheets Updates:
• Row 47: 'Email Marketing Best Practices'
  - Status: Published ✅
  - Publish date: July 25, 2024
  - Category: Marketing
  - Performance tracking: Enabled

• Row 48: 'Social Media Trends 2024'  
  - Status: Scheduled 📅
  - Publish date: July 30, 2024 at 9:00 AM
  - Category: Social Media
  - Promotion plan: Added

✅ Calendar synced with WordPress
✅ Team notification sent to #content-team
📊 Analytics tracking enabled for both posts"
```

**Why it's useful**: Keep content calendar current without manual spreadsheet updates.

## Customer Management and CRM

### 6. Customer Information Sync

**What it does**: Sync customer data between your website and CRM system automatically.

**Time saved**: 10 minutes per customer (8+ daily = 80 minutes saved)

**Setup**: FlowMattic Workflow + CRM integration (HubSpot, Salesforce, etc.)

**MCP Tool**:
- **Name**: "Sync Customer to CRM"
- **Type**: Workflow
- **Integrations**: HubSpot API + WooCommerce + WordPress
- **Workflow**: Get customer data → Format for CRM → Create/update contact → Add notes

**Real Usage**:
```
You: "Sync customer Mike Chen to CRM - he just made his third purchase (total $847) and signed up for our newsletter"

AI: "🔄 Customer synced to HubSpot CRM:

Contact Details:
• Name: Mike Chen
• Email: mike@techstartup.com
• Status: Updated existing contact
• Customer since: March 2024

Purchase History Synced:
• Total orders: 3
• Total value: $847.00
• Last purchase: July 25, 2024
• Favorite category: WordPress Plugins

Engagement Data:
• Newsletter: Subscribed ✅
• Email engagement: High (85% open rate)
• Website visits: 12 in last 30 days

CRM Actions Completed:
✅ Contact properties updated
✅ Purchase history logged
✅ Added to 'High-value customers' list
✅ Triggered welcome email sequence"
```

**Why it's useful**: Keep CRM data current without manual data entry.

### 7. Customer Support Ticket Creation

**What it does**: Create support tickets in your helpdesk system from various sources (email, chat, forms).

**Time saved**: 8 minutes per ticket (12+ daily = 96 minutes saved)

**Setup**: FlowMattic Workflow + Support system integration

**MCP Tool**:
- **Name**: "Create Support Ticket"
- **Type**: Workflow
- **Integrations**: Zendesk/Freshdesk API + Email parsing
- **Workflow**: Parse request → Create ticket → Assign priority → Notify team

**Real Usage**:
```
You: "Create support ticket for customer Lisa Park - she's having trouble with the checkout process, says payment fails at the last step, urgent because she needs to complete order for event tomorrow"

AI: "🎫 Support ticket created in Zendesk:

Ticket Details:
• Ticket ID: #ZD-15847
• Customer: Lisa Park (lisa@events.com)
• Priority: HIGH (urgent timeline)
• Category: Technical - Checkout Issues
• Assigned to: Payment specialist team

Issue Summary:
• Problem: Payment failure at checkout
• Impact: Cannot complete time-sensitive order
• Customer need: Order completion by tomorrow
• Troubleshooting: Payment gateway issue suspected

Automated Actions:
✅ Ticket created with high priority
✅ Assigned to payment specialist (Sarah)
✅ Customer notified with ticket number
✅ Internal alert sent to dev team
✅ Escalation timer set (2 hours)

Estimated resolution: 2-4 hours"
```

**Why it's useful**: Consistent ticket creation with proper categorization and routing.

## E-commerce and Sales Automation

### 8. Order Processing and Notifications

**What it does**: Process new orders and send notifications to relevant team members.

**Time saved**: 12 minutes per order (20+ daily = 240 minutes saved)

**Setup**: FlowMattic Workflow + WooCommerce + Communication integrations

**MCP Tool**:
- **Name**: "Process New Order"
- **Type**: Workflow
- **Integrations**: WooCommerce + Slack + Email + Google Sheets
- **Workflow**: Get order data → Update inventory → Notify fulfillment → Update tracking

**Real Usage**:
```
You: "Process new order #WC-3847 from Jennifer Walsh - 2x Premium Courses bundle, expedited shipping requested"

AI: "📦 Order #WC-3847 processed successfully:

Order Details:
• Customer: Jennifer Walsh
• Products: 2x Premium Courses Bundle ($297 each)
• Total: $594.00 + $25 expedited shipping
• Payment: Confirmed (Stripe)

Automated Processing:
✅ Inventory updated (Premium bundles: 23 remaining)
✅ Fulfillment team notified via Slack
✅ Customer confirmation email sent
✅ Expedited shipping label generated
✅ Order added to fulfillment spreadsheet

Shipping Information:
• Method: UPS Next Day Air
• Tracking: 1Z999AA1234567890
• Expected delivery: Tomorrow by 3 PM
• Customer notified with tracking details

Next: Fulfillment team will process within 2 hours"
```

**Why it's useful**: Streamlined order processing without manual coordination across teams.

### 9. Inventory Alerts and Reordering

**What it does**: Monitor inventory levels and send alerts when products are running low.

**Time saved**: 20 minutes per check (daily checks = 140 minutes weekly saved)

**Setup**: FlowMattic Workflow + WooCommerce + Communication tools

**MCP Tool**:
- **Name**: "Check Inventory Levels"
- **Type**: Workflow
- **Integrations**: WooCommerce + Slack + Email + Google Sheets
- **Workflow**: Check stock levels → Identify low stock → Send alerts → Update tracking sheet

**Real Usage**:
```
You: "Check inventory levels and send alerts for any products below 10 units"

AI: "📊 Inventory Level Report:

🔴 LOW STOCK ALERTS (≤10 units):
• WordPress Plugin Bundle: 7 units
• SEO Course Package: 4 units  
• Website Template #5: 9 units

⚠️ CRITICAL STOCK (≤5 units):
• SEO Course Package: 4 units (Best seller!)

📈 WELL STOCKED (>50 units):
• Basic WordPress Guide: 127 units
• Email Templates: 89 units

Automated Actions Taken:
✅ Low stock alert sent to inventory manager
✅ Critical stock alert sent to purchasing team
✅ Reorder recommendations generated
✅ Sales team notified to push other products
✅ Inventory spreadsheet updated with current levels

Recommended Actions:
🚨 URGENT: Reorder SEO Course Package (suggest 50 units)
📋 Schedule: Reorder other low-stock items this week"
```

**Why it's useful**: Prevent stockouts without daily manual inventory checks.

## File and Document Management

### 10. Google Drive File Organization

**What it does**: Automatically organize files uploaded to your site into structured Google Drive folders.

**Time saved**: 8 minutes per file (15+ weekly = 120 minutes saved)

**Setup**: FlowMattic Workflow + Google Drive integration

**MCP Tool**:
- **Name**: "Organize Files to Drive"
- **Type**: Workflow
- **Integrations**: Google Drive API + WordPress Media Library
- **Workflow**: Detect new upload → Categorize → Create folder structure → Move file → Update database

**Real Usage**:
```
You: "Organize the new client files I just uploaded - 3 logo designs and 2 brand guideline PDFs for TechStart Inc project"

AI: "📁 Files organized in Google Drive:

Created folder structure:
📂 Clients/TechStart Inc/2024-07-Brand Project/
  ├── 📂 Logos/
  │   ├── TechStart_Logo_V1.ai
  │   ├── TechStart_Logo_V2.ai  
  │   └── TechStart_Logo_V3.ai
  └── 📂 Brand Guidelines/
      ├── TechStart_Brand_Guide_Draft.pdf
      └── TechStart_Style_Guidelines.pdf

File Processing:
✅ 5 files moved from WordPress uploads
✅ Proper naming convention applied
✅ Sharing permissions set (Client access)
✅ Backup created in 'Project Archives'
✅ File links updated in project management tool

Client Access:
🔗 Shared folder link: https://drive.google.com/folder/xyz
📧 Access notification sent to client contact"
```

**Why it's useful**: Organized file storage without manual folder creation and file moving.

### 11. Document Generation and Sharing

**What it does**: Generate project documents (proposals, invoices, reports) and share them automatically.

**Time saved**: 25 minutes per document (8+ weekly = 200 minutes saved)

**Setup**: FlowMattic Workflow + Google Docs/PDFs + sharing integrations

**MCP Tool**:
- **Name**: "Generate Project Document"
- **Type**: Workflow
- **Integrations**: Google Docs API + Email + Client portal
- **Workflow**: Pull data → Generate document → Format → Share → Track access

**Real Usage**:
```
You: "Generate project proposal for WebDesign Inc - website redesign project, $15,000 budget, 6-week timeline, includes responsive design and SEO optimization"

AI: "📄 Project proposal generated and shared:

Document Details:
• Title: 'Website Redesign Proposal - WebDesign Inc'
• Type: Professional proposal (Brand template)
• Pages: 8 pages with detailed breakdown
• Format: PDF + editable Google Doc backup

Proposal Contents:
✅ Executive summary with project overview
✅ Detailed scope (responsive design + SEO)
✅ Timeline breakdown (6 weeks, 3 milestones)
✅ Investment: $15,000 (payment schedule included)
✅ Terms and conditions
✅ Portfolio examples
✅ Next steps and contact information

Delivery & Sharing:
📧 Email sent to client with proposal attachment
🔗 Secure client portal link provided
📊 Document tracking enabled (view analytics)
📅 Follow-up reminder set for 5 business days

Client can view, download, and digitally sign the proposal"
```

**Why it's useful**: Professional documents created and delivered without manual formatting and sending.

## Analytics and Reporting

### 12. Automated Performance Reports

**What it does**: Generate and send regular performance reports combining data from multiple sources.

**Time saved**: 45 minutes per report (weekly reports = 180 minutes saved)

**Setup**: FlowMattic Workflow + Analytics integrations

**MCP Tool**:
- **Name**: "Generate Performance Report"
- **Type**: Workflow
- **Integrations**: Google Analytics + Social Media APIs + Email
- **Workflow**: Collect data → Analyze trends → Format report → Send to stakeholders

**Real Usage**:
```
You: "Generate weekly performance report for July 22-28 and send to the marketing team"

AI: "📊 Weekly Performance Report Generated (July 22-28, 2024):

Website Performance:
• Total visitors: 2,847 (+15% vs last week)
• Page views: 8,492 (+12%)
• Bounce rate: 34% (improved from 38%)
• Top page: 'WordPress Security Guide' (847 views)

Social Media Growth:
• Twitter followers: +127 this week
• LinkedIn engagement: +34%
• Instagram reach: 12,400 (+18%)
• Best post: SEO Tips video (2,100 engagements)

Conversion Metrics:
• Email signups: 89 new subscribers
• Course enrollments: 12 (+25%)
• Revenue: $3,247 (+8% vs last week)

📈 Key Insights:
• Security content performing exceptionally well
• Video content shows highest engagement
• Tuesday posts get 40% more engagement

✅ Report sent to marketing team
✅ Trends analysis included
✅ Recommendations for next week provided
📅 Next report scheduled for August 4th"
```

**Why it's useful**: Regular reporting without manually collecting data from multiple platforms.

## Setup Made Simple

### Getting Started (30 minutes)

1. **Choose Your Integration**: Pick a service you already use (Gmail, Slack, Google Drive, etc.)
2. **Connect to FlowMattic**: Use FlowMattic's built-in integrations (no API keys needed for most)
3. **Build Simple Workflow**: Start with a 2-3 step workflow using FlowMattic's visual builder
4. **Create MCP Tool**: Point the tool to your workflow
5. **Test and Use**: Start with simple commands

### Easiest Integrations to Start With

**No Setup Required**:
- Email (Gmail, SMTP)
- WordPress (posts, users, comments)
- Basic webhooks

**Simple Setup**:
- Slack (webhook URL)
- Google Drive (OAuth connection)
- Social media (API connections)

**Slightly More Setup**:
- CRM systems (API keys)
- E-commerce platforms (store connections)
- Analytics tools (tracking codes)

## Why These Work Better

### No Coding Required
- Visual workflow builder in FlowMattic
- Pre-built integrations with popular services
- Drag-and-drop automation setup

### Real Business Value
- Address actual daily tasks everyone faces
- Use services most businesses already have
- Provide immediate, measurable time savings

### Scalable Solutions
- Start simple, add complexity gradually
- Build on existing business processes
- Expand integrations as you grow comfortable

## Quick Win Strategy

1. **Week 1**: Set up email notification workflow (choose Gmail or Slack)
2. **Week 2**: Add social media posting automation  
3. **Week 3**: Implement customer data sync (if using CRM)
4. **Week 4**: Add file organization automation
5. **Month 2**: Build comprehensive reporting workflows

## Expected Time Savings

**Daily Operations**: 2-4 hours saved per day
**Weekly Reporting**: 3-5 hours saved per week  
**Monthly Tasks**: 8-12 hours saved per month
**Total Annual Value**: 200+ hours saved

## Related Resources

- [FlowMattic Integrations](https://flowmattic.com/integrations) - See all available connections
- [How to Add MCP Tools](https://support.flowmattic.com/kb/article/91/) - Step-by-step tool creation
- [Understanding MCP Server Admin Screen](https://support.flowmattic.com/kb/article/90/) - Interface guide

These workflow and API-based automations require no coding knowledge while providing substantial time savings. Start with the integrations you already use, and expand from there.

---

# Requirements

Source: https://support.flowmattic.com/kb/article/28/requirements

FlowMattic requires the following site configuration in order to work smoothly and handle your workflow execution without any delays or issues.

<table><tbody><tr><td><strong>WordPress</strong></td><td>5.0 or greater</td></tr><tr><td><strong>PHP</strong></td><td>7.2 or greater</td></tr><tr><td><strong>MySQL / MariaDB</strong></td><td>5.7 / 10.2 or greater</td></tr><tr><td><strong>WordPress Cron</strong></td><td><strong>✓</strong></td></tr><tr><td><strong>Permalink Structure</strong></td><td>Set to Postname or anything but not default</td></tr><tr><td><strong>File Permissions</strong></td><td>Ability to install plugins without issues from dashboard</td></tr><tr><td><strong>Memory</strong></td><td>Recommended memory - 512MB</td></tr><tr><td><strong>HTTPS Support</strong></td><td><strong>✓</strong></td></tr></tbody></table>

If you have any questions about the requirements, please get in touch with us, and we will be more than happy to assist you.

---

# Router

Source: https://support.flowmattic.com/kb/article/29/router

Router by FlowMattic is a feature that is designed to manage the flow of data and direct it to the appropriate destinations within a set of actions. It acts as a traffic controller, routing data packets based on predefined rules and conditions. The Router by FlowMattic helps ensure efficient and secure data transfer, enabling effective communication and seamless integration between different applications. It plays a crucial role in optimizing data flow, enhancing performance, and facilitating the smooth operation of complex networks or applications.

#### Step-by-Step Documentation for Router by FlowMattic

### 1\. Create a New Workflow

Go to the FlowMattic Dashboard, where you can manage and create workflows. To start a new workflow, click the **“New Workflow”** button located in the top-right corner of the Dashboard. This will begin the process of creating your new workflow.

### 2\. Adding the Router

- In the workflow builder, click the **“+”** icon to add a new step. A panel will appear where you can either search for **"Router"** in the search bar or scroll through the list of FlowMattic's built-in tools to find Router by FlowMattic. Once located, click **Router** to add it to your workflow.

![](/storage/kb-images/9c508d4b3e-Zight-2024-12-08-at-12.05.38-PM-1024x653.png)

- Once added, FlowMattic will automatically create two default routes: **Route A** and **Route B**. These initial routes help split the workflow into different paths based on conditions you set. You can add more routes as needed.

![](/storage/kb-images/9b40bf050b-Screenshot-2024-12-08-114142-1024x608.png)

### 3\. Adding and Managing Routes

- **To Add a Route**: Click the **“+”** icon below the Router step. This will add a new route, and it will be automatically assigned a unique Route Letter (e.g., Route C, Route D, etc.). You can add as many routes as necessary.

![](/storage/kb-images/4e956f6d82-Screenshot-2024-12-08-114621-1024x529.png)

- **Managing Routes**: You can create multiple actions within each route to perform specific tasks or handle data in different ways. This gives you flexibility in designing complex workflows to meet your needs.

### 4\. Setting Conditions for Routes

- After adding a route, define the conditions that must be met for the router to process requests through that route. The workflow will only execute along the route if the specified conditions are satisfied. This ensures that the data follows the correct path based on the criteria you set.

- You can set multiple conditions for each route, allowing for precise control over how incoming requests are handled. These conditions ensure the router directs requests to the appropriate action steps, ensuring your workflow operates correctly.

### 5\. Context Menu Options for Routes

When you click the three dots icon next to a route, the context menu will appear. This menu provides various options to manage and modify your routes.

![](/storage/kb-images/b31fc5dd96-Screenshot-2024-12-08-114908.png)

- **Rename**: The **“Rename”** option allows you to change the name of a route to make it more identifiable. This helps in organizing your routes, especially when dealing with complex workflows. To rename, select this option, type the new name, and save.

- **Duplicate**: Use the **“Duplicate”** option to create an exact copy of the selected route, including its conditions and actions. This is useful when you need similar routes but with slight variations. When you duplicate a route, the new copy will be added at the end of the current route, maintaining the existing order of routes in the workflow.

- **Copy**: The **“Copy”** option allows you to copy a route’s configuration without adding it immediately. You can then paste it in another part of the workflow.

- **Paste Below**: If you’ve copied a route, you can use the **“Paste Below”** option to insert it next to the current route. This ensures the copied route is positioned logically within the workflow while maintaining the proper sequence for execution.

- **Paste to Replace**: This feature lets you replace an existing route with a copied one. When you paste a route using **“Paste to Replace,”** the original route is overwritten, including all the steps within that route. This ensures the new route fully replaces the old one, maintaining the workflow’s structure.

- **Delete**: If a route is no longer needed, you can delete it using the **“Delete”** option. Once deleted, the route cannot be restored, so make sure it’s no longer required before deleting. If all routes are deleted, the entire Router step will also be deleted from the workflow.

### 6\. Adding More Routes

If your application requires handling multiple routes, you can repeat **Step 3** to add more routes to the Router. This allows you to create different routes for various functionalities or sections of your application. By adding more routes, you can establish a comprehensive routing system that directs incoming requests to their respective handlers based on specific conditions.

It’s important to remember that the order of the routes can affect how requests are processed. Ensure that you arrange the routes in the desired order to maintain the correct routing hierarchy or priority.

### 7\. Save Your Workflow

Once your workflow is configured with all the necessary routes and conditions, click on the **“Save Workflow”** button to finalize the setup. This will schedule your workflow and ensure that it’s ready to process data based on your defined routes.

---

# Running FlowMattic Tables on multiple sites

Source: https://support.flowmattic.com/kb/article/239/running-flowmattic-tables-on-multiple-sites

If you run FlowMattic on more than one site — an agency with client sites, or a few projects of your own — FlowMattic Tables works a little differently from the plugin itself. Your FlowMattic license covers every site it allows. **FlowMattic Tables is subscribed per site**: each site gets its own database and its own subscription.

This article explains why it works that way, and how to manage it cleanly once you have several.

## The model in one line

**One site, one database, one subscription.** Ten sites using FlowMattic Tables means ten databases and ten subscriptions — not one subscription covering ten sites.

That is a deliberate design decision rather than something we haven't got to yet, and the reasoning is worth understanding because it affects how you should set things up.

## Why one database per site

### Cancelling one client shouldn't affect the others

If a single subscription backed ten client sites, cancelling it wouldn't take down one site — it would take down all ten at once. That is a real risk in agency work: a client's contract ends, someone cancels what looks like the right subscription, and nine other sites lose their data with it.

Because each site has its own subscription, ending one client's contract affects exactly that client's site. A mistake costs you one site, not your whole portfolio.

### Plan limits apply to a database, not to a site

Every plan's limits — records and monthly writes — are limits on **a database**. If ten sites shared one, a single busy site could consume half the quota on its own and leave the other nine squeezed against a cap they had no part in reaching.

There is no sensible way to fence off or evenly divide storage between sites inside one shared database. Separate databases mean each site's usage is genuinely its own, and one client's growth never quietly degrades another's.

### Handing a site over stays clean

When a site changes hands — you hand it to the client, or take it over from someone else — its database and its subscription travel with it as a single unit. Nothing has to be untangled from a shared pool first.

## Telling your subscriptions apart

Every subscription is labelled with the site it belongs to. In your billing portal and on each invoice, a subscription appears as:

```
FlowMattic Tables — clientsite.com
```

So a customer running several sites sees a list like this rather than a column of identical rows:

| Subscription | Site |
|---|---|
| FlowMattic Tables — clientsite.com | The client site |
| FlowMattic Tables — myagency.com | Your own site |
| FlowMattic Tables — anotherproject.dev | A third project |

The same label appears on the invoice PDF, which is what makes bookkeeping across several sites practical — each invoice states which site it is for.

## Finding the subscription for a particular site

The most reliable way is to start from the site itself rather than from your billing portal:

1. In that site's WordPress admin, go to **FlowMattic → FlowMattic Tables**.
2. Click **Manage billing**.

This opens the billing portal for **that site's subscription specifically**. Whatever you do there — update a card, change plan, cancel — applies to the site you opened it from and no other.

If you would rather work from the billing portal directly, match by the domain in the subscription name.

## Cancelling one site's subscription

1. Open that site's WordPress admin.
2. Go to **FlowMattic → FlowMattic Tables → Manage billing**.
3. Cancel the subscription shown there.

Because you started from the site, there is no ambiguity about which subscription you are cancelling, and no other site is affected.

Cancelling is not instant data loss. The database is kept intact for **30 days** — resubscribe within that window and everything is exactly as you left it. After that we take a final export and retain it for **90 days** before the database is removed. You can also download your own export at any time while subscribed. See [Why is FlowMattic Tables a paid add-on?](/kb/article/210/why-is-flowmattic-tables-a-paid-add-on) for the full detail on data retention.

## Billing across several sites

### Separate invoices, and why

Each subscription bills on its own date and produces its own invoice. That is a consequence of the per-site model rather than an oversight — an invoice belongs to the site it is for, which is what lets you attribute the cost to a specific client or project.

### Different owners, different accounts

In practice, who owns the subscription varies a lot:

- Some agencies subscribe for every client site and re-bill.
- Some ask the client to subscribe themselves, so the client holds their own billing relationship.
- Some deliberately use a different email per client, so handing a site over later is clean.

All of these work. There is nothing to configure — subscribe from the site, using whichever email should own it.

Choosing this at the start is worth a moment's thought: whoever completes checkout owns that subscription, and moving it later means cancelling and resubscribing.

### Practical bookkeeping

- **Use the domain on the invoice.** Each invoice names its site, so invoices can be filed against the right client without cross-referencing anything.
- **Decide who pays before you subscribe**, not after. If the client should own it, have them complete checkout from their own site.
- **Annual billing reduces the paperwork.** One invoice a year per site instead of twelve, and it costs less — two months free on Starter and Pro.

## Frequently asked questions

### Can I move a subscription from one site to another?

Not directly. A subscription is tied to the site it was created from, along with that site's database. To move, subscribe on the new site and cancel on the old one — exporting your data first if you need to carry it across.

### If I use the same email for every site, will they be grouped?

They will appear under one billing account, which makes them easier to find in one place, but they remain separate subscriptions with separate renewal dates. Each is still labelled with its own domain.

### I subscribed twice for the same site by mistake. What now?

Contact support. Cancel neither until we have checked which subscription is attached to the live database, so you don't cancel the one your data is on.

### Does a staging or development copy need its own subscription?

If it needs its own database, yes. Be careful with cloned sites: a copy of a live site carries the original's connection details, which means a staging copy can read and write the **live** database. If you clone a site that uses FlowMattic Tables, disconnect Tables on the copy before using it.

### Do I get a volume discount for many sites?

Not at present. If you are running Tables on a significant number of sites, get in touch — we would like to hear about it, and that kind of feedback shapes what we do next.

---

# Scheduled Workflows

Source: https://support.flowmattic.com/kb/article/13/scheduled-workflows

The Schedule feature in FlowMattic is a powerful tool that enables users to automate their workflows at specific times and intervals. It offers the ability to set a specific time and date when the workflow will start, and then repeat the process at specified intervals, such as hourly, daily, weekly or monthly.

For example, if a user wants to send an email newsletter every Monday at 10 am, they can set the Schedule feature to execute the workflow at that specific time and date, and then set it to repeat every Monday at 10 am.

This functionality is beneficial for users who need to perform repetitive tasks on a regular basis, as it helps to save time and reduces the risk of human error. With the Schedule feature, users can ensure that their workflows are executed consistently and automatically, allowing them to focus on other important tasks.

Here are the step-by-step instructions for creating a schedule using FlowMattic:

1. To create a new workflow on FlowMattic in WordPress, you need to first log in to your WordPress dashboard and navigate to the FlowMattic ->  Workflows. Now, click on the "**New Workflow"** button.
 
 ![new-workflow.jpeg](/storage/kb-images/3430a09ed7-inline.png)

2. By default, the trigger step is added with webhook module selected. Click on the trigger step and then in "Setup" tab, click the "Change" button, Then, choose the "Schedule" module from the FlowMattic Built-in Tools-
 
 ![choose-schedule-module.jpeg](/storage/kb-images/e05b5252b8-inline.png)

3. Once you've selected the Schedule application, click the "Choose an Event" dropdown to select the event you want to schedule the workflow.&nbsp; Depending upon your requirement you can select from various options available from every minute - every month, whenever you want to execute the workflow.

 ![schedule-choose-event.jpeg](/storage/kb-images/5aeb321b82-inline.png)

4. In the "Event" section, select the various options available to get specific the frequency of the event.&nbsp;

4.1 Every X minutes - Allows you to trigger the workflow after every X number of minutes. You can define the number of minutes in the next option made visible after this event selection. Maximum number of minutes you can set is 59 minutes.

4.2 Every Hour - This option allows you to trigger the workflow every hour. After every hour, the trigger will be executed.

4.3 Every week - This option allows you to trigger the workflow on a specific day and time of the week. You can select the day of the week and set the specific time in the next option made visible after this event selection. For example, if you select "Every week" and set it to trigger on Tuesday at 3 PM, the workflow will trigger every Tuesday at 3 PM.

4.4 Every day - This option allows you to trigger the workflow every day at a specific time. You can set the specific time in the next option made visible after this event selection. For example, if you select "Every day" and set it to trigger at 8 AM, the workflow will trigger every day at 8 AM.

4.5 Every month - This option allows you to trigger the workflow on a specific day and time of the month. You can select the day of the month and set the specific time in the next option made visible after this event selection. For example, if you select "Every month" and set it to trigger on the 15th day of the month at 10 AM, the workflow will trigger every month on the 15th day at 10 AM.

5. By default, the scheduled workflows are set to not execute on weekends. If you need to trigger the workflow even on weekends, go the configure tab and check the box for "Trigger on weekends".
 
 ![schedule-trigger-on-weekends.jpeg](/storage/kb-images/59feeea52b-inline.png)

7. In the "Time" section, enter the specific time of day that you want the event to trigger. This option is only available when “choose the event” button is selected among the three options from-

- Every Day

- Every week

- Every Month.

7. Finally, go to the Test tab and click the "Save and Close" button. The scheduled workflow will start executing as soon you publish the workflow.

## **Conclusion**

Once you've completed these steps, the event will be scheduled to trigger at the specified frequency and time. You can also edit or delete the scheduled event from the Schedule by FlowMattic dashboard if necessary.

---

# Set a form's success message or redirect from a workflow

Source: https://support.flowmattic.com/kb/article/200/set-a-forms-success-message-or-redirect-from-a-workflow

A form has a static success message and an optional redirect URL in its settings. A workflow can override both at run time, so what the visitor sees after submitting can depend on their answers — including an answer generated by an AI step.

## Set a custom success message

1. Build a workflow on the **Form Builder → New Form Submission** trigger, scoped to your form.
2. Add whatever steps produce the content you want to show — for example an AI Agent step that turns the submitter's question into an HTML answer.
3. Add a **Form Builder → Set Custom Response** action.
4. Put your content in the **Response Body** field — this can be captured output from an earlier step, such as the AI step's result. Tick **Force render as HTML (skip auto-detection)** if your content is HTML.

When the submission finishes, the visitor sees your response body as the form's success screen instead of the form's static thanks message.

![A workflow with an AI step followed by a Set Custom Response action whose Response Body is mapped to the AI output](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-form-builder-wf-set-custom-response.png)

## Set a custom redirect URL

1. In the same workflow, add a **Form Builder → Set Custom Redirect URL** action.
2. Set the URL, using `{{field_key}}` tokens if you want to pass answers into it, for example `/thank-you?plan={{plan}}`.

After submitting, the visitor is redirected to that URL. A workflow-set redirect overrides the redirect configured in the form's settings.

## How it works

Both actions run inside the same workflow that the submission triggered, and are applied before the form returns its response. So the sequence is: the visitor submits → the workflow runs **Set Custom Response** or **Set Custom Redirect URL** → the visitor sees that message or redirect instead of the form's default.

---

# Set booking availability, buffers, and limits

Source: https://support.flowmattic.com/kb/article/199/set-booking-availability-buffers-and-limits

Availability and limits decide which slots an invitee can pick. This guide covers each option on a booking calendar.

## Open the calendar's availability settings

1. Go to **FlowMattic → Bookings** and open (or create) a calendar.
2. Find the **Availability** section.

![The calendar editor's Availability section](https://assets.infidesk.support/kb/inline/2026/07/i4fMrX1IzsUOdJWUQ70ALJEGbQ4Q89lA5rFJ7yEl.png)

## Choose an availability type

Under **When can people book?**, choose one of two modes:

- **Recurring weekly** — set a window for each day under **Weekly hours**, Monday to Sunday. For example, Monday–Friday 09:00–17:00 and no weekend slots. Use this for an ongoing calendar.
- **Specific dates** — offer a single day or a date range only. Use this for a one-off event or a limited window.

## Set the timezone

Set the calendar's **Timezone** to *your* timezone. The public booking page lets each invitee switch to their own timezone, and the displayed slots adjust for them automatically — so you only ever configure your own hours.

## Set buffers and notice

- **Buffer before / Buffer after** — free time held around each booking so meetings do not sit back-to-back. Each is a dropdown: None, 5, 10, 15, or 30 minutes.
- **Min. notice** — the least lead time before a slot can be booked, so no one books you in five minutes. Options are None, 1, 2, 4, 12, or 24 hours.

## Set the booking window and daily cap

- **Booking window** — how far into the future invitees can book: 14, 30, 60, or 90 days.
- **Max bookings / day** — the largest number of bookings allowed on any single day, after which that day shows as full. Leave it blank for no limit.

![max-bookings](https://assets.infidesk.support/kb/inline/2026/07/6SCoJSSo6gsvEMhzj6YNtOLhAbfu7BVzFGGyrrLU.png)

## Save

Click **Save**. The public page immediately reflects the new availability — only slots that satisfy every rule (within the hours, outside the buffers, beyond the minimum notice, inside the booking window, and under the daily cap) are offered.

![The public booking page showing available slots for a day, reflecting the configured hours](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-bookings-booking-public-slots.png)

---

# Setting up AI Chatbot ( AI Assistants )

Source: https://support.flowmattic.com/kb/article/5/setting-up-ai-chatbot

FlowMattic now supports creating powerful AI Chatbots powered by OpenAI. You can create assistants tailored to your business needs, upload relevant content to train them, and embed or share them easily.

Before proceeding, ensure you’ve completed the following prerequisite.

---

## 🔧 Prerequisite: Connect Your OpenAI Account

Before setting up your AI Assistant, you must connect your OpenAI account to FlowMattic using **Connects**.

Follow this step-by-step guide:  
👉 [Add OpenAI API Key to FlowMattic Using Connects](https://support.flowmattic.com/kb/article/67/add-openai-api-key-to-flowmattic-using-connects)

This connection is required so FlowMattic can send and receive data from OpenAI's API using your account.

---

## 🧠 Step 1: Navigate to AI Assistants

Click the **AI Assistants** tab from the sidebar (see Screenshot 1, marked as **1**).

If you haven't created any assistants yet, you'll see an empty list. Click the **Create New Assistant** button (Screenshot 1, marked as **2**).

![Create new AI Assistant Button](/storage/kb-images/921c9e4eaf-inline.png)

---

## ➕ Step 2: Create a New Assistant

A popup will appear where you can enter the assistant details:

- **Assistant Name**: Choose a unique name.
- **OpenAI Connect**: Select the OpenAI connection created earlier.
- **Assistant Description**: A short description for internal reference.

Once filled, click **Create**.

![Create new AI Assistant Settings](/storage/kb-images/69ab22c056-inline.png)

---

## ⚙️ Step 3: Configure Your AI Assistant

Once your assistant is created, it will appear in the list. Click the **Edit** button to configure it further.

You’ll be redirected to the AI Assistant Setup Page, which includes the following tabs:

### 🔹 Setup Tab

- **Chatbot Name**  
- **Choose Connect** – Select the OpenAI Connect you created.  
- **Description** – Internal reference text.  
- **Choose Assistant** – From your OpenAI Assistant list or create a new one.  
  Click the **Create Assistant** button to open an advanced assistant creation modal (Screenshot 5).

  You can configure:
  - Assistant Name  
  - Connect  
  - Model (e.g., `gpt-4-turbo`)  
  - System Instructions  
  - Description  

- **Welcome Text** – The message users will see first.  
- **User Input Placeholder** – The hint in the input field.  
- **Instructions** – System-level instructions for your assistant.  
- **AI Model** – Select model (make sure it's compatible with retrieval if you use content sources).  
- **Load User Session Chats** – Yes to retain session history for users.

Click **Save Changes** once done.

---

## 📂 Step 4: Add Content Sources (Training Files)

Click the **Content** tab > then click **Add Source** (See Screenshot 6).

You’ll see the **Add Content Source** modal where you can:

- Upload a content file that your assistant will use to answer questions.
- Add a short description for the source.

### 📁 Supported File Types

- `.txt`, `.doc`, `.docx`, `.pdf`, `.html`, `.json`, `.md`  
- Max file size: **10 MB**

Once uploaded, these files are sent to OpenAI and used by the assistant to answer user queries accurately. Make sure to upload content relevant to your assistant's role (e.g., FAQs, help docs, policy files).

> **Note**: Ensure you are using a model that supports retrieval when working with file-based content.

---

## 🎨 Style Tab – Customize Your Chatbot's Appearance

The **Style** tab allows you to customize the visual appearance of your AI assistant to match your brand or website aesthetic. You can adjust:

- **Chat Window Header Title** – Set the chatbot’s title shown at the top of the chat.
- **Theme Color** – Choose a primary color to apply to the header and button elements.
- **Chat Bubble Color** – Customize the color of chat bubbles for both user and assistant.
- **Font Family** – Select from system fonts for consistency with your site typography.
- **Position on Screen** – Decide where the chatbot will appear (bottom left/right, full page).
- **Icon and Branding** – Upload your custom logo or icon to personalize the experience.
- **Chat Button Text and Icon** – If the assistant appears minimized, customize the button text and choose a recognizable icon for your brand.

> 📝 **Tip**: Preview your assistant style in real-time as you customize, so you get the exact look before embedding.

---

## ⚡ Actions Tab – Add Dynamic Workflows to Your Assistant

The **Actions** tab allows you to go beyond answering questions. Here, you can configure the assistant to **trigger real workflows or perform tasks** based on specific conditions or phrases.

For example:
- 🔁 **Trigger a FlowMattic workflow** when the user asks for a report, submits feedback, or wants to schedule something.
- 🔗 **Pass dynamic input** to workflows (e.g., user's question or a selected option).
- 🔄 **Update records**, send emails, or perform API calls based on user input.

### Actions Configuration Includes:
- **Trigger Word/Phrase** – Define what user input should trigger an action.
- **Mapped Workflow** – Choose an existing FlowMattic workflow to run.
- **Pass Input Variables** – Use dynamic fields to send data into the workflow like `{{user_input}}`.

> 🔍 **Example**: If user says "Generate invoice", it can run a workflow that collects data, generates a PDF invoice, and sends it via email.

---

## 💬 Conversations Tab – Monitor and Manage User Chats

The **Conversations** tab displays a complete history of all user interactions with your assistant. It’s useful for reviewing:

- ✅ **Successful responses** – See how the assistant handled questions.
- ⚠️ **Unanswered queries** – Identify gaps where training or content can be improved.
- 📁 **Content usage** – Understand which documents or instructions the assistant referred to.
- 🧑‍💻 **User sessions** – View interactions grouped by session and user, making it easy to trace back any conversation.

> 💡 This tab is essential for **refining your assistant** over time by observing real-world usage and feedback.

---

## 🔗 Embed or Share Your Assistant

Once your AI Assistant is ready, you can either **embed** it on your website or **share it via link**. These options are located at the top right corner of the setup interface.

### 🔧 Embed Assistant
- Click the **Embed** button to get a code snippet.
- You can copy and paste this script into your website's HTML where you want the chatbot to appear.
- The embedded assistant will retain all configurations including style, content, and memory.

> ✅ Use this if you want a persistent chatbot on your landing pages, help centers, or member dashboards.

### 🔗 Share Assistant (Link)
- Click the **Share** button to generate a public URL.
- This link can be shared directly in emails, support docs, or social media.
- The assistant will load in a standalone view with full chat interface.

> 📣 Ideal for sending quick access to clients, prospects, or internal teams without embedding it on a site.

---

## 🧠 Real-World Examples of AI Assistants

Here are some powerful ways to use AI Assistants in FlowMattic, particularly with uploaded content and workflow actions.

---

#### 🔹 Example 1: **Support Assistant** ✅

**Use Case**: Provide automated customer support using your company’s help docs.

- **Content Sources**: Upload refund policies, setup guides, onboarding manuals, and FAQs.
- **Actions**:
  - Escalate to human support via a FlowMattic workflow when needed.
  - Generate a support ticket with the chat transcript and user email.

---

#### 🔹 Example 2: **Documentation Help Assistant** 📚

**Use Case**: Help users understand your technical product or API.

- **Content Sources**: Upload your developer docs, API references, and integration tutorials (in `.pdf`, `.md`, `.html`, or `.json`).
- **Instructions**: Ask the assistant to respond in a technical tone with examples when available.
- **Perfect For**: SaaS platforms, API providers, plugin documentation portals.

---

#### 🔹 Example 3: **HR Assistant for Company Policies** 🧑‍💼

**Use Case**: Internal AI assistant for employees to ask about HR and company policies.

- **Content Sources**: Upload your company handbook, HR policy, leave rules, holiday calendar, etc.
- **Instructions**: Answer based on company rules and direct employees to the right department when needed.
- **Bonus**: Use actions to send leave applications to HR or log attendance queries.

---

#### 🔹 Example 4: **Product Assistant for eCommerce** ✅

**Use Case**: Assist customers with product-related queries directly from your catalog.

- **Content Sources**: Upload product catalogs, pricing tables, warranty documents, and usage manuals.
- **Actions**:
  - Suggest products based on user needs.
  - Generate a discount code or cart link using a FlowMattic workflow.
  - Send availability updates to users' emails.

---

#### 🔹 Example 5: **Knowledge Base Assistant for Teams** 🧠

**Use Case**: Enable internal teams to quickly search and reference internal training or SOPs.

- **Content Sources**: Upload SOPs, onboarding files, technical how-tos, and internal checklists.
- **Use Case**: Instead of digging through folders, employees just ask the assistant.
- **Tip**: Create multiple assistants for different departments (Sales, Support, DevOps).

---

#### 🔹 Example 6: **Client Onboarding Assistant** 👥

**Use Case**: Guide new clients or partners through your onboarding process.

- **Content Sources**: Upload welcome decks, implementation checklists, and success guides.
- **Instructions**: Provide friendly and professional guidance.
- **Actions**:
  - Collect client details using input.


## ❓ Frequently Asked Questions (FAQs)

#### 🔸 Is it safe to upload sensitive content to the assistant?
Yes. All uploaded files are securely handled and sent to OpenAI’s servers only for use within your assistant. However, avoid uploading files with sensitive credentials or PII unless your OpenAI usage policy covers such data securely.

---

#### 🔸 Can I use multiple assistants for different websites or use cases?
Absolutely! You can create unlimited assistants in FlowMattic and configure each with unique styles, content, actions, and embed code.

---

#### 🔸 Does the assistant remember past conversations?
Yes, if you enable **“Load User Session Chats”** under the Setup tab. This keeps chat history for users during a session so they can continue conversations without losing context.

---

#### 🔸 Can I update the content files later?
Yes. You can revisit the **Content** tab, remove old files, and upload new ones anytime. The assistant will start using the updated content immediately once uploaded and indexed.

---

#### 🔸 Which OpenAI models are supported?
You can use any model available in your OpenAI account such as `gpt-3.5-turbo`, `gpt-4`, or `gpt-4-turbo`. If you're using content sources (files), make sure the selected model supports **retrieval** (like `gpt-4-turbo` with files).

---

#### 🔸 How can I test the chatbot before embedding?
Use the preview inside the configuration page. Type in test queries and verify if responses are accurate and actions trigger as expected. You can always click **Restart** to reset the chat session.

---

# Setting up FlowMattic Connect for X ( Twitter ) integration

Source: https://support.flowmattic.com/kb/article/8/setting-up-flowmattic-connect-for-x-twitter-integration

In this article, we will guide you through the process of setting up the FlowMattic Connect for the X ( Twitter ) integration using your custom app for Twitter.

You’ll learn how to create custom apps on Twitter, how to get your Client ID and Client Secret, and how to use it to connect your Twitter account with FlowMattic Connect.

And it’s not as difficult as it sounds, we have explained everything step by step so it’s super easy for you.

So let’s begin!

## What is Twitter APP?

A Twitter app is feature provided by X ( Twitter ) that allows you to use their API with your own API Key, Client ID and Client Secret.

In our case, we’ll be creating a custom Twitter app with basic information to get the Client ID and Client Secret which we will use to connect FlowMattic and your Twitter account using FlowMattic Connect and X integration.

## Signing up for Twitter Developer Account

To create a custom Twitter app, you must have an account on [Twitter Developer Platform](https://developer.x.com/en/portal/dashboard "Twitter Developer Platform").

If you don't have an account, you can create one here - [Twitter Developer Platform Signup](https://twitter.com/i/flow/signup "Twitter Developer Platform Signup").

## Creating Custom Twitter App

After creating your Twitter Developer account, you can simply follow the steps below to create a custom app for Twitter.

To generate required credentials for FlowMattic Connect, simply follow these steps:

Step 1: Go to your&nbsp;[Twitter Developer website](https://developer.x.com/en/portal/dashboard)&nbsp;and then click&nbsp;**Developer Portal**.

![](/storage/kb-images/da7f128a2e-twitter-developer-portal-1.png "twitter-developer-portal-1")

Step 2: Click&nbsp;**Sign up for Free Account**

![](/storage/kb-images/da69ca95e2-twitter-signup-developer-account.png "twitter-signup-developer-account")

Step 3: Describe your use cases, select all checkboxes, and click&nbsp;**Submit**

![](/storage/kb-images/b1888731b1-twitter-developer-aggrement.png "twitter-developer-aggrement")

Step 4: Go to the Project Dashboard, navigate to Apps &gt; App Settings, and click&nbsp;**Set up**&nbsp;under&nbsp;**User Authentication Settings**

![](/storage/kb-images/919256df09-user-application-settings.png "user-application-settings")

Step 5: To set up the app, select the following options:

- In the App Permissions section, select Read, Write, and Direct Messages

![](/storage/kb-images/c6de3ee541-user-application-settings-1.png "user-application-settings-1")

- In the Type of App section, select Web App and Automated App or Bot

![](/storage/kb-images/74cb917eeb-user-application-settings-2.png "user-application-settings-2")

- In the App Info section, enter the following details:
    1. Callback URI / Redirect URL:&nbsp;**https://api.flowmattic.com/oauth2/twitter**
    
    3. Website URL: Your Website URL where FlowMattic is installed

![](/storage/kb-images/9a6f46d8d2-user-application-settings-3.png "user-application-settings-3")

Step 6: Click Save and confirm the prompt by clicking **Yes**.

## Getting Your Client ID and Client Secrete

Once your custom app is created, go back to the app page in Twitter Developer Portal, and switch to **Keys and Tokens**.

Next, you will find the section at the bottom - **OAuth 2.0 Client ID and Client Secret**, where your client ID is listed, and you need to generate the Client Secret. Copy these details to a secure place where you can access them easily.

![](/storage/kb-images/7b410d6284-get-client-id-secret.png "get-client-id-secret")

Now, login to your WordPress site, and go to FlowMattic -&gt; [Connects](/kb/how-to-use-connects "How to use Connects?").

Click the Green button - Connect Integrations and search for X ( Twitter ). If the integration is not listed, you need to install it from Integrations page.

Enter the Client ID and Client Secret details and connect. That's it!

![](/storage/kb-images/a8def1c347-create-twiiter-connect.png "create-twiiter-connect")

---

# Set up Cloudflare Browser Rendering

Source: https://support.flowmattic.com/kb/article/201/set-up-cloudflare-browser-rendering

Cloudflare Browser Rendering lets FlowMattic render your templates through a real Chrome browser on Cloudflare's edge network. One Account ID and one API Token power three things at once:

- **PDF Template Builder** — produces pixel-accurate PDF exports. Without Cloudflare, PDF generation still works but falls back to the bundled mPDF engine, which lays out complex CSS, gradients, charts, and custom fonts slightly differently.
- **Image Template Builder** — when a workflow generates an image from a template, it renders through Browser Rendering, so configure Cloudflare before relying on image generation in production.
- **FlowMattic Browser integration and the AI Agent's `browse_url` tool** — screenshots, page-to-PDF, scraping, Markdown extraction, and OG images all use the same credentials.

Cloudflare's free plan includes a monthly Browser Rendering allowance that is enough for most sites; heavier use may need a paid plan.

## Step 1 — Copy your Cloudflare Account ID

1. Log in to your Cloudflare dashboard at `dash.cloudflare.com`.
2. Open any page under your account. The **Account ID** is shown in the right-hand sidebar.
3. Copy the value — it is a 32-character string such as `9c3dfc45229e2a3aa7a626f5b7fa1e3f`.

![Cloudflare dashboard with the right-hand sidebar visible and the **Account ID** field highlighted.](https://assets.infidesk.support/kb/inline/2026/07/sXnE5PY0mkkUffCmEfhkrcJgzuJrn1GgyKnRlpJm.png) Blur or crop out any other account identifiers.

## Step 2 — Create an API Token with Browser Rendering permission

1. Go to **My Profile → API Tokens** (`dash.cloudflare.com/profile/api-tokens`).
2. Click **Create Token**, then choose **Create Custom Token**.
3. Give the token a name such as `FlowMattic Browser Rendering`.
4. Under **Permissions**, set the row to **Account → Browser Rendering → Edit**. This is the only permission the token needs.
5. Under **Account Resources**, select the account you copied the ID from.
6. Click **Continue to summary**, then **Create Token**.
7. Copy the token now — Cloudflare shows it only once.

![The Cloudflare "Create Custom Token" screen with the permission row set to Account · Browser Rendering · Edit](https://assets.infidesk.support/kb/inline/2026/07/JXaNyDNOjVPT1zgUzyQA47KO42dJnQxcXPXfOnOE.png).

## Step 3 — Save the credentials in FlowMattic

1. In your WordPress admin, open **FlowMattic → Settings**.
2. Select the **Cloudflare** tab in the settings sidebar.
3. Paste your Account ID into **Cloudflare Account ID**.
4. Paste your token into **Cloudflare API Token**.
5. Click **Save**.

When both fields are filled, FlowMattic shows a green confirmation that Cloudflare Browser Rendering is configured and will be used automatically. If the fields are empty, FlowMattic instead notes that PDF exports fall back to the bundled mPDF renderer.

![FlowMattic Settings → Cloudflare tab with the Cloudflare Account ID and API Token fields and the green "configured" confirmation](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-cloudflare-01-settings-cloudflare.png)

Once saved, no further action is needed. The PDF Builder, Image Template Builder, Browser integration, and AI Agent browsing tools all pick up the credentials automatically on their next run.

---

# Share Credentials Securely with the Credentials Vault

Source: https://support.flowmattic.com/kb/article/235/share-credentials-securely-credentials-vault

Sometimes our support team needs temporary access to your site — a WordPress admin login, an FTP account, or an API key — to investigate an issue properly. Pasting passwords into a ticket reply is never a good idea: ticket threads travel by email, live in your inbox, and stay readable in the conversation forever.

The **Credentials Vault** solves this. It's a secure, encrypted space attached to each of your tickets where you can share access details safely — outside the ticket conversation, protected by a PIN you choose, and visible only to the agent working on your ticket.

## What is the Credentials Vault?

- **Encrypted at rest.** Everything you put in the vault is encrypted on our servers using industry-standard OpenSSL encryption. Your credentials are never stored — or shown — as plain text in the ticket thread.
- **Protected by your PIN.** When you create the vault, you choose a 4-digit PIN. Only the correct PIN reveals the contents to you later — a wrong PIN doesn't show an error, it shows scrambled nonsense.
- **Per ticket.** Each ticket has its own vault, so access you share for one issue never lingers on another.
- **Yours to delete.** You can update or delete the vault at any time. When the issue is resolved, remove it with one click.

## How to share credentials

**1. Open your ticket.** Log in to the support portal and open the ticket you want to share access for. You'll find the **Credentials Vault** panel in the sidebar:

![Credentials Vault panel with the Create Vault button](https://assets.infidesk.support/products/flowmattic/kb-images/credentials-vault/vault-01-card-empty.png)

**2. Click "Create Vault".** Enter the details our team needs — the site URL, a username and password, or anything else that's relevant. There's no limit on what you can include, and a short note (for example, "temporary admin user, please remove when done") is always helpful:

![Create Vault dialog with credentials and a 4-digit PIN](https://assets.infidesk.support/products/flowmattic/kb-images/credentials-vault/vault-02-create-modal.png)

**3. Set your Vault PIN.** Choose a 4-digit PIN and click **Create Vault**. Remember this PIN — you'll need it to view the vault contents yourself later.

That's it. The sidebar now confirms your credentials are shared, and the agent on your ticket is able to access them securely:

![Vault panel showing credentials shared, with View, Update and Delete](https://assets.infidesk.support/products/flowmattic/kb-images/credentials-vault/vault-03-card-shared.png)

## Viewing, updating and deleting your vault

- **View** — click *View* and enter your PIN to see exactly what you stored:

![Unlocked vault showing the stored credentials](https://assets.infidesk.support/products/flowmattic/kb-images/credentials-vault/vault-04-unlocked.png)

  If the text comes back looking scrambled, the PIN was incorrect — that's the encryption doing its job. Nothing is revealed without the right PIN, and there's no lockout to worry about; just try again:

![A wrong PIN shows scrambled text instead of the credentials](https://assets.infidesk.support/products/flowmattic/kb-images/credentials-vault/vault-05-wrong-pin.png)

- **Update** — replaces the vault contents and lets you set a new PIN. Useful when you rotate a password mid-ticket.
- **Delete** — removes the vault entirely. The agent immediately loses access, and the action is recorded on the ticket.

## How our agents access your vault

This is the part that should give you real confidence:

**Only the agent assigned to your ticket can open the vault.** Not other agents, not administrators — one person, the one actually working on your issue. If the ticket hasn't been assigned yet, nobody can open it at all. The agent opens the vault through a secure, server-side decryption path (they never need — or see — your PIN), and **every single access is recorded in the ticket's activity log**, along with when you created, updated or deleted the vault. Your credentials never appear in the ticket conversation, never travel by email, and disappear for good the moment you delete the vault or the ticket is removed.

## Good practices when sharing access

- Create a **temporary user** for us rather than sharing your own login, and remove it once the ticket is resolved.
- Mention any specifics in the vault note — staging vs. production, plugins we shouldn't touch, time windows.
- **Delete the vault** (or rotate the password) as soon as your issue is solved. It takes one click.

## Submitting as a guest?

The Credentials Vault is available on tickets in the support portal, so it needs a portal account. If you submitted your ticket as a guest, simply log in (or register with the same email) and open your ticket from **My tickets** — the vault panel will be waiting in the sidebar. Please never send passwords by email reply.

---

# Share Secrets Module

Source: https://support.flowmattic.com/kb/article/124/share-secrets-module

Share sensitive information securely through self-destructing links with FlowMattic's Share Secrets module. This guide walks you through creating workflows that generate secure, time-limited links for sharing passwords, API keys, and confidential data.

## Overview

Share Secrets allows you to:
- Create encrypted, self-destructing links for sensitive information
- Set time-based or view-based expiration
- Add password protection for extra security
- Customize the reveal page with your branding
- Receive notifications when secrets are accessed

![FlowMattic - Share Secret.gif](/storage/kb-images/a769757266-inline.png)


## Prerequisites

Before you begin, ensure you have:
- FlowMattic 5.5.0 or later installed
- An active FlowMattic license
- A workflow trigger configured (webhook, form submission, etc.)

## Step 1: Create a New Workflow

1. Navigate to **FlowMattic → Workflows** in your WordPress admin
2. Click **Add New Workflow**
3. Give your workflow a descriptive name (e.g., "Secure Password Sharing")

## Step 2: Configure Your Trigger

Choose a trigger based on your use case:

### Option A: Webhook Trigger
Use this when you want to trigger secret creation from external applications.

1. Select **Webhook** as your trigger
2. Copy the webhook URL for use in your external application
3. The webhook can receive the secret content as a POST parameter

### Option B: Form Submission Trigger
Use this when you want users to submit secrets through a form.

1. Select your form plugin trigger (WPForms, Gravity Forms, etc.)
2. Map the form field containing the secret content

## Step 3: Add the Share Secrets Action

1. Click the **+** button to add a new action
2. Search for **Share Secrets** in the integration list
3. Select **Create Secret Link** action

![Choose share secrets module.png](/storage/kb-images/5edb876aa3-inline.png)

## Step 4: Configure Secret Content

### Secret Content
Enter the sensitive information you want to share. You can:
- Type static content directly
- Use dynamic data from previous steps (click the database icon)
- Combine text with dynamic fields

**Example:**
```
Your temporary password is: {{trigger.password}}
Please change it after first login.
```

### Page Title
Set a title that appears on the reveal page. Keep it generic to avoid revealing the content type.

**Good examples:**
- "Secure Message"
- "Confidential Information"
- "Private Note"

**Avoid:**
- "Your Password"
- "API Keys"

## Step 5: Set Expiration Options

Choose how and when the secret should expire:

### Expiration Type

#### Time-Based Expiration
The secret expires after a set duration, regardless of views.

| Duration | Use Case |
|----------|----------|
| 5 minutes | One-time passwords, verification codes |
| 1 hour | Meeting credentials, temporary access |
| 24 hours | Daily passwords, shift handover info |
| 7 days | Project credentials, onboarding info |

#### View-Based Expiration
The secret expires after a set number of views.

| Views | Use Case |
|-------|----------|
| 1 view | Burn after reading - maximum security |
| 3 views | Small team sharing |
| 5 views | Department-wide distribution |

### Expiration Value
Enter the numeric value corresponding to your expiration type:
- For time-based: number of minutes, hours, or days
- For view-based: number of allowed views

## Step 6: Add Password Protection (Optional)

For additional security, enable password protection:

1. Enter a password in the **Password** field
2. The recipient will need to enter this password to view the secret
3. Share the password through a different channel (phone, SMS, etc.)

**Best practices:**
- Use a simple but not obvious password
- Never include the password in the same message as the link
- Consider using a verbal password for sensitive secrets

## Step 7: Configure Branding (Optional)

Customize the reveal page to match your brand:

### Branding Logo URL
Enter the full URL to your logo image:
```
https://yoursite.com/wp-content/uploads/logo.png
```

**Recommended specifications:**
- Format: PNG or SVG
- Max width: 200px
- Transparent background preferred

### Branding Text
Add custom text below the logo:
```
Secure message from Acme Corporation
```

### Button Style
Choose a color scheme for the reveal button:
- **Primary** - Blue/Indigo (default)
- **Secondary** - Gray
- **Success** - Green
- **Danger** - Red

## Step 8: Set Up Access Notifications (Optional)

Get notified when someone accesses your secret:

### Notification Email
Enter the email address to receive notifications:
```
security@yourcompany.com
```

### Notification Details
When enabled, you'll receive an email containing:
- Date and time of access
- IP address of the viewer
- Browser and device information
- Remaining views (for view-based secrets)
- Viewed by ( if user is logged in )

## Step 9: Customize Button Text (Optional)

### Reveal Button Text
Default: "Reveal Secret"

Customize to match your use case:
- "Show Password"
- "View Credentials"
- "Unlock Message"

### Copy Button Text
Default: "Copy to Clipboard"

Customize as needed:
- "Copy Password"
- "Copy to Clipboard"

## Step 10: Advanced Options

### Custom Messages

#### Expired Message Title
Shown when the secret has expired:
```
Link Expired
```

#### Expired Message
Detailed message for expired secrets:
```
This secure link has expired and the content is no longer available.
```

### Redirect URL
Redirect users to a specific page after the secret expires:
```
https://yoursite.com/request-new-password
```

### Custom CSS
Add custom styles to the reveal page:
```css
.fm-secret-container {
    font-family: 'Your Custom Font', sans-serif;
}
.fm-reveal-btn {
    border-radius: 20px;
}
```

## Step 11: Test Your Workflow

1. Click **Save** to save your workflow
2. Toggle the workflow status to **Active**
3. Trigger the workflow (submit form, call webhook, etc.)
4. Check the workflow execution log for the generated link
5. Open the link in an incognito window to test the user experience

## Step 12: Use the Generated Link

The Share Secrets action returns a `secret_url` that you can use in subsequent actions:

### Send via Email
Add an email action after Share Secrets:
```
Subject: Your Secure Access Link

Hi {{trigger.name}},

Click the link below to view your secure credentials:
{{share_secrets.secret_url}}

This link will expire in 24 hours.

Best regards,
Your Team
```

### Send via SMS
Use an SMS integration (Twilio, etc.):
```
Your secure link: {{share_secrets.secret_url}}
Password hint: First pet's name
```

### Store in Database
Save the link to your database for tracking:
- Secret URL
- Recipient email
- Creation timestamp
- Expiration time

---

## Common Use Cases

### 1. New Employee Onboarding
**Trigger:** HR form submission
**Content:** Initial login credentials
**Expiration:** 24 hours or 1 view
**Notification:** IT admin email

### 2. Client Credential Sharing
**Trigger:** Project management webhook
**Content:** API keys, FTP credentials
**Expiration:** 7 days or 3 views
**Branding:** Company logo and colors

### 3. Password Reset
**Trigger:** Support ticket creation
**Content:** Temporary password
**Expiration:** 1 hour or 1 view
**Password:** Verbal confirmation required

### 4. Secure Document Access
**Trigger:** Manual or scheduled
**Content:** Access codes, PINs
**Expiration:** Based on sensitivity
**Notification:** Always enabled

---

## Security Best Practices

1. **Use the shortest practical expiration time** - Reduce the window of vulnerability

2. **Enable password protection for highly sensitive data** - Add a second authentication factor

3. **Never include passwords in the same channel as links** - Use separate communication methods

4. **Enable notifications for audit trails** - Track who accessed what and when

5. **Use view-based expiration for maximum security** - "Burn after reading" ensures one-time access

6. **Customize expired message with next steps** - Guide users on how to request new credentials

7. **Regularly review notification emails** - Monitor for unauthorized access attempts

---

## Troubleshooting

### Secret link not working
- Check if the secret has expired (time or views)
- Verify the URL wasn't truncated in the email
- Ensure no extra characters were added to the link

### Password not accepted
- Passwords are case-sensitive
- Check for leading/trailing spaces
- Verify the correct password was shared

### Notification emails not received
- Check spam/junk folders
- Verify the email address is correct
- Ensure your WordPress can send emails

### Branding not showing
- Verify the logo URL is publicly accessible
- Check if the image URL uses HTTPS
- Ensure the image format is supported (PNG, JPG, SVG)

---

## Global Settings

Configure default settings for all Share Secrets links in **FlowMattic � Settings � Share Secrets Settings**:

### Error Page Button Text
Customize the button text on expired/error pages:
- Default: "Go to Homepage"
- Example: "Contact Support"

### Error Page Button URL
Set a custom destination for the error page button:
- Default: Site homepage
- Example: `https://yoursite.com/support`

---

## Output Data

The Share Secrets action returns the following data for use in subsequent steps:

| Field | Description | Example |
|-------|-------------|---------|
| `secret_url` | The full URL to access the secret | `https://yoursite.com/secret/abc123def456` |
| `secret_id` | Unique identifier for the secret | `abc123def456` |
| `expires_at` | Timestamp when the secret expires | `2025-12-10 15:30:00` |
| `max_views` | Maximum allowed views (if view-based) | `3` |

---

## Need Help?

- **Documentation:** Visit [flowmattic.com/docs](https://support.flowmattic.com/kb)
- **Support:** Contact us at [flowmattic.com/support](https://support.flowmattic.com/)
- **Community:** Join our [Facebook group](https://www.facebook.com/groups/flowmattic) for tips and discussions

---

# Sticky notes in the Workflow Builder

Source: https://support.flowmattic.com/kb/article/214/sticky-notes-in-the-workflow-builder

Sticky notes let you annotate a workflow canvas — explain why a branch exists, leave a reminder for a colleague, or paste a link to the ticket that prompted the automation.

They are purely visual. **A sticky note adds no steps, consumes no tasks, and cannot affect how your workflow runs.**

## Adding a note

In the Workflow Builder, click **Add sticky note** in the canvas controls. The note appears in the middle of your current view. Add several and they are offset slightly from one another rather than stacking exactly on top.

Click the note body to start typing. Notes have an optional title and a body.

## Moving a note — hold ⌘ or Ctrl

This is the one thing worth knowing up front, because it surprises everybody:

**To move a sticky note, hold ⌘ (Mac) or Ctrl (Windows) while you drag it.**

Without the modifier key, clicking the note puts you into text-editing mode instead of picking it up. That is intentional — it means you can click straight into a note to edit it without nudging it out of place. When a note is selected you will see a small `⌘ / Ctrl + drag to move` hint to remind you.

## Resizing

Select the note first, and resize handles appear on its edges. Drag any handle to resize. Notes will not go below roughly 180×120 pixels; there is no upper limit.

## Colours

Six colours are available: **yellow** (the default), **blue**, **green**, **pink**, **purple** and **grey**. Click the coloured dot in the note's toolbar and pick from the swatches. There is no custom colour or hex picker.

Colour is a good way to build a convention across a busy canvas — for example yellow for general notes, pink for known issues, green for "verified working".

## Links

Paste a URL into a note and it stays clickable. Handy for linking a support ticket, a spec, or the vendor's API documentation right where the relevant step is.

## How notes are saved

Notes are saved with the workflow, alongside your steps. There is nothing extra to do — save the workflow as normal.

One thing worth knowing if you move workflows between sites: notes are stored separately from the steps, so **tooling that only transfers steps and connections may not carry your notes across.** If you export a workflow and the notes are missing on the other side, that is why — the workflow itself will be intact.

## What sticky notes do not do

- They do not appear in your workflow's step list or step numbering.
- They are not included in task runs and do not count toward task usage.
- They do not open the step settings panel when clicked.
- They have no effect on execution order or workflow logic.

You can add as many as you like without any impact on how the workflow behaves.

---

# Style and Embed Your FlowMattic Chatbot

Source: https://support.flowmattic.com/kb/article/230/flowmattic-ai-assistant-embed

Once your assistant is set up and trained, make it look like *your* brand and drop it onto your site. Styling lives on the **Theme** tab; publishing is the **Embed** button in the top-right of the editor.

---

## Style your chatbot — the Theme tab

![The Theme tab](https://assets.infidesk.support/products/flowmattic/kb-images/ai-assistants/theme-tab.png)

### Theme Preset

Pick a **preset** to apply a unified look in one click — Default, Blue, Purple, Green, Teal, Indigo, Rose, Dark, and more — or choose **Custom** to set everything yourself. Toggle **Light** or **Dark** mode to match your site.

### Colors

- **Brand Color** — the primary color used for the chat header, buttons, and accents. Set it to your brand's hex value and the whole widget follows.
- Message appearance options let you fine-tune how bot and user bubbles look.

### Background

Add a custom **background image** for the chat area if you want more than a solid color.

Every change previews instantly in the right-hand pane, so you can dial in the look before you save. Widget options (launcher position, avatar, and icon) let you control how the popup appears on your site.

---

## Embed your chatbot

Click **Embed** in the top-right to open the embed options. There are three ways to add the assistant to your site:

![The Embed Chatbot dialog](https://assets.infidesk.support/products/flowmattic/kb-images/ai-assistants/embed-modal.png)

### Shortcode

Copy the `[flowmattic_chatbot …]` shortcode and paste it into any **WordPress post or page** to render the chatbot inline where you want it — perfect for a dedicated "Support" or "Ask us" page.

### iFrame

Use the **iFrame** snippet to embed the chatbot on **any website**, not just WordPress — drop it into a landing page, a help center, or a different platform.

### Popup Widget

Add the **Popup Widget** script for a floating launcher button in the corner of your site that opens the chat on click — the classic site-wide chatbot experience.

Copy the snippet for the method you want, paste it where it belongs, and your assistant is live.

---

## Tips

- **Match your brand color** first — it drives most of the widget's appearance in one setting.
- **Use the shortcode** for a focused, on-page assistant; **use the popup widget** for site-wide support.
- Re-open **Embed** any time — the snippet always reflects the assistant's current configuration.

---

**Related guides:** [Getting Started](https://support.flowmattic.com/portal/flowmattic/kb/article/227/flowmattic-ai-assistants-getting-started) · [Content Sources](https://support.flowmattic.com/portal/flowmattic/kb/article/228/flowmattic-ai-assistant-content-sources) · [Actions, Leads & Meetings](https://support.flowmattic.com/portal/flowmattic/kb/article/229/flowmattic-ai-assistant-actions)

---

# Tables

Source: https://support.flowmattic.com/kb/article/38/tables

### Step 1: Set the Database Location

The first thing you need to do to use the **Tables** feature in FlowMattic is to figure out where your database is located and connect to it if it’s on a different server. Here’s how you can do it step by step.

#### Is Your Database Local or Remote?

- **Local Database:** A local database is the one your current website is already using. Since FlowMattic is installed on this website, it can automatically access the database, so you don’t need to do anything extra. You can jump straight into creating and managing your tables.

- **Remote Database:** A remote database is hosted on another server, not on the website where FlowMattic is active. If your database is remote, you’ll need to connect it to FlowMattic first.

#### How to Connect a Remote Database

If you’re using a remote database, go to FlowMattic’s settings and find the **“Connect Database”** button. Click it, and you’ll see a form where you’ll need to enter some important information:

1. **Label:** Give your database a name you can easily recognize later. For example, “Order Management DB.”

3. **Description:** Write a short note about what this database is used for, like “Stores WooCommerce order details.”

5. **Database Name:** Type the exact name of your database.

7. **Database Host:** Enter the server’s address where your database is hosted. This could be an IP address or a domain name.

9. **Database User:** Provide the username needed to access your database.

11. **Database Password:** Enter the password for the username you provided.

#### Testing the Connection

Once you’ve entered all the details, click **“Test Connection”** to check if everything is set up correctly.

- **If it works:** You’ll get a success message, and your database will be ready to use in FlowMattic.

- **If it doesn’t work:** You’ll see an error message. Double-check what you entered especially the database name, host, username, and password, and try again.

---

# Text Formatter

Source: https://support.flowmattic.com/kb/article/27/text-formatter

Text Formatter by FlowMattic is a software tool used to perform various text-based operations such as finding and replacing strings, splitting text, and capitalizing text. This tool is designed to simplify and automate common text formatting tasks and streamline workflow efficiency.

The Text Formatter interface is user-friendly and easy to navigate, making it an ideal tool for both novice and experienced users. It offers a variety of features and functions to enhance text formatting capabilities.

**Step by Step Documentation for Text Formatter by FlowMattic:**

1. To create a new workflow on FlowMattic in WordPress, you need to first log in to your FlowMattic account and navigate to the "Dashboard". Once you're in the "Dashboard", you can select the "New Workflow" button to begin creating your new workflow..

Click on New Workflow

2. In the "Choose Application" section, select "Text Formatter by FlowMattic."&nbsp;

3. Select an Action Event. In the "Action Event" section, choose from the following options:

**3.1 Extract Pattern:** This refers to identifying and extracting specific patterns or sub-strings from a given text. This can be useful for tasks such as finding email addresses or phone numbers within a larger body of text.

**3.2 Find in Text:** This involves searching a text for a specific word, phrase, or pattern, and returning its location within the text. This can be useful for tasks such as searching a document for a specific keyword or phrase.

**3.3 Replace Text:** This involves replacing a specific word, phrase, or pattern with a different word, phrase, or pattern within a given text. This can be useful for tasks such as cleaning up text data by removing unwanted characters or replacing misspelled words.

**3.4 Basic Formatting:** This involves applying basic formatting options to a given text, such as changing the font size or color, adding bold or italicized text, or adding bullet points or numbered lists.

**3.5 Split Text:** This involves splitting a given text into smaller segments based on a specific delimiter or pattern, such as splitting a comma-separated list of names into individual names.

**3.6 Default Value:** This refers to setting a default value to be used in case a particular value is not present or is invalid. This can be useful for ensuring that data processing functions continue to run smoothly even in cases where data is missing or incorrect.


4\. If you choose "Extract Pattern":

you need to enter your content in the "Content" option. This can be any text that you want to extract information from using a regular expression.

Next, you need to define the regular expression in the "Regular Expression" option. A regular expression is a sequence of characters that define a search pattern. It is used to match and extract information from text. When entering your regular expression in this option, you do not need to include the enclosing slashes (/ /) that are typically used in regular expressions. Simply enter the pattern that you want to match.

5\. If you choose "Find in Text":

**5.1** Enter your content in the "Content" option: The content option is where you input the text or string where you want to search for a specific value. This could be a paragraph, a sentence, or any other text string where you want to locate a specific value or pattern.

**5.2** Enter the value to be searched in the "Search String" option: The "Search String" option is where you input the value or pattern you want to search for in the content. This could be a single word, a phrase, or a regular expression that you want to locate within the content.

**5.3** If found, the 'result' parameter returns the position of the string from the left; else, it returns -1: After inputting the content and the search string, the function will execute and search for the search string within the content. If the search string is found within the content, the 'result' parameter will return the position of the string from the left of the content where the search string was found. If the search string is not found within the content, the 'result' parameter will return -1, indicating that the search string was not found within the content.

6\. If you choose "Replace Text":

**6.1** First, you need to enter your content in the "Content" option. This is where you will input the text that you want to modify. You can either type or paste the content directly into the text field.

**6.2** Next, you will need to enter the value that you want to search for in the "Search For" option. This is the specific text that you want to replace within your content. For example, if you want to replace the word "apple" with the word "banana", you would enter "apple" in this field.

**6.3** Finally, you will need to enter the value that you want to replace the searched text with in the "Replace With" option. This is the new text that you want to use in place of the text you searched for. Continuing with the previous example, you would enter "banana" in this field.

7\. If you choose "Basic Formatting":

**7.1** the first step is to enter your content in the "Content" option. This could be any text that you want to format, such as a blog post, an email, or a social media update.

**7.2** Select the formatting method in the "Formatting Method" option. if you want to make a particular word or phrase stand out in your content, you can select the "Bold" formatting method and apply it to that text. If you want to emphasize a point in your content, you can use the "Italic" formatting method to add emphasis. If you want to create a list in your content, you can use the "Bullet Points" or "Numbered List" formatting method.

8\. If you choose "Split Text":

- Enter your content in the "Content" option.

- Enter the character or word separator to split the text on in the "Separator" option. For space as a separator, use \[space\].

- Select the segment of text to return after splitting in the "Segment Index" option and choose from various options available.

9\. Once you have selected your desired Action Event and entered the necessary information, click "Execute" to perform the operation.

#### **Conclusion**

Text Formatter by FlowMattic is a powerful and versatile tool designed to manipulate text-based content. By following the steps outlined above, you can perform various text-based operations, including finding and replacing strings, splitting text, capitalizing, and more. Additionally, the tool allows for customization, enabling users to save their own formatting rules for future use. Overall, Text Formatter by FlowMattic is a user-friendly and efficient solution for text formatting needs.

---

# The Bookings Public Booking Page: Shortcode, Block, Permalink and Branding

Source: https://support.flowmattic.com/kb/article/155/the-bookings-public-booking-page-shortcode-block-permalink-and-branding

Every Bookings calendar has a public-facing page where visitors pick an open time and book a meeting. You can share it as a standalone link, embed it in a post or page with a shortcode, or drop it in with a Gutenberg block. This guide covers all three ways to publish it, what a visitor sees, and how each branding setting changes the page.

## The shareable permalink

Every calendar automatically gets a clean public URL on your own domain:

```
https://yoursite.com/flowmattic-booking/{slug}/
```

The `{slug}` is the calendar's slug (for example `discovery-call`). You don't create a WordPress page for this — FlowMattic serves it directly as a standalone, theme-independent page. You can copy this URL from the calendar editor and paste it anywhere: an email signature, a "Book a call" button, social media, etc.

**Single-use links** look slightly different. Because they use an unguessable one-time token instead of a friendly slug, their URL is:

```
https://yoursite.com/flowmattic-booking/d/{token}/
```

The extra `/d/` segment signals a one-time link. Once that link has been used to book, it shows a friendly "already booked" notice instead of the calendar.

### Changing the URL prefix

The `/flowmattic-booking/` part is configurable. Go to **FlowMattic → Settings → Bookings** and set the **Booking URL slug** to whatever you like (lowercase letters, numbers and dashes only). Permalinks are flushed automatically when you change it, and all your calendar pages move under the new prefix.

![FlowMattic → Settings → Bookings showing the Booking URL slug field with the example URL preview beneath it](https://assets.infidesk.support/kb/inline/2026/07/nAAt3VzVpHhmYYHpDi4W7JiRj7R0veHqdOKm86QS.png).

## The shortcode

To embed the booking page inside an existing WordPress post or page, use:

```
[flowmattic_booking calendar="discovery-call"]
```

The single **calendar** attribute takes the calendar's slug (or its ID). The booking widget renders inline where you place the shortcode, inheriting your theme's surrounding layout. If you leave the `calendar` attribute empty, nothing renders.

## The Gutenberg block

FlowMattic also registers a booking **block** for the WordPress block editor. Add it like any other block and choose the calendar in the block's settings. It renders the same booking widget as the shortcode. If no calendar is selected, the block shows a "Select a booking calendar in the block settings" placeholder in the editor.

![The WordPress block editor with the FlowMattic booking block inserted and its calendar selector shown in the block settings sidebar](https://assets.infidesk.support/kb/inline/2026/07/svL57Pxf5IEpaX0tZUYyVwmr1S1Kpb4UXfj9wlVC.png).

## What a visitor sees

The booking page is a clean two-panel card:

**Left panel (the details rail):**
- The calendar's **logo** (if you uploaded one).
- The **host** — an avatar with the host's name and optional title.
- The **event name** (the calendar's name) as the heading.
- Meeting **details** — duration (e.g. "30 min"), location (e.g. "Google Meet"), and the visitor's selected time zone.
- The calendar **description**, if you wrote one.

**Right panel (the picker):**
- A month **calendar** showing only days with open slots.
- A list of available **time slots** for the selected day.
- A **time zone picker** so the visitor can switch to their own zone — all the offered times re-display in that zone automatically.

After choosing a day and time, the visitor fills in the **booking form**: name and email are always asked; phone, notes and guest emails appear only if you enabled those Invitee questions. For a Phone call location they're asked for a number; for an In-person location they're asked for the address. When they submit, a confirmation screen appears and a confirmation email goes out.

![A live public booking page showing the host rail on the left, the month calendar and time-slot list on the right, with the time-zone picker visible](https://assets.infidesk.support/kb/inline/2026/07/AfeJSqDdjNIENNpdQqfWybjcRjWNeuqaBgHOk3Ph.png).

### Reschedule and cancel

If you allowed rescheduling or cancellation, the invitee's emails contain secure manage links. Opening a reschedule link brings them back to the picker to choose a new time; a cancel link shows a confirmation card. These links are token-protected — no login is required, but they can't be guessed or reused after the booking is closed.

### Unavailable and booked states

If a calendar is paused or archived, the page renders a friendly "this scheduling link isn't available" notice rather than an error. A used single-use link shows an "already booked" notice. If the URL points to a calendar that doesn't exist, a clean branded 404 page is shown.

## Per-calendar branding

Open a calendar's editor and find the **Branding** section ("Make the booking page feel like yours"). Each setting below changes the visitor-facing page:

### Logo

The **Logo** field (marked optional) lets you upload or pick an image from the Media Library. When set, it appears at the top of the left rail above the host. Remove it to fall back to no logo.

### Host name and title

Optional per-calendar **Host name** and **Host title** override the account-wide defaults for this one calendar. The host name shows next to the avatar; the title is a smaller sub-label beneath it (for example "Founder & Head of Growth"). Leave them blank and the page falls back to the **Default host name** and **Default host title** set under FlowMattic → Settings → Bookings, which in turn fall back to your site name.

### Accent color

The **Accent color** tints the booking page — buttons, the selected day, and highlights all use it. It also color-labels this event across your calendars in the dashboard. Pick from the preset swatches or set a custom hex value.

![The Branding section of the calendar editor showing the Logo upload, Host name/title fields, the Accent color swatches, the Redirect after booking toggle, and the Show FlowMattic branding switch — with the Live preview card beside it](https://assets.infidesk.support/kb/inline/2026/07/KPARVv3bEVp42CEZKQgTYTqTMdUGmAnPmY5Ml8ec.png).

### Redirect after booking

By default, after someone books, they see FlowMattic's built-in confirmation screen. Turn on **Redirect after booking** and enter a URL (e.g. `yoursite.com/thank-you`) to send the visitor to your own page instead the moment their booking succeeds. This is handy for a custom thank-you page, an upsell, or conversion tracking.

### Show FlowMattic branding

A small **"Powered by FlowMattic"** credit appears in the booking page footer by default. The **Show FlowMattic branding** toggle (under "FlowMattic Credits") removes it when turned off, for a fully white-labeled page. This footer credit is also reflected in the booking emails — turning branding off here drops the "Powered by FlowMattic" line from those emails too.

## How it helps you

Because the page lives on your domain, your invitees never leave your brand to schedule. The logo, accent color, host details and optional white-labeling make it look like a native part of your site, the time-zone picker removes back-and-forth over "what time is that for you?", and the post-booking redirect lets you control exactly what happens after someone books.

---

# Train Your AI Assistant with Content Sources

Source: https://support.flowmattic.com/kb/article/228/flowmattic-ai-assistant-content-sources

An AI Assistant is only as helpful as what it knows. The **Content** tab is where you feed it your business's information — docs, web pages, FAQs, WordPress content — so it answers from *your* material instead of guessing. FlowMattic indexes what you add into the assistant's vector store and retrieves the most relevant pieces on every question (file search / RAG).

Open your assistant and switch to the **Content** tab.

![The Content tab with content sources](https://assets.infidesk.support/products/flowmattic/kb-images/ai-assistants/content-sources.png)

---

## Content sources

### Upload Files

Upload documents — PDFs, text, and similar — for the chatbot to learn from. Each uploaded file (and each crawled page or synced table chunk) appears in the list so you can see exactly what the assistant is drawing on, and remove anything that's out of date.

### Crawl Webpages

Point the assistant at public URLs — your website, docs, or help center — and FlowMattic scrapes the content into its knowledge. Great for keeping the bot in sync with pages you already maintain.

### Connect Tables

Sync FAQs and resources straight from a **FlowMattic Table** (up to 10,000 rows each). This is the tidiest way to manage a question/answer knowledge base: edit rows in your Table, re-sync, and the assistant stays current. Use it for support FAQs, product catalogs, policy snippets, and more.

### Sync WordPress Posts

Sync your WordPress content so the assistant can answer questions from your posts and pages — no copy-pasting, and it refreshes as your content changes.

### Sync Google Docs & Notion — coming soon

You'll see a **Sync Google Docs & Notion** section on the Content tab, but its Connect buttons are currently disabled — this source is on the roadmap and isn't available yet. For now, use the four sources above (uploading a Google Doc as a file, or crawling a public page, covers most cases in the meantime).

---

## How retrieval works

Everything you add is chunked and stored in the assistant's **vector store** (the *Vector Store ID* on the Setup tab). When a visitor asks a question, the assistant searches those chunks for the most relevant passages and answers from them — so replies stay grounded in your content rather than the model's general training.

---

## Tips for good answers

- **Keep it current.** Remove stale files and re-crawl or re-sync when your content changes.
- **Prefer structured sources.** A well-maintained FlowMattic Table of Q&A pairs often out-performs a big pile of prose.
- **Scope it.** Only add content you actually want the bot to speak from — more isn't always better.
- **Pair with Instructions.** Use the Setup → Instructions field to tell the assistant to answer *only* from its sources when accuracy matters.

---

**Related guides:** [Getting Started](https://support.flowmattic.com/portal/flowmattic/kb/article/227/flowmattic-ai-assistants-getting-started) · [Actions, Leads & Meetings](https://support.flowmattic.com/portal/flowmattic/kb/article/229/flowmattic-ai-assistant-actions) · [Style & Embed](https://support.flowmattic.com/portal/flowmattic/kb/article/230/flowmattic-ai-assistant-embed)

---

# Translating FlowMattic - Contributor Guide

Source: https://support.flowmattic.com/kb/article/136/translating-flowmattic-contributor-guide

FlowMattic is used by WordPress users around the world. To make the plugin accessible in more languages, we rely on volunteer translators who contribute translations through our dedicated translation portal.

This guide explains how to apply as a translator, get access, and start translating FlowMattic into your language.

---

## Overview

- **Translation Portal:** [https://translate.flowmattic.com](https://translate.flowmattic.com)
- **Tool Used:** [Loco Translate](https://wordpress.org/plugins/loco-translate/) (a WordPress plugin for managing translations)
- **Source Language:** English (US)
- **How It Works:** You translate strings in a web-based editor. Once your translation reaches a minimum completion percentage, it becomes available as a language pack that FlowMattic users can download automatically.

---

## Step 1: Apply to Become a Translator

1. Visit the translator application form at **[https://translate.flowmattic.com](https://translate.flowmattic.com)**.
2. Fill in the required details:
   - **Your Name**
   - **Email Address**
   - **Language(s)** you want to translate into (e.g., Spanish, French, German)
   - **WordPress Experience** (basic familiarity is enough)
3. Submit the form and wait for approval. You will receive an email with your login credentials once approved.

> **Note:** You do not need to be a professional translator. If you are a native speaker of your language and comfortable with basic WordPress terminology, you are welcome to apply.

---

## Step 2: Log In to the Translation Portal

Once approved:

1. Go to [https://translate.flowmattic.com/wp-login.php](https://translate.flowmattic.com/wp-login.php). 
2. Log in with the credentials provided in your approval email.
3. You will be redirected to the WordPress dashboard with access to the translation tools.

---

## Step 3: Open the Translation Editor

1. In the WordPress admin sidebar, go to **Loco Translate > Plugins**.
2. Click on **FlowMattic** from the plugin list.
3. You will see a list of existing languages. There are two possibilities:
   - **Your language already exists:** Click on it to open the editor.
   - **Your language does not exist yet:** Click **New Language** to add it (see below).

### Adding a New Language

If your language is not listed:

1. Click the **New Language** button.
2. In the **Choose a language** dropdown, select your language (e.g., "Spanish (Spain) - es_ES").
3. For the **Choose a location** option, select **System** — this stores files in `wp-content/languages/plugins/` which is the recommended location.
4. Click **Start Translating**.

---

## Step 4: Translate Strings

The Loco Translate editor shows a two-column interface:

| Column | Description |
|--------|-------------|
| **Source text** (top box) | The original English string. This is read-only. |
| **Translation** (bottom box) | Where you type your translation. |

### How to Translate

1. Click on a string in the list to select it.
2. The **source text** appears in the top box.
3. Type your translation in the **Translation** box below.
4. Press **Enter** or click the next string to move on.
5. Click **Save** (or press **Ctrl+S** / **Cmd+S**) periodically to save your progress.

### Tips for Translating

- **Placeholders:** Strings may contain placeholders like `%s`, `%d`, or `%1$s`. These are replaced with dynamic values at runtime. Always keep them in your translation in the same order.
  - Example: `"Step %d of %d"` → `"Paso %d de %d"` (Spanish)
- **HTML Tags:** Some strings contain HTML like `<strong>` or `<a>`. Keep these tags intact in your translation.
  - Example: `"Click <strong>Save</strong>"` → `"Haga clic en <strong>Guardar</strong>"`
- **Context:** If a string seems ambiguous, look at the **Reference** section below the editor. It shows the PHP file and line number where the string is used, which can help you understand the context.
- **Consistency:** Use consistent terminology throughout. For example, if you translate "workflow" as "flujo de trabajo" in one place, use the same term everywhere.
- **Do Not Translate:**
  - Brand names: "FlowMattic", "WordPress"
  - Technical identifiers: function names, API keys, URLs
  - Placeholder tokens: `{workflow_name}`, `{{variable}}`

### Translation Status Icons

| Icon | Meaning |
|------|---------|
| Blue dot | Translated |
| Empty | Not yet translated |
| Fuzzy (orange) | Needs review — the source string was updated and the translation may be outdated |

If you see a **fuzzy** string, review the source text and update your translation if needed, then uncheck the "Fuzzy" flag.

---

## Step 5: Track Your Progress

At the top of the Loco Translate editor, you will see a progress bar showing:

- **Total strings** in the plugin
- **Translated** count and percentage
- **Untranslated** count
- **Fuzzy** (needs review) count

Your translation must reach a **minimum completion percentage** (typically 60%) before it is included in the published language pack. Aim for 100% to provide the best experience for users in your language.

---

## Step 6: Build and Publish Your Translation

Once your translation has reached the minimum completion threshold:

1. Go to **Language Packs** in the WordPress admin sidebar.
2. You will see a list of all available translations with their completion percentages.
3. Click **Build** next to your language to generate the language pack.
4. The system will create a downloadable ZIP file containing your `.mo` and `.po` files.
5. The language pack becomes immediately available for FlowMattic users worldwide.

> **Note:** Only translations that meet the minimum completion percentage can be built. If your language shows as "Below minimum," continue translating until you reach the threshold.

---

## How Users Get Your Translation

Once a language pack is published:

1. A FlowMattic user changes their WordPress site language (in **Settings > General > Site Language**) to the language you translated.
2. FlowMattic automatically checks for available translations.
3. The translation is downloaded and installed to `wp-content/languages/plugins/`.
4. The plugin interface appears in the translated language.

Users can also manually check for translations from the **Plugins** page by clicking the **Check Translations** link next to FlowMattic.

---

## Updating Your Translation

FlowMattic adds new strings with each release. To keep your translation up to date:

1. Log in to the translation portal.
2. Open the FlowMattic translation for your language.
3. New untranslated strings will appear at the top of the list.
4. Translate the new strings and save.
5. Build the updated language pack from the **Language Packs** page.

You will be notified by email when new strings are added and your translation needs updating.

---

## Frequently Asked Questions

### Do I need coding experience?
No. The translation interface is entirely visual. You just type translations for each string.

### Can I translate into multiple languages?
Yes. You can contribute to as many languages as you are comfortable with.

### What if I am not sure how to translate a string?
Skip it and come back later. You can also leave a comment or reach out to us for context.

### How long does it take?
FlowMattic has a significant number of translatable strings. A full translation might take several sessions depending on the language. You can save your progress and return anytime.

### What happens if I stop contributing?
Your completed translations remain available. Other translators can pick up where you left off.

### Can I edit someone else's translation?
If you have access to a language, you can improve or correct existing translations.

---

## Need Help?

If you have questions about the translation process or encounter any issues:

- **Email:** support@flowmattic.com
- **Translation Portal:** [https://translate.flowmattic.com](https://translate.flowmattic.com)

We appreciate every contribution, no matter how small. Thank you for helping make FlowMattic accessible to users around the world!

---

# Trigger a workflow on bookings

Source: https://support.flowmattic.com/kb/article/202/trigger-a-workflow-on-bookings

Every booking lifecycle event fires a trigger you can build a workflow on — to push the invitee into a CRM, post to Slack, write to a Table, or send a custom message. This guide covers connecting a workflow to bookings.

## Step 1 — Create a workflow with the Bookings trigger

1. Go to **FlowMattic → Workflows** and add a new workflow.
2. Choose **FlowMattic Bookings** as the trigger app.
3. Choose the trigger event — **New Booking** is the most common.

![The workflow trigger picker with FlowMattic Bookings selected and New Booking chosen](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-bookings-wf-booking-trigger.png)

## Step 2 — Scope the trigger to a calendar

In the trigger settings, use the **Calendar** picker (marked *Optional*) to choose the calendar you want, or leave it on **Any calendar** to fire for every calendar on the site.

## Step 3 — Map the booking data

Click **Capture Response** and make one test booking so FlowMattic pulls the field keys into the workflow, then map the fields in your actions. Every booking event exposes the same flat payload, including `customer_name`, `customer_email`, `customer_phone`, `booking_date`, `booking_time`, `booking_end`, `duration_minutes`, `location`, `guests`, `notes`, `status`, and `manage_url`.

![An action step with the variable picker open, showing the captured booking fields](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-bookings-wf-booking-fields.png)

## Step 4 — Branch on status if you use one workflow for all events

Because every lifecycle event (created, rescheduled, cancelled, completed, no-show, deleted) uses the same payload shape and carries a `status`, you can build one workflow that reacts to all of them and branch on `status` with a Router or Filter — rather than duplicating a workflow per event. Alternatively, scope separate workflows to individual events.

## Step 5 — Turn the workflow on

Save and enable the workflow. The next matching booking event will run it.

---

# Troubleshooting Workflow Editor or Action Step Settings Loading Issues

Source: https://support.flowmattic.com/kb/article/47/troubleshooting-workflow-editor-or-action-step-settings-loading-issues

#### Overview
If the workflow editor or action step settings popup fails to load, it can disrupt your ability to manage workflows effectively. This article provides a comprehensive guide to identify and resolve common issues that may prevent the workflow editor from functioning properly.

#### Common Causes and Solutions

###### 1. **Browser Cache**
   - Cached files in your browser may interfere with the loading of the workflow editor.
   - **Solution**: Clear your browser cache and refresh the page.

###### 2. **Browser Extensions**
   - Certain browser extensions can conflict with the workflow editor.
   - **Solution**: Disable all browser extensions temporarily and try reloading the editor.

###### 3. **Browser Compatibility**
   - Some browsers may not fully support the workflow editor.
   - **Solution**: Switch to a different browser and check if the issue persists.

###### 4. **JavaScript Conflicts from Plugins or Themes**
   - Other plugins or themes may load JavaScript (JS) files that cause errors, preventing the editor from loading.
   - **Solution**:
     1. Open your browser's developer console (usually accessible via `F12` or `Ctrl+Shift+I`).
     2. Check for any JavaScript errors in the console.
     3. Disable other plugins or switch to a default theme to identify the conflicting source.

###### 5. **Website SSL Settings**
   - If your site is accessed via HTTPS but the WordPress Address and Site Address settings are configured for HTTP, it may cause loading issues.
   - **Solution**:
     1. Navigate to `Settings > General` in your WordPress dashboard.
     2. Ensure both the **WordPress Address** and **Site Address** fields are set to `https://`.

#### Additional Tips
- After implementing any of the above solutions, clear your browser cache and reload the page.
- Test the workflow editor on an incognito browser window to bypass potential cache or extension issues.

#### When to Contact Support
If none of the above solutions resolve the issue, reach out to the support team for further assistance. Provide with details of the troubleshooting steps you've already attempted and any error messages observed in the browser console.

By following these steps, you should be able to diagnose and resolve most issues with the workflow editor not loading.

---

# Understanding MCP Server Admin Screen

Source: https://support.flowmattic.com/kb/article/90/understanding-mcp-server-admin-screen

The FlowMattic MCP Server admin screen is your central hub for managing your Model Context Protocol server and all its tools. This comprehensive interface allows you to configure, monitor, and maintain your MCP server with ease.

## Overview

The MCP Server admin screen provides a modern, intuitive interface for managing your server and tools. Whether you're a developer integrating custom functions or a business user automating workflows, this interface gives you complete control over your MCP server configuration.

 
 ![FlowMattic_MCP_Server_admin.png](/storage/kb-images/105e3b586e-inline.png)

## Header Section

### Server Management Title
The header displays "MCP Server Management" along with a brief description of the server's purpose. This section also includes the primary "Add New Tool" button for quick access to tool creation.

### Quick Actions
- **Add New Tool Button**: Primary blue button that opens the tool creation modal
- **Settings Icon**: Provides access to server configuration options
- **History Icon**: Links to the execution history page

## Server Information Card

The server info card is the main dashboard for your MCP server, displaying critical information and providing quick access to essential functions.

![MCP Server ‹ FlowMattic — WordPress 2025-07-27 at 5.13.35 AM.png](/storage/kb-images/e260894d63-inline.png)

### Server Status and Details

**Server Name**: Displays the friendly name of your MCP server (default: "FlowMattic MCP")

**Status Indicator**: 
- **Active** (Green): Server is running and accepting connections
- **Inactive** (Gray): Server is disabled and not accessible

**Server Description**: Brief explanation of the server's capabilities and purpose

### MCP Server URL Section

**Server URL Display**: Shows your unique MCP server URL with security masking (asterisks hide sensitive parts)

**Copy Button**: One-click copying of the complete server URL to clipboard

**Connect Button**: Opens the client configuration modal with instructions for various MCP clients

**Important Notes**:
- The URL is your server's endpoint for MCP client connections
- Some clients may require appending `/sse` for Server-Sent Events support
- Treat this URL like a password - it provides access to your server tools

### Action Buttons

**Settings Button**: Opens server configuration modal for:
- Changing server name
- Enabling/disabling the server
- Managing server-level preferences

**History Button**: Navigates to the execution history page showing:
- All tool executions
- Success/failure rates
- Execution timestamps
- Performance metrics

## Available Tools Section

This section displays all tools configured on your MCP server, providing both overview statistics and detailed tool management.

![MCP Server ‹ FlowMattic — WordPress 2025-07-27 at 5.14.39 AM.png](/storage/kb-images/6f947f5e8f-inline.png)

### Tools Overview Statistics

**Tool Count**: Shows total number of configured tools

**Execution Summary**: Displays total executions across all tools and number of tools that have been used

### Tool Filtering and Search

**Type Filter Dropdown**: Filter tools by execution method:
- All Types
- PHP Function
- Workflow
- API Endpoint
- Database Query

**Search Box**: Real-time search through tool names for quick location

### Tool Cards

Each tool is displayed as a card containing comprehensive information and management options.

![MCP Server ‹ FlowMattic — WordPress 2025-07-27 at 5.15.51 AM.png](/storage/kb-images/2936b50f10-inline.png)

#### Tool Card Elements

**Tool Icon**: Visual indicator based on execution method:
- Code icon for PHP Functions
- Workflow icon for FlowMattic Workflows  
- Link icon for API Endpoints
- Database icon for Database Queries

**Tool Name**: The display name used by MCP clients

**Tool Description**: Brief explanation of the tool's functionality

**Execution Method Badge**: Color-coded badge showing the tool type:
- Green: PHP Function
- Blue: Workflow
- Purple: API Endpoint
- Orange: Database Query

**HTTP Method Badge** (API tools only): Shows GET, POST, PUT, or DELETE

**Plugin Badge** (Plugin tools): Indicates tools added by external plugins

#### Execution Statistics

**Execution Count**: Shows total number of times the tool has been used
- Displays "0" for unused tools
- Shows formatted numbers for used tools (e.g., "1.2K" for 1,200 executions)

**Last Execution**: Shows when the tool was last used
- "Never" for unused tools
- Relative time for recent usage (e.g., "2 hours ago", "Last week")

**Success Rate** (on hover): Percentage of successful vs. failed executions

#### Tool Management Menu

Each tool card includes a three-dot menu with available actions:

**For Database Tools**:
- **Edit Tool**: Modify tool configuration
- **Duplicate**: Create a copy of the tool
- **Tool History**: View execution logs for this specific tool
- **Delete Tool**: Remove the tool (with confirmation)

**For Plugin Tools**:
- **Tool History**: View execution logs (tools from plugins cannot be edited or deleted)

## Tool Types and Execution Methods

### PHP Function Tools
- Execute custom PHP functions defined in your WordPress installation
- Support both individual parameters and array-based parameter passing
- Ideal for custom business logic and data processing

### Workflow Tools  
- Execute FlowMattic workflows when called by MCP clients
- Workflow must be published and active
- Perfect for complex automation sequences

### API Endpoint Tools
- Make HTTP requests to external APIs
- Support for all HTTP methods (GET, POST, PUT, DELETE)
- Built-in authentication via FlowMattic Connects
- Optional webhook integration for async processing

### Database Query Tools
- Execute SQL queries directly against your WordPress database
- Support for dynamic parameters using `:param_name` syntax
- Requires careful consideration of security implications

### Plugin Tools
- Tools automatically added by installed WordPress plugins
- Read-only in the admin interface
- Managed by the originating plugin

## Client Connection Management

The Connect button opens a comprehensive modal for connecting various MCP clients to your server.

![MCP Server ‹ FlowMattic — WordPress 2025-07-27 at 5.17.01 AM.png](/storage/kb-images/18920bbe21-inline.png)

### Supported Clients

**AI Assistants**:
- Claude Desktop
- Claude Assistant (Chat)
- Mindpal
- n8n AI Agent

**APIs**:
- OpenAI API
- OpenAI API Playground

**Code Editors**:
- VS Code
- Warp
- Windsurf  
- Cursor

**Voice Assistants**:
- Vapi
- ElevenLabs

And many more...

### Configuration Instructions

Each client provides detailed, step-by-step setup instructions including:
- Prerequisites and requirements
- Specific configuration code/JSON
- Copy-paste ready configurations
- Platform-specific guidance

## Server Settings Management

The Settings modal allows you to configure server-level options:

![MCP Server ‹ FlowMattic — WordPress 2025-07-27 at 5.17.33 AM.png](/storage/kb-images/cf9489b65c-inline.png)

**Server Name**: Change the display name for your MCP server

**Server Active Toggle**: Enable or disable the entire server
- When disabled, all tools become inaccessible
- Client connections will fail
- Useful for maintenance or troubleshooting

## Best Practices

### Security Considerations
- Keep your MCP server URL confidential
- Regularly review tool execution history
- Disable the server when not in use for extended periods
- Monitor execution patterns for unusual activity

### Performance Optimization
- Archive or remove unused tools
- Monitor execution success rates
- Use appropriate execution methods for your use cases
- Regular cleanup of execution history

### Organization Tips
- Use descriptive tool names and descriptions
- Group related tools with consistent naming conventions
- Leverage filtering and search for large tool collections
- Document tool purposes and parameter requirements

## Troubleshooting Common Issues

### Server Connection Problems
- Verify server is active (green status indicator)
- Check MCP client configuration matches server URL exactly
- Ensure network connectivity between client and server

### Tool Execution Failures
- Review tool history for error messages
- Verify required parameters are provided correctly
- Check execution method configuration
- Validate API endpoints and authentication

### Performance Issues
- Monitor execution counts and patterns
- Review database query efficiency
- Check for resource-intensive operations
- Consider workflow optimization

## Related Resources

For more information about specific aspects of MCP server management:

- [How to Add MCP Tools in FlowMattic MCP Server](https://support.flowmattic.com/kb/article/91/)
- [FlowMattic MCP Server: Developer Integration Guide](https://support.flowmattic.com/kb/article/89/)


The MCP Server admin screen provides everything you need to effectively manage your automation tools and workflow integrations. With its intuitive interface and comprehensive features, you can easily configure, monitor, and optimize your MCP server for maximum productivity.

---

# Understanding MCP Tool Execution History

Source: https://support.flowmattic.com/kb/article/92/understanding-mcp-tool-execution-history

The MCP Tool Execution History page provides comprehensive monitoring and analytics for all tool executions on your FlowMattic MCP server. This interface allows you to track performance, debug issues, and analyze usage patterns of your MCP tools.

## Overview

The execution history page serves as your monitoring dashboard, recording every interaction between MCP clients (like Claude Desktop, VS Code, etc.) and your FlowMattic MCP server. It provides detailed insights into tool performance, success rates, and usage patterns.

![MCP Tools History ‹ FlowMattic — WordPress 2025-07-27 at 6.10.26 AM.png](/storage/kb-images/51c4a5eead-inline.png)

## Accessing Execution History

You can access the execution history in two ways:

1. **Server-wide History**: From the main MCP Server admin page, click the "History" button to view all tool executions across the server
2. **Tool-specific History**: From any tool's dropdown menu, select "Tool History" to view executions for that specific tool only

## Page Header

### Navigation Elements

**Page Title**: Shows either "MCP Server Execution History" for all tools or "[Tool Name] - Execution History" for specific tools

**Export Button**: Downloads execution data in CSV or JSON format for external analysis

**Back to Server Button**: Returns you to the main MCP Server admin page


## Server Information Card

The server info card displays:

- **Server Name**: The name of your MCP server
- **Tool-specific Info** (when viewing single tool): Shows the specific tool name and its execution method (PHP Function, Workflow, API Endpoint, etc.)

## Filtering and Controls

### Filter Options

**Items per Page**: Control how many execution records to display
- Options: 10, 25, 50, or 100 executions per page
- Useful for managing large execution logs

**Date Range Filter**: Narrow down executions by time period
- **All Time**: Shows all recorded executions
- **Today**: Shows only today's executions
- **This Week**: Shows executions from the current week
- **This Month**: Shows executions from the current month

**Refresh Button**: Manually reload the execution history to see the latest data

![MCP Tools History ‹ FlowMattic — WordPress 2025-07-27 at 6.11.48 AM.png](/storage/kb-images/c74ac5844f-inline.png)

## Execution History Table

The main table displays execution records with the following columns:

### Tool Column
- **Tool Name**: The display name of the executed tool
- **Tool ID**: The unique identifier used internally (shown in smaller text)

### Status Column
- **Success**: Green indicator with checkmark icon for successful executions
- **Error**: Red indicator with X icon for failed executions

### Executed At Column
- **Timestamp**: Shows the exact date and time when the tool was executed
- **Format**: Displays in your local time format

### Execution Time Column
- **Duration**: Shows how long the tool took to execute (in seconds)
- **Format**: Displayed with 3 decimal places for precision (e.g., "0.002s")

### Client Column
- **Client Type**: Shows which MCP client was used to execute the tool
- **Common Types**: Claude, OpenAI, Node MCP Client, etc.
- **Badge Format**: Displayed as a small badge for easy identification

### Actions Column
- **View Details Button**: Opens the detailed execution modal with comprehensive information

![MCP Tools History ‹ FlowMattic — WordPress 2025-07-27 at 6.10.26 AM.png](/storage/kb-images/2e9f30887e-inline.png)

## Execution Details Modal

Clicking "View Details" opens a comprehensive modal with detailed information about the specific execution.

![MCP Tools History ‹ FlowMattic — WordPress 2025-07-27 at 6.16.03 AM.png](/storage/kb-images/8f9dae4406-inline.png)

### Execution Information Section
- **Tool Name**: The executed tool's display name
- **Execution ID**: Unique identifier for this specific execution
- **Status**: Success or error indicator
- **Executed At**: Precise timestamp of execution

### Client Information Section
- **Client Type**: The MCP client that initiated the execution
- **User Agent**: Technical details about the client software
- **IP Address**: The IP address from which the execution was initiated
- **Execution Time**: Precise execution duration

### Arguments Section
- **JSON Format**: Shows the exact parameters passed by the MCP client
- **Copy Button**: Allows copying the arguments for debugging or testing
- **Formatted Display**: Pretty-printed JSON for easy reading

### Results Section
- **JSON Format**: Shows the complete response returned to the MCP client
- **Copy Button**: Allows copying the results for analysis
- **Includes**: Both successful results and error messages when applicable

## Pagination Controls

When there are multiple pages of execution history:

### Information Display
- **Results Summary**: Shows "Showing X to Y of Z items" to indicate current view
- **Current Position**: Clearly indicates which results you're viewing

### Navigation Controls
- **Previous/Next Buttons**: Navigate between adjacent pages
- **Page Numbers**: Direct links to specific pages
- **Ellipsis Indicators**: Show when there are many pages available


## Export Functionality

### Export Modal
The export feature allows you to download execution history for external analysis:

**Export Format Options**:
- **CSV**: Comma-separated values for spreadsheet applications
- **JSON**: JavaScript Object Notation for programmatic analysis

**Date Range Selection**:
- **Start Date**: Optional beginning date for the export
- **End Date**: Optional ending date for the export
- **Empty Dates**: Exports all available data

**Limitations**:
- Limited to 10,000 most recent executions
- Includes all execution details and metadata

![MCP Tools History ‹ FlowMattic — WordPress 2025-07-27 at 6.16.50 AM.png](/storage/kb-images/69ed7e9a94-inline.png)

## Understanding Execution Data

### Success vs Error Analysis
- **Success Rate**: Monitor the percentage of successful tool executions
- **Error Patterns**: Identify tools that frequently fail
- **Performance Trends**: Track execution times over time

### Client Usage Patterns
- **Popular Clients**: See which MCP clients are used most frequently
- **Client-specific Issues**: Identify if certain clients have higher error rates
- **Usage Distribution**: Understand how different clients interact with your tools

### Performance Monitoring
- **Execution Times**: Identify slow-performing tools
- **Peak Usage**: Understand when tools are used most heavily
- **Resource Usage**: Monitor server load patterns

## Empty State

When no execution history is available, the page displays:
- **Empty State Message**: "No Execution History"
- **Explanation**: Indicates that executions will appear once tools are called
- **Next Steps**: Guidance on using tools through MCP clients

## Troubleshooting with Execution History

### Debugging Failed Executions
1. **Check Error Messages**: View detailed error information in the execution details
2. **Examine Arguments**: Verify that correct parameters were passed
3. **Review Timing**: Check if timeouts or performance issues occurred

### Performance Analysis
1. **Identify Slow Tools**: Look for executions with high execution times
2. **Usage Patterns**: Understand peak usage periods
3. **Client Behavior**: Analyze how different clients use your tools

### Security Monitoring
1. **IP Address Tracking**: Monitor where executions originate
2. **Usage Frequency**: Identify unusual activity patterns
3. **Client Analysis**: Verify expected client types are being used

## Best Practices

### Regular Monitoring
- **Weekly Reviews**: Check execution success rates and performance
- **Error Analysis**: Investigate any failed executions promptly
- **Performance Trends**: Monitor for degradation in execution times

### Data Management
- **Regular Exports**: Backup execution history for long-term analysis
- **Archive Old Data**: Export and clean up old execution records periodically
- **Documentation**: Keep notes on significant execution patterns or issues

### Security Practices
- **Monitor Access**: Review client types and IP addresses regularly
- **Unusual Activity**: Investigate unexpected execution patterns
- **Rate Limiting**: Consider implementing rate limits for heavily used tools

## Related Features

### Integration with Main Admin
- **Tool Cards**: Execution counts displayed on main admin tool cards
- **Quick Access**: Direct links from tool management to execution history
- **Status Indicators**: Real-time status updates based on recent executions

### Performance Insights
- **Execution Counts**: Track total number of tool uses
- **Success Rates**: Monitor reliability of individual tools
- **Usage Analytics**: Understand which tools are most valuable

## Next Steps

After reviewing execution history:

1. **Optimize Performance**: Improve slow-executing tools based on timing data
2. **Fix Errors**: Address tools with high failure rates
3. **Scale Resources**: Plan server capacity based on usage patterns
4. **Enhance Security**: Implement additional monitoring based on access patterns

## Related Resources

- [Understanding MCP Server Admin Screen](https://support.flowmattic.com/kb/article/90) - Learn about the main admin interface
- [How to Add MCP Tools](https://support.flowmattic.com/kb/article/91) - Create and configure tools
- [FlowMattic MCP Server: Developer Integration Guide](https://support.flowmattic.com/kb/article/89/) - Advanced integration information

The execution history page is an essential tool for maintaining and optimizing your MCP server, providing the insights needed to ensure reliable, high-performance tool operations for your AI assistant integrations.

---

# Understanding Routers, Filters, and Action Step Conditions in Workflow Automation

Source: https://support.flowmattic.com/kb/article/53/understanding-routers-filters-and-action-step-conditions-in-workflow-automation

### Overview
In workflow automation, understanding when to use Routers, Filters, or Action Step Conditions is critical for optimizing your workflows. These tools allow you to control conditional logic and streamline processes effectively. Below is a detailed guide on each of these components, their use cases, and tips for implementation.

---

### Routers
Routers are used to route workflows into different paths based on conditions. This is particularly useful when workflows need to branch out into multiple directions, executing distinct sets of actions.

#### **When to Use Routers?**
- When you have multiple conditions to evaluate and need to route workflows into separate paths.
- When you want to perform actions based on **Round Robin** or **Random selection**.
- When multiple actions need to be executed based on different conditions.

#### **Example Use Case:**
Imagine a workflow that processes customer inquiries. Based on the category of the inquiry (e.g., billing, technical support, or general), the Router can direct the workflow to specific teams.

---

### Filters
Filters are used to evaluate data against specific conditions and determine whether the workflow should proceed. If the conditions are not met, the workflow stops, or actions can be adjusted based on the filter's logic.

#### **When to Use Filters?**
- When you want to filter data based on specific conditions before executing subsequent actions.
- When you need to stop the workflow if certain conditions are not satisfied.
- When further actions in the workflow should only execute if specific criteria are met.

#### **Example Use Case:**
A workflow processes form submissions. You can use a Filter to validate whether a required field (e.g., email address) is present. If the field is missing, the workflow will halt.

---

### Action Step Conditions
Action Step Conditions allow you to control whether a specific action step within a workflow is executed. These conditions are evaluated at the step level.

#### **When to Use Action Step Conditions?**
- When you want to execute a specific action step only if certain conditions are met.
- When you need to skip the execution of an action step if conditions are not fulfilled.

#### **Example Use Case:**
In an email marketing workflow, you can set an Action Step Condition to send a promotional email only to users who have opted in for marketing communications.

---

### Tips for Implementation
1. **Combine Strategically:** Use Routers, Filters, and Action Step Conditions together for complex workflows to maximize efficiency.
2. **Test Thoroughly:** Before deploying, test workflows to ensure conditions and logic behave as expected.
3. **Document Logic:** Clearly document the purpose of each Router, Filter, or Action Step Condition for easier maintenance.

---

By understanding these tools and their use cases, you can build robust, efficient, and highly customizable workflows tailored to your specific needs.

---

# Understanding Settings Page

Source: https://support.flowmattic.com/kb/article/35/understanding-settings-page

### **FlowMattic Settings Page**

The Settings page in FlowMattic is your centralized hub for managing global configurations, notifications, integrations, and workflow optimization. Below is a detailed explanation of each setting, now including the latest additions in version 5.0.

* * *

#### **1\. Custom Table Databases** _(New in v5.0)_

This section allows you to manage connections to custom table databases, whether local or external.

- **Connect Database**: Add new database connections, enabling the use of external databases for storing and managing data tables.

- **Fetch Existing Tables**: Toggle this option to fetch and edit existing tables from the connected database directly within FlowMattic.

- **Current Site Database**: The local WordPress database will remain an available option by default.

This feature is ideal for users who wish to offload data operations to external databases, keeping the WordPress site optimized.

* * *

#### **2\. Workflow Builder Settings** _(New in v5.0)_

This section provides settings to control the default behavior of the Workflow Builder.

- **Default Workflow Builder**: Choose between the new **Visual Workflow Builder** (introduced in v5.0) or the classic **Static Workflow Builder**.

- **Default Folder**: Set the default folder where all new workflows will be saved. This eliminates the need to manually organize workflows post-creation.

* * *

#### **3\. SMTP Settings for FlowMattic Email Module** _(New in v5.0)_

Simplify email delivery across workflows by configuring global SMTP settings.

- **Server Name**: Enter the SMTP server (e.g., `smtp.gmail.com`).

- **Port Number**: Provide the server port (e.g., 587 for TLS).

- **Username and Password**: Enter the SMTP credentials.

- **Encryption Type**: Select the encryption method (SSL or TLS).

Once configured, select **FlowMattic Default** as the email provider in workflows, and these settings will be used for email delivery.

* * *

#### **4\. Notification of Failed Tasks**

- **Enable Notifications**: Toggle to receive notifications when a workflow task fails.

- **Notification Email**: Specify the email address to receive these notifications.

* * *

#### **5\. Notification of Authentication Expiry**

- **Enable Notifications**: Enables alerts for expiring or expired API authentication tokens.

- **Notification Email**: Define the email address for these notifications.

* * *

#### **6\. Task Clean Interval**

- **Interval (in days)**: Specify how often old task history should be cleaned. For example, setting it to 30 removes task history older than 30 days.

* * *

#### **7\. Allow Integration Deletion**

- **Enable/Disable**: Control whether users with the Workflow Manager role can delete integrations. When disabled, only admin users can perform this action.

* * *

#### **8\. Allow Integration Page Access**

- **Enable/Disable**: Manage whether Workflow Manager users have access to the Integrations page.

* * *

#### **9\. Webhook URL Base**

- **Regular**: Default option using WordPress permalinks for webhook URLs.

- **REST API**: Use this option if you face issues with permalink-based webhooks. REST API-based URLs are more robust in certain server configurations.

* * *

#### **10\. Disable Core Integrations**

- **Toggle Core Integrations**:
    
    - This section allows you to disable core integrations that are not being used, which can help declutter the workflow editor and improve usability.
    - You will find several core integrations listed here, with a toggle option next to each one. You can turn off any integration that you don’t use to streamline the interface.
    
    **List of Core Integrations Available to Enable/Disable**:

- **Webhooks**: Send or receive data via webhooks.

- **Number Formatter**: Tools to manipulate and format numbers.

- **Webhook Response**: Handle responses from incoming webhooks.

- **Plugin Actions**: Interact with specific WordPress plugins.

- **HARO Email Parser**: Parse HARO (Help a Reporter Out) emails.

- **Schedule**: Trigger workflows based on time-based schedules.

- **FlowMattic Tools**: Additional tools provided by FlowMattic for workflow customization.

- **Webpage Parser**: Extract data from web pages.

- **CSV Parser**: Handle CSV files and parse them for workflows.

- **Iterator Storage**: Manage iteration in workflows with stored data.

- **WordPress**: Interact with WordPress posts, pages, users, etc.

- **Email Parser**: Extract and process data from incoming emails.

- **FlowMattic Chatbot**: Enable chatbot-related workflows.

- **Date/Time Formatter**: Format and manipulate date/time values.

- **RSS Feed**: Integrate and parse RSS feed data.

- **PHP Array**: Handle and manipulate PHP arrays.

- **PHP Functions**: Execute custom PHP functions within workflows.

- **Webhook Outgoing**: Manage outgoing webhook requests.

- **XML Parser**: Parse XML files and use them in workflows.

- **API**: Enable direct API access and interaction.

- **Counter**: Use counters in workflows for counting and triggering actions based on numbers.

- **Maths**: Perform mathematical operations.

- **Iterator**: Handle repeating actions in workflows.

- **Filter**: Apply conditional logic to workflows.

- **Tables:** Manage FlowMattic Tables

* * *

#### Conclusion

The FlowMattic Settings page allows you to customize global options, streamline workflow execution, and enhance integration management. With the new additions in v5.0, users can now manage databases, tailor workflow builder preferences, and simplify email configuration for better efficiency and performance. Customize these settings to match your specific automation needs!

---

# Understanding Sub-Workflows in FlowMattic

Source: https://support.flowmattic.com/kb/article/109/understanding-sub-workflows-in-flowmattic

Are you tired of rebuilding the same workflow steps over and over? Meet Sub-Workflows—your secret weapon for creating smarter, more maintainable automations in FlowMattic.

## What Are Sub-Workflows?

Think of Sub-Workflows as reusable building blocks for your automations. They're mini-workflows that run inside other workflows, letting you build common tasks once and use them everywhere.

Instead of copying and pasting the same 5 steps across 10 different workflows, you create one Sub-Workflow and call it whenever you need it. Change it once, update it everywhere. Simple as that.

### Real-World Analogy

Imagine you're cooking. Instead of writing out "dice onions, mince garlic, sauté in olive oil" in every single recipe, you could just write "prepare sofrito" and reference the detailed steps elsewhere. That's exactly what Sub-Workflows do for your automations.

## Why Should You Care?

### 1. **Save Massive Amounts of Time**

Build your workflow logic once. Use it in 5, 10, or 50 different workflows. Need to add a new step? Update it in one place instead of hunting through dozens of workflows.

**Real example:** You send order confirmations from your website, mobile app, and in-person sales system. Instead of building the same email formatting and sending logic three times, build it once as a Sub-Workflow. Now all three systems use the same logic.

### 2. **Never Duplicate Work Again**

We've all been there—you build a complex workflow, then realize you need the exact same logic somewhere else. With Sub-Workflows, you just call the existing one. No copying, no pasting, no maintaining multiple versions.

### 3. **Update Once, Fix Everywhere**

Your boss wants to change the email template? Your payment processor updated their API? Fix it in the Sub-Workflow once, and every workflow using it gets the update automatically. No more tracking down every place you used that logic.

### 4. **Keep Your Workflows Clean and Organized**

Sub-Workflows help you break complex processes into logical chunks. Instead of a 30-step monster workflow, you have a clean 8-step workflow that calls well-named Sub-Workflows. Your future self will thank you.

## When to Use Sub-Workflows

Sub-Workflows shine when you have repeatable tasks. Here are the most common scenarios:

### Data Transformation and Formatting
- Standardizing phone numbers from different sources ("+1-555-0123" vs "5550123" vs "(555) 0123")
- Converting dates to consistent formats
- Cleaning up customer names and addresses
- Parsing email addresses from text that might contain extra characters

### Shared Notifications
- Sending branded email templates with your company styling
- Posting formatted Slack messages with consistent structure
- Creating support tickets with standardized fields

### Customer Interactions
- Sending welcome email sequences
- Creating follow-up tasks after specific events
- Updating CRM records with consistent data

### Data Lookups and Enrichment
- Searching multiple databases for customer information
- Validating emails or phone numbers
- Enriching contact data from various sources
- Looking up product information across systems

### Security and Access Control
- Retrieving data from secure systems without giving everyone direct access
- Creating data gateways between departments
- Returning only non-sensitive information from databases

## How Sub-Workflows Actually Work

Sub-Workflows use a simple input-process-output model:

### The Three Components

**1. Start Sub-Workflow (Trigger)**  
This is where your Sub-Workflow begins. It defines what data (parameters) the Sub-Workflow will receive from parent workflows.

**2. Action Steps**  
Just like regular workflows, add as many action steps as you need. These process the incoming data.

**3. Return Response (Action)**  
The final step that sends processed data back to the parent workflow. Every Sub-Workflow must have this.

### The Process Flow

```
Parent Workflow starts
    ↓
Parent Workflow runs some steps
    ↓
Calls Sub-Workflow (sends data like email, name, etc.)
    ↓
Sub-Workflow receives data
    ↓
Sub-Workflow processes it (formats, validates, enriches)
    ↓
Sub-Workflow returns results
    ↓
Parent Workflow continues with the results
    ↓
Parent Workflow completes
```

### A Quick Example

**Sub-Workflow: "Format Customer Data"**
- Receives: raw email, raw phone, raw name
- Processes: Converts email to lowercase, removes phone number formatting, fixes name capitalization
- Returns: formatted email, formatted phone, formatted name

**Parent Workflow 1: "Fluent Forms → CRM"**
- Trigger: New form submission
- Calls "Format Customer Data" with form data
- Creates CRM contact with formatted data

**Parent Workflow 2: "FluentCart → CRM"**
- Trigger: New order
- Calls "Format Customer Data" with customer data
- Updates CRM contact with formatted data

Both workflows get consistently formatted data without duplicating the formatting logic.

## The Key Benefits You'll Experience

### Consistency Across Your Business

When you use Sub-Workflows, you ensure the same business logic applies everywhere. No more "this workflow formats phone numbers differently than that one" problems.

### Easier Troubleshooting

Bug in your email formatting? Fix it in the Sub-Workflow and test it once. No need to hunt through 15 workflows to find all the places that logic exists.

### Team Collaboration Made Simple

Sub-Workflows make it easy to divide work. One team member builds the customer data formatter, another builds workflows that use it. Everyone stays in sync because they're using the same component.

### Future-Proof Your Automations

Business requirements change. When they do, Sub-Workflows let you adapt quickly. Update the logic in one place, and all your workflows instantly use the new version.

## What You Need to Know Before Starting

### Sub-Workflows vs Regular Workflows

**Regular Workflows** start with a trigger that responds to external events (new email, form submission, schedule, etc.)

**Sub-Workflows** start with the "Start Sub-Workflow" trigger, which only fires when called by another workflow. They can't run on their own.

### Performance Considerations

Sub-Workflows add a small amount of processing time since data needs to be passed back and forth. For most use cases, this is negligible. Keep Sub-Workflows efficient by:

- Only including necessary steps
- Avoiding unnecessary delays
- Not nesting Sub-Workflows too deeply

## Common Patterns You'll Use

### Pattern 1: The Data Formatter
Receive messy data, clean it up, return it formatted. Use this for emails, phone numbers, addresses, dates.

### Pattern 2: The Multi-Source Lookup
Search several systems for information, compile what you find, return the results. Perfect for finding customer data spread across multiple tools.

### Pattern 3: The Notification Hub
Receive a notification request, determine how to send it (email, Slack, SMS), format it appropriately, send it, return confirmation.

### Pattern 4: The Validator
Receive data, check if it's valid (format, requirements, business rules), return validation status and any errors.

## Planning Your First Sub-Workflow

Before you build, ask yourself:

1. **What do I need this Sub-Workflow to do?** Be specific about the task.

2. **What data do I need to send it?** List all the parameters required.

3. **What should it return?** Think about what data the parent workflow needs back.

4. **Where will I use it?** Knowing all the use cases helps you design it right.

5. **How might this change?** Design for flexibility if requirements might evolve.

## Common Questions

**Q: How many Sub-Workflows can I create?**  
A: There's no specific limit on Sub-Workflows themselves

**Q: Can Sub-Workflows call other Sub-Workflows?**  
A: Yes! But avoid circular references (A calls B, B calls A) which create infinite loops.

**Q: What happens if I change a Sub-Workflow?**  
A: All parent workflows using it will immediately use the updated version. Test changes carefully!

**Q: Can I see which workflows use a specific Sub-Workflow?**  
A: Currently, you'll need to search through your workflows or check execution logs. Consider documenting this in the Sub-Workflow description.

## Next Steps

Ready to build your first Sub-Workflow? Check out our step-by-step guide: **[Create Reusable Workflow Steps with Sub-Workflows](#)**

Want to see real examples in action? Read: **[FlowMattic Sub-Workflows and How to Use Them](#)**

---

**Need help?** Visit [FlowMattic Support](https://support.flowmattic.com) or contact our support team.

---

**Related Articles:**
- Create Reusable Workflow Steps with Sub-Workflows
- FlowMattic Sub-Workflows and How to Use Them

---

# Understanding the Status Page

Source: https://support.flowmattic.com/kb/article/37/understanding-the-status-page

### FlowMattic Status Page

The **FlowMattic Status Page** provides an overview of the critical server and site configuration settings that FlowMattic requires to function optimally. This page highlights the current status of these configurations, allowing you to ensure that your WordPress site is set up correctly to avoid issues with your workflows. If any of the checks are marked in red, it indicates a potential problem that should be addressed, typically with the help of your hosting provider. Below is a detailed explanation of each status check shown in the image.

#### 1\. Permalink Structure

- **Requirement**: Anything but not default, preferred: `%postname%`

- **Description**: FlowMattic requires a proper permalink structure for API calls and workflows to function seamlessly. The default permalink structure (e.g., `?p=123`) is not supported. For best results, it is recommended to set the permalink structure to `%postname%`. You can configure this by going to **Settings &gt; Permalinks** in your WordPress dashboard and selecting an appropriate option like "Post name."

#### 2\. Secure Site URL (HTTPS)

- **Requirement**: The site must be using HTTPS

- **Description**: To ensure the security and proper functioning of workflows, FlowMattic requires your site to be served over HTTPS. If your site is not secured with an SSL certificate, you may encounter issues, especially with third-party integrations and API requests. Ensure that your site URL begins with `https://`. You can verify and configure this by checking the **General** settings in WordPress or contacting your hosting provider for an SSL setup.

#### 3\. PHP Version

- **Requirement**: Minimum PHP version required: 7.2

- **Description**: FlowMattic relies on a supported PHP version to execute its backend operations. PHP 7.2 or higher is required for compatibility. Running an outdated version of PHP could lead to errors and security vulnerabilities. You can check and update the PHP version from your hosting control panel or by contacting your hosting provider.

#### 4\. PHP Memory Limit

- **Requirement**: Minimum memory limit: 256MB

- **Description**: The PHP memory limit determines how much memory is allocated to run processes on your server. A minimum of 256MB is required for FlowMattic to handle workflows without memory-related issues. If the memory limit is set too low, it could cause workflows to fail or time out. To adjust the PHP memory limit, you can modify the `wp-config.php` file or request your hosting provider to increase it.

#### 5\. PHP Timeout Limit

- **Requirement**: 0 or 300 preferred

- **Description**: The PHP timeout limit defines how long a server will wait for a process to complete before it’s considered failed. A timeout limit of `0` (which means no limit) or `300` seconds (5 minutes) is preferred to ensure that even complex workflows are executed without interruption. Shorter timeout values may cause long-running processes to fail. You can adjust the timeout limit in the server's PHP settings or by contacting your hosting provider for assistance.

### Final Note

If any of these configurations are marked in red on your FlowMattic status page, it is essential to address them promptly. These settings ensure that FlowMattic can run efficiently and that your workflows function smoothly. For assistance in changing any of these configurations, you may need to contact your hosting provider or consult your server's documentation.

This status page acts as an essential diagnostic tool to keep your system optimized and workflows running seamlessly in FlowMattic.

---

# Unit Converter by FlowMattic - Complete Guide

Source: https://support.flowmattic.com/kb/article/105/unit-converter-by-flowmattic---complete-guide

## Overview

The Unit Converter integration by FlowMattic is a powerful built-in tool that allows you to convert values between different units of measurement directly within your workflows. This integration supports 13 different conversion categories, making it versatile for various automation needs.

## Key Features

- **No External API Required**: Built directly into FlowMattic, requiring no external service connections
- **13 Conversion Categories**: Comprehensive coverage of common unit conversions
- **Multiple Unit Variations**: Supports various unit name formats (e.g., "kilometer", "km", "kilometers")
- **High Precision**: Accurate conversion calculations for all supported units
- **Dynamic Field Support**: Compatible with dynamic values from previous workflow steps

## Available Conversion Categories

### 1. Length Conversion
Convert between various distance and length measurements.

**Supported Units:**
- Meter (m, meter, meters)
- Kilometer (km, kilometer, kilometers)
- Centimeter (cm, centimeter, centimeters)
- Millimeter (mm, millimeter, millimeters)
- Mile (mi, mile, miles)
- Yard (yd, yard, yards)
- Foot (ft, foot, feet)
- Inch (in, inch, inches)
- Nautical Mile (nm, nautical_mile)

### 2. Weight Conversion
Convert between different weight and mass units.

**Supported Units:**
- Kilogram (kg, kilogram, kilograms)
- Gram (g, gram, grams)
- Milligram (mg, milligram, milligrams)
- Pound (lb, lbs, pound, pounds)
- Ounce (oz, ounce, ounces)
- Ton (t, ton, tons, metric_ton)
- Stone (st, stone, stones)

### 3. Temperature Conversion
Convert between temperature scales.

**Supported Units:**
- Celsius (c, celsius)
- Fahrenheit (f, fahrenheit)
- Kelvin (k, kelvin)

### 4. Volume Conversion
Convert between liquid and volume measurements.

**Supported Units:**
- Liter (l, liter, liters)
- Milliliter (ml, milliliter, milliliters)
- Gallon (gal, gallon, gallons)
- Quart (qt, quart, quarts)
- Pint (pt, pint, pints)
- Cup (cup, cups)
- Fluid Ounce (fl_oz, fluid_ounce, fluid_ounces)
- Tablespoon (tbsp, tablespoon, tablespoons)
- Teaspoon (tsp, teaspoon, teaspoons)
- Cubic Meter (m3, cubic_meter, cubic_meters)
- Cubic Centimeter (cm3, cc, cubic_cm)

### 5. Area Conversion
Convert between area measurements.

**Supported Units:**
- Square Meter (sqm, m2, square_meter, square_meters)
- Square Kilometer (km2, square_kilometer, square_kilometers)
- Square Centimeter (cm2, square_cm)
- Square Millimeter (mm2, square_mm)
- Square Mile (mi2, square_mile, square_miles)
- Square Yard (yd2, square_yard, square_yards)
- Square Foot (sqft, ft2, square_foot, square_feet)
- Square Inch (in2, square_inch, square_inches)
- Acre (acre, acres)
- Hectare (ha, hectare, hectares)

### 6. Speed Conversion
Convert between velocity and speed units.

**Supported Units:**
- Meter per Second (m/s, mps, meter_per_second, meters_per_second)
- Kilometer per Hour (km/h, kmh, kph, kilometer_per_hour, kilometers_per_hour)
- Mile per Hour (mph, mi/h, mile_per_hour, miles_per_hour)
- Foot per Second (ft/s, fps, foot_per_second, feet_per_second)
- Knot (kn, knot, knots)

### 7. Pressure Conversion
Convert between pressure measurements.

**Supported Units:**
- Pascal (pa, pascal, pascals)
- Kilopascal (kpa, kilopascal, kilopascals)
- Bar (bar, bars)
- Millibar (mbar, millibar, millibars)
- Atmosphere (atm, atmosphere, atmospheres)
- PSI (psi)
- Torr (torr)
- Millimeters of Mercury (mmhg)

### 8. Energy Conversion
Convert between energy units.

**Supported Units:**
- Joule (j, joule, joules)
- Kilojoule (kj, kilojoule, kilojoules)
- Calorie (cal, calorie, calories)
- Kilocalorie (kcal, kilocalorie, kilocalories)
- Watt Hour (wh, watt_hour, watt_hours)
- Kilowatt Hour (kwh, kilowatt_hour, kilowatt_hours)
- BTU (btu, btus)
- Electron Volt (ev, electron_volt)

### 9. Power Conversion
Convert between power measurements.

**Supported Units:**
- Watt (w, watt, watts)
- Kilowatt (kw, kilowatt, kilowatts)
- Megawatt (mw, megawatt, megawatts)
- Horsepower (hp, horsepower)
- Metric Horsepower (ps, metric_horsepower)
- BTU per Hour (btu/h, btu_per_hour)
- Foot-Pound per Second (ft_lb/s, foot_pound_per_second)

### 10. Data Size Conversion
Convert between digital storage units.

**Supported Units:**
- Bit (b, bit, bits)
- Byte (byte, bytes)
- Kilobyte (KB, kb, kilobyte, kilobytes)
- Megabyte (MB, mb, megabyte, megabytes)
- Gigabyte (GB, gb, gigabyte, gigabytes)
- Terabyte (TB, tb, terabyte, terabytes)
- Petabyte (PB, pb, petabyte, petabytes)

### 11. Angle Conversion
Convert between angular measurements.

**Supported Units:**
- Degree (deg, degree, degrees)
- Radian (rad, radian, radians)
- Gradian (grad, gon, gradian, gradians)
- Arc Minute (arcmin, arc_minute, arc_minutes)
- Arc Second (arcsec, arc_second, arc_seconds)
- Turn/Revolution (turn, turns, rev, revolution, revolutions)

### 12. Frequency Conversion
Convert between frequency units.

**Supported Units:**
- Hertz (hz, hertz)
- Kilohertz (khz, kilohertz)
- Megahertz (mhz, megahertz)
- Gigahertz (ghz, gigahertz)
- RPM (rpm, revolutions_per_minute)
- BPM (bpm, beats_per_minute)

### 13. Fuel Economy Conversion
Convert between fuel efficiency measurements.

**Supported Units:**
- Miles per Gallon (mpg, miles_per_gallon, mile_per_gallon)
- Kilometers per Liter (km/l, kilometers_per_liter, kilometer_per_liter)
- Liters per 100 Kilometers (l/100km, liters_per_100km, liter_per_100km)

## How to Use the Unit Converter

### Step 1: Add the Unit Converter Action

1. In your workflow editor, click on the **"+"** button to add a new action step
2. Search for **"Unit Converter"** in the applications list
3. Select **"Unit Converter"** from the list

 
 ![Image_2025-09-09_at_22418_AM.jpeg](/storage/kb-images/608b2a3ad8-inline.png)


### Step 2: Choose Conversion Type

Select the appropriate conversion type from the available actions:
- Length Conversion
- Weight Conversion
- Temperature Conversion
- Volume Conversion
- Area Conversion
- Speed Conversion
- Pressure Conversion
- Energy Conversion
- Power Conversion
- Data Size Conversion
- Angle Conversion
- Frequency Conversion
- Fuel Economy Conversion

 
 ![Image_2025-09-09_at_23124_AM.jpeg](/storage/kb-images/b717da8bc4-inline.png)


### Step 3: Configure Conversion Parameters

Each conversion requires three parameters:

1. **Value** (Required)
   - The numeric value you want to convert
   - Can be a static number or dynamic value from previous steps
   - Example: `100`, `{temperature_value}`, `{step_1.data.measurement}`

2. **From Unit** (Required)
   - The unit of the input value
   - Enter the unit abbreviation or full name
   - Example: `km`, `kilometer`, `fahrenheit`, `f`

3. **To Unit** (Required)
   - The desired output unit
   - Enter the unit abbreviation or full name
   - Example: `miles`, `mi`, `celsius`, `c`

 
 ![Image_2025-09-09_at_23826_AM.jpeg](/storage/kb-images/8b7cba6fea-inline.png)


### Step 4: Test the Conversion

1. Click the **"Test Action"** button
2. Enter sample values to verify the conversion works correctly
3. Review the output to ensure accuracy

## Response Format

The Unit Converter returns a JSON response with the following structure:

```json
{
  "status": "success",
  "converted_value": 62.137,
  "from_unit": "km",
  "to_unit": "miles",
  "original_value": 100
}
```

**Response Fields:**
- `status`: Indicates success or error
- `converted_value`: The converted result
- `from_unit`: The source unit used
- `to_unit`: The target unit used
- `original_value`: The original input value

## Use Cases and Examples

### Example 1: E-commerce Product Dimensions
Convert product dimensions from inches to centimeters for international customers:
- **Value**: `{product_length}`
- **From Unit**: `inches`
- **To Unit**: `cm`

### Example 2: Weather Data Processing
Convert temperature readings from Fahrenheit to Celsius:
- **Value**: `{weather_api.temperature}`
- **From Unit**: `fahrenheit`
- **To Unit**: `celsius`

### Example 3: Shipping Weight Calculations
Convert package weight from pounds to kilograms:
- **Value**: `{order.total_weight}`
- **From Unit**: `lbs`
- **To Unit**: `kg`

### Example 4: Real Estate Area Conversion
Convert property size from square feet to square meters:
- **Value**: `{property.area}`
- **From Unit**: `sqft`
- **To Unit**: `m2`

### Example 5: Data Storage Monitoring
Convert storage usage from bytes to gigabytes:
- **Value**: `{storage.used_bytes}`
- **From Unit**: `bytes`
- **To Unit**: `GB`

## Integration with Other Applications

The Unit Converter works seamlessly with other FlowMattic integrations:

1. **API Integrations**: Process data from APIs that use different unit systems
2. **Database Operations**: Convert units before storing or after retrieving data
3. **Email Notifications**: Include converted values in automated emails
4. **Webhook Processing**: Convert incoming webhook data to preferred units
5. **CSV/Excel Processing**: Standardize units when processing spreadsheet data

## Best Practices

### 1. Input Validation
- Always ensure the input value is numeric
- Use conditional logic to handle non-numeric inputs
- Consider adding error handling for invalid unit names

### 2. Unit Name Consistency
- Use consistent unit naming throughout your workflow
- Document which unit format you're using (abbreviation vs. full name)
- Consider standardizing on abbreviations for cleaner workflows

### 3. Precision Handling
- Be aware that some conversions may result in floating-point numbers
- Use rounding or formatting functions if needed for display
- Consider the required precision for your use case

### 4. Dynamic Values
- Use the plus icon to insert dynamic values from previous steps
- Ensure dynamic values are properly formatted before conversion
- Test with various input values to verify workflow reliability

## Troubleshooting

### Common Issues and Solutions

**Issue 1: "Invalid unit specified" error**
- **Solution**: Check that the unit name is spelled correctly and matches supported units
- Refer to the supported units list for each conversion type
- Unit names are case-insensitive but must match exactly

**Issue 2: "Value field is required and must be numeric" error**
- **Solution**: Ensure the value field contains only numbers
- Remove any non-numeric characters (currency symbols, commas, etc.)
- Use text manipulation steps if needed to clean the input

**Issue 3: Unexpected conversion results**
- **Solution**: Verify you're using the correct "from" and "to" units
- Check that units are not reversed
- Test with known values to verify accuracy

**Issue 4: Dynamic values not working**
- **Solution**: Ensure the dynamic field reference is correct
- Check that the previous step is outputting numeric values
- Use the test feature to debug the data flow

## Advanced Tips

### 1. Chaining Conversions
You can chain multiple unit conversions for complex calculations:
1. Convert meters to feet
2. Calculate area in square feet
3. Convert square feet to acres

### 2. Conditional Conversions
Use conditional logic to apply different conversions based on criteria:
- If country is "US", convert to imperial units
- If country is "EU", keep metric units

### 3. Batch Processing
Process multiple values efficiently:
- Use iterators to convert arrays of values
- Store conversion results in variables for reuse
- Aggregate converted values for reporting

### 4. Custom Formatting
Format converted values for display:
- Round to specific decimal places
- Add unit labels to the output
- Format for currency or percentage display

## Performance Considerations

- The Unit Converter operates locally within FlowMattic
- No external API calls means faster processing
- Suitable for high-volume conversions
- No rate limits or usage restrictions

## Summary

The Unit Converter by FlowMattic is a versatile and reliable tool for handling unit conversions within your automation workflows. With support for 13 conversion categories and hundreds of unit combinations, it can handle virtually any conversion requirement. The integration's built-in nature ensures fast, reliable conversions without dependency on external services.

Whether you're processing e-commerce data, scientific measurements, or everyday conversions, the Unit Converter provides the flexibility and accuracy needed for professional automation workflows.

## Need Help?

If you encounter any issues or need assistance with the Unit Converter integration:
1. Check the troubleshooting section above
2. Review your workflow configuration
3. Contact FlowMattic support with specific error messages
4. Visit the FlowMattic documentation for updates

Remember to test your conversions thoroughly before deploying workflows to production environments.

---

# Upload Base64 Image to the WordPress Media Library

Source: https://support.flowmattic.com/kb/article/164/upload-base64-image-to-the-wordpress-media-library

The **Upload Base64 Image** action is part of FlowMattic's built-in **WordPress** integration. It takes an image that is encoded as a base64 text string, decodes it back into a real image file, and saves it into your WordPress **Media Library** — optionally converting it to a different format and giving it a custom filename, folder, and metadata along the way.

## What this action does

Many tools and APIs don't return an image as a downloadable file. Instead, they return the image as a long block of text called **base64** — a way of representing binary data (like a picture) using only plain characters. AI image generators, screenshot APIs, PDF/chart services, and "convert this to an image" endpoints commonly hand back base64.

That text on its own is useless inside WordPress — you can't attach it to a post or show it on your site. The **Upload Base64 Image** action bridges that gap: it converts the base64 text into a genuine image file and registers it in your Media Library, exactly as if you had uploaded it through **Media → Add New**. You get back a real attachment ID and a public URL you can use in the rest of your workflow.

![The WordPress action dropdown in a workflow step with "Upload Base64 Image" highlighted](https://assets.infidesk.support/kb/inline/2026/07/d5hD14RWqSWXzGIpFJpydg3EMZ6hzWCLIEw6nl7o.png)

## When you'd use it

You'd typically place this action right after a step that produces a base64 image string. Common examples:

- An **AI image generation** step (or API call) that returns the generated image as base64.
- An **API** action that downloads or builds an image and returns it base64-encoded.
- Any earlier step whose output is a `data:image/...;base64,...` value that you now want stored permanently in WordPress.

Once uploaded, you can pass the resulting attachment ID or URL into a later step — for example, setting it as a post's featured image, or sending the URL somewhere else.

## How it works end-to-end

When the action runs, FlowMattic does the following:

1. **Reads the base64 string** you provided. If the string starts with a data URI prefix (like `data:image/png;base64,`), that prefix is automatically detected and stripped, so you can paste either format.
2. **Decodes** the base64 text back into the original image data. If the string can't be decoded, the action stops and returns an error.
3. **Detects the image type.** If the data URI told it the type, it uses that; otherwise it inspects the decoded data to figure out the format.
4. **Converts the format if you asked it to** (see **Convert to Format** below). If you leave conversion off, the original image data is kept as-is.
5. **Builds a filename** from your custom name, or auto-generates one if you left it blank.
6. **Saves the file into the Media Library** using WordPress's standard upload process, optionally into a custom folder.
7. **Applies metadata** (alt text, caption, description) if you provided any.
8. **Returns** the new attachment's ID and URL.

![The expanded Upload Base64 Image action showing all of its fields](https://assets.infidesk.support/kb/inline/2026/07/9FvRjs9lySpXxoVZoXiHyBXELKqp4dALPfeMg5mz.png)

## The fields

### Base64 Image Data (Required)

This is the core input — paste or map the base64-encoded image string here. It accepts both formats:

- **Raw base64**, just the encoded characters on their own.
- **Data URI format**, which includes a prefix such as `data:image/png;base64,` before the encoded characters. The prefix is removed automatically.

In most real workflows you won't type this by hand — you'll insert the output field from an earlier AI or API step. If this field is empty, the action returns the error *"Base64 data is required."*, and if the value can't be decoded it returns *"Invalid base64 data. Could not decode."*

### Convert to Format

An optional dropdown that lets you change the image's format before it's saved. The choices are:

- **Keep Original Format** (the default) — no conversion; the image is stored in whatever format the base64 data already is.
- **WebP** — modern, highly compressed format good for web performance.
- **JPG** — widely compatible, good for photos.
- **PNG** — supports transparency, good for graphics and logos.
- **AVIF** — newest, very efficient format. As the field's own note states, *AVIF support requires PHP 8.1+ with GD AVIF enabled* on your server.
- **GIF** — for simple graphics or animations.

**How the conversion works:** when you pick a format, the decoded image is loaded by your server's GD image library and re-saved in the chosen format. Transparency is preserved where the output format supports it (PNG, WebP, AVIF). WebP, AVIF, and JPG are saved at a quality level of 85, and PNG at compression level 6 — a balance between file size and image quality. GIF is saved without a quality setting.

If your server can't perform the requested conversion (for example, AVIF on an older PHP version, or an invalid source image), the action returns an error like *"Failed to convert image to AVIF. The format may not be supported by your server."* rather than uploading a broken file. If you're unsure whether your server supports a format, leaving this on **Keep Original Format** is the safe choice.

### Custom Filename

An optional name for the saved file, **without the extension** (the placeholder shows `my-custom-image`). The correct extension for the final format is added for you automatically. If you leave this blank, FlowMattic auto-generates a unique name in the pattern `image-<timestamp>.<extension>`.

### Folder Path

An optional subfolder inside your WordPress uploads directory where the file should be saved (the placeholder shows `custom-folder/sub-folder`). You can use nested paths with slashes. If the folder doesn't exist yet, it's created automatically (along with a small protective `index.php` file). Leave this empty to use WordPress's default upload location (the usual year/month folders).

### Alternative Text

Optional **alt text** for the image. If provided, it's stored as the attachment's alternative text — the same field you'd normally fill in when editing an image in the Media Library. Good alt text helps accessibility and SEO.

### Caption

Optional caption for the image, saved to the attachment's caption field.

### Description

Optional longer description for the image, saved to the attachment's description field.

![The uploaded image's entry in the WordPress Media Library showing its alt text, caption, and description](https://assets.infidesk.support/kb/inline/2026/07/lbwgisDXxXSV0EUmVbgmJvP9ZZKPUPLiQwVmv1Cw.png)


There is no separate "Title" field on this action — naming is handled by the **Custom Filename** field, and the descriptive metadata is set through **Alternative Text**, **Caption**, and **Description**.

## What the action outputs

On success, the action returns these values, which you can map into later steps:

- **status** — `success` when the upload worked.
- **media_id** — the new attachment's ID in WordPress. This is the most useful output; you can feed it into other actions, such as setting a post's featured image.
- **media_url** — the public URL of the uploaded image.
- **alt_text**, **caption**, **description** — echoed back only if you supplied them.

If something goes wrong, it instead returns a `status` of `error` with a `message` (for missing or undecodable data) or an `error` describing what failed (for upload or conversion problems).

![The action's test/output panel showing media_id and media_url returned after a successful run](https://assets.infidesk.support/kb/inline/2026/07/m1RV0DyjAjqv2PdC5rDnqWuDwkC74b0tfeavc8Ar.png)

## Tips for reliable results

- **Map, don't type.** Use the data-picker to insert the base64 output from your previous step rather than pasting a huge string manually.
- **Stick with Keep Original Format unless you have a reason to convert.** Conversion depends on your server's GD library supporting the target format — especially for AVIF.
- **Use Custom Filename for clean, predictable URLs** when the image will be used publicly; otherwise the auto-generated timestamped name is perfectly fine.

---

# Use FlowMattic API Module for Connecting Applications via API

Source: https://support.flowmattic.com/kb/article/57/use-flowmattic-api-module-for-connecting-applications-via-api

### Overview
The FlowMattic API module allows seamless integration with any application that provides an API and relevant documentation. By leveraging this module, you can perform various API requests such as GET, POST, PUT, DELETE, and PATCH. This guide provides a detailed walkthrough for connecting to an API, using Google Maps API as an example.

### Steps to Connect an Application via FlowMattic API Module

Let's try using the Google Maps API in the following steps as an example.

1. **Create a Workflow**:
   - Start by creating a new workflow in FlowMattic.
   - Add an action step and select the API module.

2. **Configure API Module**:
   - Choose the action event, e.g., `GET`, `POST`, or other supported methods.
   - Enter the API Endpoint URL provided by the application you are connecting to. For example, to retrieve the distance between two locations using Google Maps API, use the URL: `https://maps.googleapis.com/maps/api/distancematrix/json?origins=Toronto&destinations=Montreal`.

3. **Set Authentication**:
   - Select the appropriate authentication method:
     - **No Authentication**: For APIs that don’t require authentication.
     - **Basic Auth**: Use a username and password for authentication.
     - **Bearer Token**: Provide a token for secure access.
     - **FlowMattic Connect**: Use pre-configured FlowMattic Connect for OAuth 2.0 and different other authentication types.

4. **Enable Headers and Parameters**:
   - Enable the **Headers** option if the API requires specific headers, and add them accordingly.
   - Enable the **Parameters** option and input the required key-value pairs. For example:
     ```
     Key: key
     Value: Your Google Maps API key
     ```

5. **Set Response Format**:
   - Choose the response format as `Simple` or any other format as required by the API.
 
 ![Google Maps API](/storage/kb-images/59d90115d3-inline.png)


6. **Test the API Connection**:
   - Navigate to the `Test` tab and click the `Test Action` button.
   - Review the response in the `Data-out` tab to ensure the connection is successful.

### Supported HTTP Methods
The FlowMattic API module supports the following methods:
- **GET**: Retrieve data from the server.
- **POST**: Submit data to the server.
- **PUT**: Update data on the server.
- **DELETE**: Remove data from the server.
- **PATCH**: Partially update data on the server.

### Understanding the API requirements for your app
- **API Endpoint**: The URL where the API is hosted.
- **Authentication**: The method required to access the API (e.g., API key, OAuth 2.0, etc.).
- **Headers**: Additional information required by the API (e.g., content-type).
- **Parameters**: Key-value pairs to be sent with the API request.
- **Response Format**: The format in which the API will return the data (e.g., JSON, XML).
- **Request Type**: The type of request to be made (e.g., GET, POST).

All of the above details can be found on the API documentation of the application you are connecting to. Some apps provide the API request examples in their documentation to help you get started. Let's try to explore a sample to help you understand how you can retrieve the required details from such documentation.

Let's assume the following is an example request shared on your apps documentation page, which uses the CURL command to send some sample data to your app's API endpoint:
```
curl -X POST "https://api.example.com/data"
-H "Content-Type: application/json"
-H "Accept: application/json"
-H "Authorization: Bearer YOUR_ACCESS_TOKEN"
-d '{"key_1":"value1","key_2":"value2"}'
```

From the above example, you can extract the following details:
- **API Endpoint**: `https://api.example.com/data`
- **Authentication**: Bearer Token
- **Headers**:
  - Content-Type: application/json
  - Accept: application/json
- **Parameters**:
  - key_1: value1
  - key_2: value2
- **Request Type**: POST

 
 ![API Example](/storage/kb-images/9475b8c202-inline.png)


You can use these details to configure the FlowMattic API module to connect to your app's API as shown in the screenshots above.

### Tips for Using FlowMattic API Module
- Always refer to the API documentation of the application you are connecting to for accurate endpoint URLs, headers, and parameters.
- Use test actions in FlowMattic to validate your API configurations before proceeding further in your workflow.
- For OAuth 2.0 and different authentication types, use pre-configure FlowMattic Connect to simplify the process.

By following these steps and tips, you can efficiently connect and interact with APIs using the FlowMattic API module.

For any further assistance or queries, please feel free to reach out to our support team.

---

# Use FlowMattic Tables in your workflows

Source: https://support.flowmattic.com/kb/article/209/use-flowmattic-tables-in-workflows

FlowMattic Tables is built for automation: every table is available as an app inside the workflow builder, with actions to write and read rows and triggers that fire when data changes.

## Available actions and triggers

**Actions** — Insert Row, Update Row, Insert or Update Row (upsert by a match field), Update Cell, Get Row, Find Row, Find Rows, Get Row Count, Delete Row, Raw SQL Query, and Continue on Approve or Reject (pause a workflow for an email approval).

**Triggers** — New Row, Updated Row, Deleted Row, Updated Cell, and Button Clicked (fires when someone clicks a Button column in the grid).

## Add a Tables step

In the workflow builder, add a step and search for **FlowMattic Tables**. On the **Setup** tab pick your action (for example *Insert Row*), then on **Configure** choose the table.

## Typed field cards — no JSON required

Row values are configured as **cards**. Each card has a searchable field picker (type to filter — every field shows its name and type), and the inputs below adapt to the column's type:

![Insert Row — typed field cards for Person, Tags, and Dropdown columns](https://assets.infidesk.support/kb/inline/2026/07/oQnmy2DmzdE1kIJMbev1PLe9S96MADHv1ZP1PTvK.jpg)

- **Person** — First name, Last name, and Email inputs. You can also map a plain value like `Jane Doe <jane@example.com>` — it's converted automatically when the workflow runs.
- **Tags** — pick from the column's option chips, or map a dynamic value below them. Comma-separated names (`Urgent, Design`), a JSON list, or a token all work.
- **Dropdown / Status** — choose an option, or pick *Custom value / token…* to map dynamic data.
- **Files** — one row per file URL; a mapped value may also be a single URL or comma-separated URLs.
- **Currency** — amounts in whole minor units (`1999` = 19.99), with the column's currency code shown beside the input.
- **Checkbox** — Checked / Unchecked, or a custom token that resolves to true/false, yes/no, or 1/0.

Every input has the **+** button to insert captured data from earlier steps, and the `</>` toggle on each card exposes the raw value for power users.

> **Automatic attribution:** *Created by* and *Modified by* columns are excluded from the field picker — FlowMattic stamps them itself, so workflow writes carry a trustworthy audit trail.

## Plain values convert at run time

You don't need to know how a column stores its data. When the workflow executes, FlowMattic normalizes mapped values to each column's storage format — comma-separated tags become a list, a plain name-and-email becomes a Person, file URLs become a file list, and a list mapped into a single-choice Dropdown collapses to its first value.

## React to data changes

Use the **New Row / Updated Row / Updated Cell / Deleted Row** triggers to start workflows when your tables change — whether the change came from another workflow, the grid, or a CSV import (imports only fire triggers when you enable *Run workflows for each imported row*).

---

# Use tables and totals in a PDF template

Source: https://support.flowmattic.com/kb/article/204/use-tables-and-totals-in-a-pdf-template

Invoices, quotes, and reports usually contain a list of rows and a set of computed totals. The PDF Template Builder handles both with two elements: **Table**, which repeats over array data, and **Totals**, which computes values with formulas.

## Prepare your data

Your template's sample data needs an array for the rows and, optionally, an object for the totals. For an invoice:

```json
{
  "line_items": [
    { "description": "Design work", "quantity": 10, "amount": 1200 },
    { "description": "Hosting",      "quantity": 1,  "amount": 150 }
  ],
  "totals": { "tax_rate": 0.2 }
}
```

See *Bind dynamic data in PDF templates with tokens and sample data* for how to set sample data.

## Add a Table element

1. Drag a **Table** element onto the canvas.
2. In its **Data binding**, set **Repeat from** to the array in your data — `line_items`.
3. In the **Columns** section, add one column per value you want to show and map each column's key to a field on the array items: `description`, `quantity`, `amount`.
4. Set each column's label, width, and alignment.

At render time the Table draws one row per item in the array, so a two-item `line_items` array produces two rows, and a ten-item array produces ten. You design the row once; the data decides how many rows appear.

![A Table element selected with its column mapping panel, columns bound to description, qty, rate, and amount](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-pdf-template-builder-pdf-table-columns.png)

## Add a Totals element

1. Drag a **Totals** element onto the canvas, usually below the table.
2. Click **Add line** for each figure you want. Give each a **Label**, and enter the calculation in the row's formula (fx) field.

The Totals element supports these formulas:

- `sum(line_items.amount)` — add a numeric field across every array item.
- `avg`, `min`, `max`, `count` — average, smallest, largest, and number of items.
- `mul(a, b)` — multiply two values, for example `mul(totals.subtotal, totals.tax_rate)` for a tax figure.

A typical invoice footer uses three rows:

- **Subtotal** — `sum(line_items.amount)`
- **Tax** — `mul(totals.subtotal, totals.tax_rate)`
- **Total** — the subtotal plus tax

![A Totals element selected showing Subtotal, Tax, and Total rows with their formulas in the settings panel](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-pdf-template-builder-pdf-totals-element.png)

## Save and test

Click **Save**. Because the Table and Totals read from your sample data while you design, the canvas already shows realistic rows and figures. When the workflow runs, they recompute from the live data your action supplies.

---

# Using FlowMattic Variables to Generate Random Numbers

Source: https://support.flowmattic.com/kb/article/64/using-flowmattic-variables-to-generate-random-numbers

FlowMattic includes a powerful **built-in variable system**, accessible from a dedicated admin page called **"Variables"**. This page not only lists pre-defined system variables like `random_number:<NUMBER>`, but also allows users to **create their own custom variables** for reuse across workflows.

One of the most useful built-in variables is the **random number generator**, which helps you generate a dynamic number between `0` and your defined upper limit — perfect for things like OTPs, invoice IDs, or test data.

---

## 🔧 How It Works

To generate a random number, you use the following syntax:

```
{{random_number:<NUMBER>}}
```

- `random_number:` is the variable type.
- `<NUMBER>` defines the upper limit.
- It generates a random number between `0` and `<NUMBER>` (inclusive of 0, exclusive of <NUMBER>).

### ✅ Example:

```
{{random_number:100}}
```

Will generate a number like `72` (any number between 0 and 100).

---

## 🪜 Step-by-Step: How to Use Random Number Variable

1. **Open your workflow** in FlowMattic.
2. Add or select a step where you want to use a dynamic random number.
3. Inside the input field, click the **`+` icon** to open the **Dynamic Fields popup**.
4. The first section in the popup is **FlowMattic Variables** — search or scroll to find `random_number:<NUMBER>`.
5. Select or modify the number to suit your range, e.g., `random_number:1000` for values between `0` and `1000`.
6. Insert the variable — it will appear as `{{random_number:1000}}`.
7. You can now use this variable directly — for example, in number formatting, API calls, or creating dynamic content.

---

## 📦 Use Case Examples

### 1. 🔐 Generate 4-digit OTP
```text
{{random_number:9999}}
```
- Used to create a random 4-digit One-Time Password.
- Example Output: `4832`

---

### 2. 📦 Create a unique invoice suffix
```text
INV-{{random_number:100000}}
```
- Used to create invoice codes like `INV-49832`.

---

### 3. 🧪 Add a random delay in testing flows
```text
{{random_number:10}}
```
- Used to randomly set wait times between 0 to 10 seconds for testing.

---

### 4. 🎟 Generate a short coupon code number
```text
COUPON-{{random_number:1000}}
```
- Used to create short numeric codes like `COUPON-417`.

---

### 5. 🧾 Generate customer reference number
```text
REF{{random_number:1000000}}
```
- Example Output: `REF492837`

---

## 💡 Tip

You can also use this inside **Format Number**, **Conditions**, **API Calls**, or **Custom Email Templates**, just like shown in the **screenshot shared below** — where it’s used inside a **Format Number** step to apply a comma separator for readability.

![Zight 2025-04-13 at 1.34.40 AM.png](/storage/kb-images/c2fec2f665-inline.png)

---

# Using Local Variables in FlowMattic

Source: https://support.flowmattic.com/kb/article/62/using-local-variables-in-flowmattic

The **Local Variables** feature in the **FlowMattic Tools** module lets you **create, retrieve, update, and delete temporary variables** within a single workflow. These variables exist only during the execution of a workflow and can be incredibly useful for storing and manipulating values on the fly.

---

## 🔍 Where to Find This Feature

Local Variables are part of the **FlowMattic Tools** module. When creating or editing a workflow, choose an action, search for **"FlowMattic Tools"**, and select one of the available Local Variable actions.

---

## 🧰 What Are Local Variables?

Local variables are temporary variables that:
- Are accessible only during the **current workflow execution**
- Can be used to **store static values**, **intermediate results**, or **data across steps**
- Support two types:
  - **String** – A single text or numeric value
  - **Array** – A collection of key-value pairs

---

## 🔧 Available Actions

There are four key actions available:

1. **Create Local Variable**
2. **Get Local Variable**
3. **Update Local Variable**
4. **Delete Local Variable**

Let’s walk through each of them step by step.

---

### 1️⃣ Create Local Variable

Use this action to define and initialize a local variable.

#### 🔹 Configuration

- **Variable Name** – A name for your variable (e.g., `my_custom_variable`)
- **Variable Type** – Choose `String` or `Array`
- **Variable Values**:
  - If **String**, provide a single value
  - If **Array**, provide multiple key-value pairs

#### ✅ Example (Array)

```json
{
  "product": "FlowMattic",
  "quantity": 1
}
```

#### 🔁 Response
```json
{
  "status": "success",
  "variable_id": "a08d289c6e94207f1f1b8388fd6e8b3e",
  "value": {
    "product": "FlowMattic",
    "quantity": 1
  }
}
```

> **Note**: The `variable_id` will be used in subsequent steps to access this variable.

---

### 2️⃣ Get Local Variable

Retrieve the value of a previously created variable using its ID.

#### 🔹 Configuration

- **Variable ID** – Use dynamic tag like `{tools2.variable_id}`

#### ✅ Example Usage

Use this step to get values and pass them to a webhook, email, or conditional logic.

---

### 3️⃣ Update Local Variable

Modify the value of an existing variable.

#### 🔹 Configuration

- **Variable ID** – Use the ID from the "Create" step
- **Variable Type** – Must match the original type
- **Updated Values**:
  - You can change any key or add new ones

#### ✅ Example Update

```json
{
  "product": "Updated Name",
  "quantity": 2
}
```

---

### 4️⃣ Delete Local Variable

Removes a variable completely from the workflow memory.

#### 🔹 Configuration

- **Variable ID** – Use dynamic tag like `{tools4.variable_id}`

> Once deleted, the variable is no longer available for the remainder of the workflow run.

---

## 🧷 Use Case: Storing Static Data

Sometimes you need to reuse **static data** (like constants) across multiple steps.

### ✅ Example

Create a variable:
```json
{
  "company_name": "FlowMattic",
  "support_email": "support@flowmattic.com"
}
```

Now, instead of entering these values again and again, you can just use `Get Local Variable` wherever needed.

### 💡 Use Case

Send a thank-you email with the company name and email, then log the entry with the same details using a webhook.

---

## 💡 Real-World Use Cases

### ✅ Basic Use Cases
- Store and reuse user input like name or email
- Carry temporary values between steps
- Hold static information like support details or tax rates

### 🚀 Advanced Use Cases
- Build custom payloads for API calls step-by-step
- Store filter results from Google Sheets or Airtable temporarily
- Store status flags (e.g., `status = success`) to use in conditional paths
- Use as counters (e.g., `loop_count += 1`) for iterations

---

## 📘 Summary

| Action         | Purpose                                               |
|----------------|-------------------------------------------------------|
| **Create**     | Define a new variable                                 |
| **Get**        | Retrieve the value for further use                    |
| **Update**     | Modify contents of an existing variable               |
| **Delete**     | Remove the variable from memory                       |

---

Let us know if you have any questions about using Local Variables in FlowMattic!

---

# Using Lookup Table Module in FlowMattic

Source: https://support.flowmattic.com/kb/article/71/using-lookup-table-module-in-flowmattic

## Overview

The Lookup Table module in FlowMattic is designed to simplify workflows by mapping keys to values using a custom table. This feature is ideal for transforming values such as language codes to full language names, country codes to country names, user roles, and other similar mappings. It eliminates the need for complex conditional steps, making workflows cleaner and more dynamic.

---

## Steps to Configure the Lookup Table Module

### Step 1: Add the Lookup Table Action
1. Navigate to your workflow in FlowMattic.
2. Add a new action and select **"Lookup Table"** from the list of available modules.

---

### Step 2: Configure the Lookup

#### 🔑 Lookup Key (Required)
- Specify the key to be matched in the table.
- You can input static text or use dynamic tags from previous trigger/action steps.

**Examples:**
- Static Key: `mr`
- Dynamic Key: `{{trigger.language_code}}`

#### 🛠️ Fallback Value (Required)
- Provide a fallback value to be used if the lookup key is not found in the table.

**Example:**
`English`

#### 📋 Lookup Table
- Define the mapping of keys to values in a table format.
- Example:

| Key | Value   |
| --- | ------- |
| en  | English |
| mr  | Marathi |
| hi  | Hindi   |

- Use the **"Add More"** button to add additional rows.

---

## Example Use Case

Imagine you receive a language code (`mr`) in a form submission and need to convert it into the full language name for further processing or integration with another app.

**Configuration:**
- **Lookup Key:** `mr`
- **Fallback Value:** `English`
- **Lookup Table:**

  | Key | Value   |
  | --- | ------- |
  | en  | English |
  | mr  | Marathi |
  | hi  | Hindi   |

**Expected Output:**
- If the key `mr` is found, the output will be `Marathi`.
- If the key is not found, the fallback value `English` will be returned.

---

## Tips for Effective Usage
- Use dynamic tags for keys to make workflows adaptive and responsive.
- Ensure the fallback value is meaningful and aligns with your workflow requirements.
- Regularly update the lookup table to accommodate new keys and values.

---

## Additional Context
The Lookup Table module also provides structured outputs, indicating whether the fallback value was used or the key was successfully matched. This ensures transparency in workflow execution and helps with debugging.

By leveraging this module, you can create workflows that are both efficient and scalable, reducing manual intervention and enhancing automation capabilities.

---

# Using Loop in Email Templates

Source: https://support.flowmattic.com/kb/article/118/using-loop-in-email-templates

The **Loop block** lets you repeat content multiple times in your emails - perfect for product catalogs, team rosters, event schedules, and more.

## What is a Loop?

Think of Loop as a "repeater" - you design content once, and it automatically duplicates for each item in your list. For example, if you have 10 products, the Loop will create 10 product cards automatically.

---

## Quick Start Guide

### Step 1: Add a Loop Block

1. Open the Email Template Builder
2. Click the Plus button to open the blocks and choose the **Loop** block from the blocks panel into your template
3. Inside the Loop block, add the content you want to repeat (columns, text, images, buttons, etc.)

### Step 2: Configure the Loop

Click on the Loop block to see its settings:

- **Data Source**: The name of your array (e.g., `products`, `team`, `events`). This needs to present in your JSON in Dynamic Data.
- **Loop Variable**: The name to use inside the loop (e.g., `product`, `member`, `event`). This isn't present, but used to refer the single item in your items.

**Example:**
- Data Source: `products`
- Loop Variable: `product`

![Loop data source and variables.png](/storage/kb-images/b746926966-inline.png)

### Step 3: Use Variables

Inside the Loop block, reference your data using this format:
```
{{loopVariable.property}}
```

**Examples:**
- `{{product.name}}` - Product name
- `{{product.price}}` - Product price
- `{{member.email}}` - Team member email
- `{{event.time}}` - Event time

---

## Pre-built Loop Templates

FlowMattic includes ready-to-use Loop templates. Just pick one, customize it, and send!

### 1. Product Catalog

Display products with images, descriptions, and prices.

**Your data should look like:**
```json
{
  "products": [
    {
      "name": "Wireless Headphones",
      "description": "Noise-canceling with 30-hour battery",
      "price": "$299.99",
      "image": "https://example.com/image.jpg",
      "url": "https://example.com/product"
    }
  ]
}
```

**Variables you can use:**
- `{{product.name}}`
- `{{product.description}}`
- `{{product.price}}`
- `{{product.image}}`
- `{{product.url}}`

---

### 2. Team Directory

Showcase team members with photos and contact info.

**Your data should look like:**
```json
{
  "team": [
    {
      "name": "Sarah Johnson",
      "role": "CEO",
      "bio": "15 years in tech leadership",
      "photo": "https://example.com/sarah.jpg",
      "email": "sarah@example.com",
      "phone": "+1 (555) 123-4567"
    }
  ]
}
```

**Variables you can use:**
- `{{member.name}}`
- `{{member.role}}`
- `{{member.bio}}`
- `{{member.photo}}`
- `{{member.email}}`
- `{{member.phone}}`

---

### 3. Event Schedule

List conference sessions, meetings, or events.

**Your data should look like:**
```json
{
  "events": [
    {
      "time": "9:00 AM",
      "title": "Opening Keynote",
      "speaker": "Dr. Jane Smith",
      "description": "Latest breakthroughs in AI",
      "location": "Main Auditorium",
      "type": "🎤 Keynote"
    }
  ]
}
```

**Variables you can use:**
- `{{event.time}}`
- `{{event.title}}`
- `{{event.speaker}}`
- `{{event.description}}`
- `{{event.location}}`
- `{{event.type}}`

---

## Using Loop Templates in Workflows

### Option 1: Test in Template Builder

1. Open your Loop template in the builder
2. Click **"Dynamic Data"** tab in the right panel
3. Paste your JSON test data
4. The preview updates instantly to show all items

![Email Templates ‹ FlowMattic — WordPress 2025-11-05 at 10.20.07 PM.png](/storage/kb-images/0ac809d397-inline.png)

### Option 2: Send from Workflow

1. In your workflow, add **"Send Template Email"** action
2. Select your Loop template
3. In the **Template Variables** field, pass your data:

**Example for products:**
```
{
  "products": [
    {"name": "Item 1", "price": "$99"},
    {"name": "Item 2", "price": "$149"}
  ]
}
```

You can also use dynamic data from previous workflow steps!

---

## Tips & Tricks

### ✅ Keep It Simple
Start with 2-3 items to test, then scale up

### ✅ Match Your Data Structure
Your JSON array name must match the Loop's "Data Source" setting

### ✅ Use Descriptive Variable Names
- For products: use `product` not `item`
- For team members: use `member` not `person`
- Makes templates easier to understand

### ✅ Test with Real Data
Copy actual data from your database/API to ensure everything displays correctly

### ✅ Nested Data Works Too
You can access nested properties:
- `{{product.pricing.regular}}`
- `{{member.contact.phone}}`

---

## Common Use Cases

### E-commerce
- Product catalogs
- Order confirmations with line items
- Shopping cart reminders
- Best sellers lists

### Events & Conferences
- Event schedules
- Speaker lineups
- Workshop agendas
- Venue locations

### Team & Organizations
- Employee directories
- Meet the team pages
- Board member listings
- Department rosters

### Real Estate
- Property listings
- Open house schedules
- Featured properties
- Agent directories

### Education
- Course catalogs
- Class schedules
- Faculty directories
- Student rosters

---

## Troubleshooting

**Loop not showing items?**
- Check that your Data Source matches your array name exactly
- Verify your JSON is valid (use a JSON validator)
- Make sure your array has items in it

**Variables not displaying?**
- Double-check variable names match your data properties
- Use correct syntax: `{{variable.property}}`
- Ensure no typos in property names

**Styling looks wrong?**
- Each item inherits the Loop block's styling
- Customize padding and background color in Loop settings
- Child blocks inside the Loop can have their own styles

---

## How It Works Behind the Scenes

When you send an email, FlowMattic processes your Loop using **LiquidJS** template engine:

**Your template:**
```html
{% for product in products %}
  <div>{{product.name}} - {{product.price}}</div>
{% endfor %}
```

**Becomes:**
```html
<div>Product 1 - $99</div>
<div>Product 2 - $149</div>
<div>Product 3 - $199</div>
```

All automatic - you just provide the data! 🎉

---

## Need More Help?

- Check out the pre-built Loop templates for inspiration
- Copy a template and modify it to learn how it works
- Start simple with 1-2 fields, then add more complexity

Happy looping! 🚀

---

# Using Magic Link Module in FlowMattic

Source: https://support.flowmattic.com/kb/article/70/using-magic-link-module-in-flowmattic

### Overview
The Magic Link module in FlowMattic allows you to trigger workflows seamlessly when a visitor or site user clicks a specific link on your WordPress site. This feature provides flexibility through customizable parameters, enabling tailored user experiences and automation triggers.

### What is the Magic Link module?
The Magic Link module lets you start any FlowMattic workflow simply by letting a site user —or even an anonymous visitor—click a hyperlink. Instead of waiting for a form submission, webhook, or schedule, the workflow fires instantly when the link is visited.
Behind the scenes FlowMattic:

- Verifies the link (using a random, unguessable workflow ID).
- Records the click for your logs/analytics.
- Runs the workflow in the background.
- (Optional) Redirects the clicker to a page you choose.

Because you embed the link with a WordPress shortcode, you can drop it into posts, Elementor blocks, menu items, custom frontend dashboards that render shortcodes.

### Why use a Magic Link?

| Scenario                                         | How the Magic Link helps                                                                                          |
| ------------------------------------------------ | ----------------------------------------------------------------------------------------------------------------- |
| **Self-service actions**—e.g. “Generate invoice” | A logged-in customer clicks a link in their dashboard; your invoicing workflow runs and delivers a PDF.           |
| **Gated downloads**—e.g. “Download e-book”       | Visitor clicks, the workflow adds them to your CRM, tags them, then redirects them to the file.                   |
| **One-click campaigns**                          | Send an email blast: every click instantly triggers a personalised workflow (apply tags, start automation, etc.). |


### How the Magic Link Works

- Link render – The shortcode expands to an HTML `<a>` tag at page load or during email rendering.
- Click – When clicked, FlowMattic receives a secure request containing the Magic Link ID.
- Workflow execution – The associated workflow starts immediately and logs the run.
- Redirect – The browser is sent to the redirect URL you specified

### Prerequisites

- FlowMattic ≥ 5.1.1 installed & activated.
- A published workflow that should run on click.
- Proper user roles/permissions set if the workflow must only run for logged-in users.

### Steps to Implement the Magic Link

1. **Generate the Magic Link Shortcode:**
- Go to FlowMattic ▸ Workflows and open or create new workflow.
- Choose the trigger app as `Magic Link` and choose the event as `Magic Link Clicked`
- Click Continue button and go to the Configure tab.
- You will see the following basic shortcode template to add the Magic Link to your WordPress page:
   ```
   [fm_magic_link id="YOUR_WORKFLOW_ID" link_text="Click Here"]
   ```
   FlowMattic will automatically replace the `YOUR_WORKFLOW_ID` with the ID of the workflow you are editing.

2. **Customize the Shortcode Parameters:**
   Enhance the Magic Link's functionality by using the following parameters:

| Parameter              | Purpose                                                                                  | Example                              |
| ---------------------- | ---------------------------------------------------------------------------------------- | ------------------------------------ |
| `id`                   | The workflow's Magic Link ID (find it in the Magic Link tab inside the workflow editor). | `id="YDtUm40X6f"`                    |
| `link_text`            | Anchor text shown **when the visitor is logged in**.                                            | `link_text="Run My Report"`          |
| `visitor_link_text`    | Text shown **when the visitor is not logged in**. Falls back to `link_text` if omitted.          | `visitor_link_text="Sign in to run"` |
| `user_redirect_url`    | Where to send a logged-in user after the click (absolute or relative URL).                       | `user_redirect_url="/thank-you/"`    |
| `visitor_redirect_url` | Where to send non-logged-in visitors.                                                           | `visitor_redirect_url="/login/"`     |
| `css_class`            | Custom class(es) added to the `<a>` tag.                                                        | `css_class="btn btn-primary"`        |
| `css_id`               | Custom ID for the `<a>` tag.                                                                 | `css_id="start-workflow"`            |
| **Custom Fields**      | Any custom parameter you define (e.g., `product_id`, `user_role`, `campaign_name`).     | `product_id="12345"`                 |

### Using Custom Fields in Magic Links

Custom fields allow you to pass additional data from the Magic Link to your workflow. Any parameter you add to the shortcode (besides the standard parameters listed above) will be captured and made available in your workflow's trigger data. This enables dynamic, context-aware workflows.

#### How Custom Fields Work
1. Add any custom parameter to your Magic Link shortcode
2. When the link is clicked, FlowMattic captures all custom field values
3. Access the custom field values in your workflow using the Magic Link trigger's output data
4. Use these values in subsequent workflow steps for conditional logic, personalization, or data processing

#### Practical Use Cases for Custom Fields

| Use Case                           | Custom Fields                                      | Workflow Action                                                                                      |
| ---------------------------------- | -------------------------------------------------- | ---------------------------------------------------------------------------------------------------- |
| **Product-specific downloads**     | `product_id="PRO-123"` `format="pdf"`              | Check the product ID, verify user access, then deliver the requested file format                     |
| **Campaign tracking**              | `campaign_name="spring-sale"` `source="email"`     | Track which campaign generated the click, log to analytics, apply appropriate tags in CRM            |
| **User segmentation**              | `tier="premium"` `region="north-america"`          | Run different automation paths based on user tier and region                                         |
| **Event registration**             | `event_id="webinar-2025"` `session="morning"`      | Register user for specific event session, send confirmation email with session details                |
| **Dynamic content delivery**       | `content_type="video"` `language="es"`             | Deliver content in the requested format and language based on user preference                        |
| **A/B testing**                    | `variant="A"` `test_id="homepage-cta"`             | Track which variant was clicked, log results for analysis                                            |
| **Referral tracking**              | `referrer_id="USER-456"` `reward_type="discount"`  | Credit the referrer, apply appropriate reward, create commission record                              |

#### Examples with Custom Fields

**Example 1: Product Download Link**
```
[fm_magic_link
 id="YDtUm40X6f"
 link_text="Download Premium Template"
 product_id="TMPL-2025-PRO"
 format="sketch"
 license_type="extended"
 css_class="download-btn"]
```
**Workflow use:** The workflow can check if the user has purchased `product_id`, verify the `license_type`, and deliver the file in the requested `format`.

**Example 2: Event Registration**
```
[fm_magic_link
 id="ABC123XYZ"
 link_text="Register for Morning Session"
 event_id="webinar-automation-101"
 session="morning"
 timezone="EST"
 user_redirect_url="/thank-you-registration/"]
```
**Workflow use:** Register the user for the specific `event_id` and `session`, send calendar invite in their `timezone`, and add them to the event email sequence.

**Example 3: Multi-language Support**
```
[fm_magic_link
 id="LNG789MNO"
 link_text="Descargar Guía"
 content_id="guide-getting-started"
 language="es"
 region="latin-america"]
```
**Workflow use:** Deliver the guide (`content_id`) in Spanish (`language`), apply region-specific formatting, and track engagement by region.

**Example 4: Referral Program**
```
[fm_magic_link
 id="REF456DEF"
 link_text="Claim Your Bonus"
 referrer_id="USER-12345"
 campaign="friend-referral"
 reward_amount="50"
 css_class="referral-link"]
```
**Workflow use:** Credit the `referrer_id` account, apply the `reward_amount` as credits or discount, log the referral under the specific `campaign`.

#### Best Practices for Custom Fields
- **Use descriptive names:** Choose field names that clearly indicate their purpose (e.g., `product_id` instead of `pid`)
- **Keep values simple:** Avoid special characters and spaces in field values; use hyphens or underscores instead
- **Document your fields:** Maintain a list of custom fields used across different Magic Links for consistency
- **Test thoroughly:** Always test your Magic Links with custom fields to ensure the workflow receives and processes the data correctly
- **Use in conditions:** Leverage custom field values in workflow conditional logic to create dynamic, intelligent automations

3. **Example of a Fully Customized Shortcode:**
   Below is an example of a shortcode with all parameters including custom fields:
   ```
   [fm_magic_link
    id="YDtUm40X6f"
    link_text="Check your collection"
    visitor_link_text="Explore Cars"
    user_redirect_url="https://example.com/dashboard"
    visitor_redirect_url="https://example.com/signup"
    css_class="custom-class"
    css_id="magic-id"
    collection_type="premium"
    category="sports-cars"]
   ```
   In this example, `collection_type` and `category` are custom fields that will be passed to the workflow, allowing you to filter or process data based on these values.

4. **Add the Shortcode to Your WordPress Page:**
   Copy the generated shortcode and paste it into the desired page or post on your WordPress site. The Magic Link will automatically display based on the settings you configured.

### Tips for Optimizing Your Magic Link
- **Styling the Link:** Use the `css_class` and `css_id` parameters to apply custom styles that align with your website's design.
- **Testing the Workflow:** Ensure the workflow ID is correct and test the Magic Link functionality across different user scenarios (logged-in users vs. visitors).
- **Redirect URLs:** Use meaningful redirect URLs to guide users to the appropriate pages after they click the Magic Link.
- **Leverage Custom Fields:** Use custom fields to pass contextual data (like product IDs, campaign names, user preferences) to your workflows for more intelligent and personalized automation.
- **Capture & Test Custom Fields:** After adding custom fields to your shortcode, use the "Capture response" button in the workflow editor to test and verify that all custom field data is being received correctly.

By integrating the Magic Link module into your WordPress site, you can create a seamless and automated experience for your users and visitors.

---

# Using Magic Login Link

Source: https://support.flowmattic.com/kb/article/63/using-magic-login-link

# 🔐 Magic Login Link – FlowMattic Tools Module

The **Magic Login Link** action in the **FlowMattic Tools** module allows you to send your users or team members a special one-time login link. When the link is clicked, it logs the user in **automatically**, without asking for a password.  

> ⚠️ The link is valid for **1 hour only** and can be used **only once**. After that, it's either expired or invalid.

---

## ✨ What is the Magic Login Link?

A **Magic Login Link** is a temporary, encrypted, one-time-use URL that logs a user into your site without requiring their password.

It's perfect when:
- You want to give temporary access.
- Your users forgot their password but need urgent access.
- You want to provide a seamless login experience without sending credentials.

---

## 🛠️ Where to Find It?

You can find the **Magic Login Link** action inside the **FlowMattic Tools module** while building your workflow.

1. Go to **Workflows**.
2. Add a new step.
3. Select **FlowMattic Tools** from the app list.
4. Choose the **Generate Magic Login Link** action.

---

## 🧭 Step-by-Step Guide

### Step 1: Open the Workflow
- Create a new workflow or edit an existing one inside FlowMattic.

### Step 2: Add Action – Generate Magic Login Link
- In the action app list, search for **FlowMattic Tools**.
- Select **Generate Magic Login Link**.

### Step 3: Configure the Action

#### ✅ User ID or Email *(Required)*
Enter the user’s ID or email address for whom you want to generate the login link.

#### 🌐 Redirect URL *(Optional)*
Enter the URL where the user should be redirected **after** clicking the login link.  
_Default: homepage_

#### ⏱️ Redirect URL on Expired *(Optional)*
Enter the URL where the user should be redirected if the link is **expired**.  
_Default: login page_

> 💡 Note: The login link is valid for **1 hour** only. It is **not reusable**.

### Step 4: Use the Link
Once the workflow runs, the link will be generated in the step response. You can use this link:
- In an email
- In an SMS
- In a WhatsApp message
- Or anywhere else using FlowMattic actions

---

## 🧪 Example Use Cases

### 📩 1. Send Login Access via Email
Automatically email a login link to your user when they fill out a contact form.

### 🔄 2. Reset Access Without Password
Let users log in through a magic link instead of resetting their password.

### 🔐 3. Temporary Client Access
Allow clients to log into a staging site for 1 hour with a one-time secure link.

### 🧑‍🤝‍🧑 4. Invite Team Members
Send new staff or collaborators a magic login link to access their dashboard securely.

---

## 🙋‍♂️ Frequently Asked Questions

### ❓ Is it safe to use the Magic Login Link feature?

**Yes, absolutely!**  
The link is:
- Encrypted using built-in secure methods
- Not stored in your database
- Automatically invalidated after first use
- Limited to 1-hour validity

There’s **no way to alter, extend, or reuse** the link.

---

### ❓ What happens if the user shares the link?

If the user shares the link **before** using it:
- The **first person** who clicks the link will gain access.

If the user has **already clicked** the link:
- The link becomes invalid and sharing it has **no effect**.

---

### ❓ Can I change the expiry time?

**No**, the expiration is **fixed to 1 hour** due to security and technical reasons. This helps ensure:
- Short-lived access
- Higher security
- Minimal misuse

---

### ❓ What happens if the user clicks after 1 hour?

They’ll be redirected to the URL set in **"Redirect URL on Expired"** field.  
If you leave this blank, they will be sent to your site’s **login page**.

---

### ❓ Can I use it for WooCommerce or Membership sites?

Yes!  
You can generate a login link for any **registered user**, no matter the role (Subscriber, Customer, Administrator, etc.).

Use it to:
- Let customers check their order
- Give members access to premium content

---

## 🔚 Conclusion

The **Magic Login Link** is a powerful way to streamline user logins without compromising security. Whether you're offering temporary access, simplifying logins, or automating user access flows, this action helps you do it all — safely and efficiently.

---

# Using the PHP Array Module

Source: https://support.flowmattic.com/kb/article/50/using-the-php-array-module

Article: Effectively using PHP Array module

#### Overview
The PHP Array module is a versatile tool designed to help you manage and manipulate JSON data within your workflows. This guide provides a detailed explanation of the available actions in the module, along with examples to help you understand their application.

---

#### Available Actions

- **Get Value by Index**
Get value of a specified index of an array

- **Get Array Count**
Get count of total number of items in array

- **Array Search**
Searches an array for a given value and returns the key

- **Convert List to Array**
Converts a list to an array

- **Convert Array to List**
Converts an array to a list

- **Insert Value at Index**
Inserts a value at a specified index in an array

- **New Line to Array**
Converts a new line separated list to an array

- **Extract JSON Data**
Extracts JSON data to individual items

- **Itemize Array**
Converts an array to individual items

- **Create Line Items**
Creates a list of line items from multiple fields


#### Action Details with Examples

### 1. Get Value by Index
This action allows you to get the value of a specified index of an array.
For example, if you have an array of fruits `["apple", "banana", "cherry"]`, you can use this action to get the value at index 1, which is 'banana'. For more advanced use cases, this works with nested arrays as well. For example, if you have an array of fruits and each fruit has a color, you can get the color of the fruit by specifying the fruit index, eg. your array is - `[{"apple": "red"}, {"banana": "yellow"}, {"cherry": "red"}]`, you can get the color of banana by specifying the index as banana, and you will get the response as yellow.

### 2. Get Array Count
This action allows you to get the count of the total number of items in an array.
For example, if you have an array of fruits `["apple", "banana", "cherry"]`, you can use this action to get the count of the total number of fruits, which is 3.

### 3. Array Search
This action allows you to search an array for a given value and returns the key of first occurrence.
For example, if you have an array of fruits `["apple", "banana", "cherry"]`, you can use this action to search for the value 'banana' and it will return the key 1. A more advanced use case is when you have a nested array of fruits and each fruit has a color, you can search for the color 'red' and it will return the key of the first occurrence of the color 'red'. eg. your array is - `[{"apple": "red"}, {"banana": "yellow"}, {"kiwi": "green"}, {"cherry": "red"}]`, you can search for the color 'red' and it will return the key of the first occurrence of the color 'red'. If you search for the color 'green', it will return the key of the first occurrence of the color 'green', which is 2.

### 4. Convert List to Array
This action allows you to convert a list to an array. A list is a string of values separated by a delimiter, eg. a comma separated list of fruits - "`apple, banana, cherry`". You can use this action to convert this list to an array of fruits `["apple", "banana", "cherry"]`.
Note: This action will not work with nested lists.

### 5. Convert Array to List
This action allows you to convert an array to a list. An array is a collection of values, eg. an array of fruits `["apple", "banana", "cherry"]`. You can use this action to convert this array to a comma separated list of fruits - "`apple, banana, cherry`".
Note: This action will not work with nested arrays.

### 6. Insert Value at Index
This action allows you to insert a value at a specified index in an array. 
For example, if you have an array of fruits `["apple", "banana", "cherry"]`, you can use this action to insert a new fruit 'kiwi' at index 1, and the new array will be `["apple", "kiwi", "banana", "cherry"]`. 
This action also works with nested arrays. For example, if you have an array of fruits and each fruit has a color, you can insert a new fruit with color at a specified index. eg. your array is - `[{"apple": "red"}, {"banana": "yellow"}, {"cherry": "red"}]`, you can insert a new fruit 'kiwi' with color 'green' at index 1, and the new array will be `[{"apple": "red"}, {"kiwi": "green"}, {"banana": "yellow"}, {"cherry": "red"}]`.

### 7. New Line to Array
This action allows you to convert a new line separated list to an array. A new line separated list is a string of values separated by a new line character, eg. a new line separated list of fruits - 
 ```
apple
banana
cherry
 ```

You can use this action to convert this new line separated list to an array of fruits, and you will get the response as `[{"list_item":"apple"},{"list_item":"banana"},{"list_item":"cherry"}]`.

### 8. Extract JSON Data
This action allows you to extract JSON data to individual items. If you have a JSON object with multiple key-value pairs, you can use this action to extract each key-value pair as an individual item. For example, if you have a JSON object - `{"name": "John", "age": 30, "city": "New York"}`, you can use this action to extract each key-value pair as an individual item, and you will get the response as - 
name - John
age - 30
city - New York

Now, you can map this data in the next action steps in your workflow for further processing.

### 9. Itemize Array
This action allows you to convert an array to itemized array of individual items. Then, the generated itemized array can be used in the next action steps in your workflow in Iterator module. For example, if you have an array of fruits `["apple", "banana", "cherry"]`, you can use this action to convert this array to an itemized array of individual items, and you will get the response as - `[{"item":"apple"},{"item":"banana"},{"item":"cherry"}]`.

### 10. Create Line Items
This action allows you to create an array of line items from multiple fields. If you have multiple fields with values, you can use this action to create an array of line items with each field value as an individual item. For example, if you have line item fields - name: John, age: 30, city: New York, you can use this action to create an array of line items and return the response as - `{"item_1":{"name":"John","age":"30","city":"New York","fm_item_index":1}}`.

These are the available actions in the PHP Array module and how you can effectively use them to manage your JSON data in your workflow. You can combine these actions with other modules in FlowMattic to create powerful workflows for your business needs.

---

### Tips for Effective Use
- Always validate your JSON data structure before processing.
- Use the **Extract JSON Data** action when working with nested JSON objects.
- Combine multiple actions for complex workflows, such as converting a list to an array and then inserting a value at a specific index.

### Additional Context
The PHP Array module is particularly useful for automating data transformations and ensuring consistency in your workflows. By leveraging these actions, you can streamline data processing and reduce manual intervention.

---

For further assistance, refer to the official documentation or reach out to support.

---

# Using the Text Formatter Module

Source: https://support.flowmattic.com/kb/article/54/using-the-text-formatter-module

### Overview
The Text Formatter module in FlowMattic allows users to perform advanced operations on textual content within their workflows. This article provides a detailed explanation of each available action, its use case, and examples to help you utilize the module effectively.

#### Available Actions and Use Cases

### 1. **Extract Pattern**
Use regular expressions to extract specific patterns or strings from the text.
- **Example**: Extract email addresses from a block of text using a regex pattern.

### 2. **Find in Text**
Search for specific text within the content.
- **Example**: Check if the word "FlowMattic" exists in the input text.

### 3. **Replace Text**
Search for a specific string and replace it with another string.
- **Example**: Replace the word "error" with "issue" in a log file.

### 4. **Basic Formatting**
Perform basic text formatting operations such as capitalization, case conversion, and extracting specific data.
- **Available Options**:
  - Capitalize

	Capitalize the first letter of each word. Example: "hello world" returns "Hello World".

  - Title Case

	Capitalize the first letter of each word except for articles, conjunctions, and prepositions. Example: "the quick brown fox" returns "The Quick Brown Fox".

  - Upper Case

	Convert all letters to uppercase. Example: "hello world" returns "HELLO WORLD".

  - Lower Case

	Convert all letters to lowercase. Example: "HELLO WORLD" returns "hello world".

  - Sentence Case

	Capitalize the first letter of the first word. Example: "hello world" returns "Hello world".

  - Remove HTML Tags

	Remove HTML tags from the text. Example: "<p>Hello, world!</p>" returns "Hello, world!".

  - Extract Numbers

	Extract numbers from the text. Example: "abc123def" returns "123".

  - Extract Email Address

	Extract email addresses from the text. Example: "Contact us at support@domain.com for assistance." returns an array of emails like - ["support@domain.com"].

  - Extract Phone Numbers

	Extract phone numbers from the text. Example: "Call us at 123-456-7890 for more information." returns all phone numbers like - phone_0: "123-456-7890".

  - Extract URLs

	Extract URLs from the text. Example: "Visit our website at https://www.domain.com for more information." returns all URLs like - url_0: "https://www.domain.com".

  - Get Length of String

	Get the length of the input text. Example: "Hello, world!" returns 13.

  - Get Word Count

	Get the number of words in the input text. Example: "Hello, world!" returns 2.

  - Trim White Space

	Remove leading and trailing white spaces from the text. Example: "  Hello, world!  " returns "Hello, world!".

### 5. **Split Text**
Split text based on a specific character or word and return a segment.
- **Example**: Split a full name into first and last names using a space as the delimiter. eg. "John Doe" returns as - 
	```
	item_0: John
	item_1: Doe
	```
Split Text action comes with the following options - 
  - Content to Split
	- Provide the text to be split. You can map the content from previous steps response.
  - Seperator
	- Provide the character or word to split the text. Default is a comma (,). To split based on a space, use [space] as the separator.
  - Segment Index
	- Segment of text to return after splitting. Available options are - 
		- First : Returns the first segment of the split text.
		- Second : Returns the second segment of the split text.
		- Last : Returns the last segment of the split text.
		- Second to Last : Returns the second to last segment of the split text.
		- All : Returns all segments of the split text as an array.

### 6. **Text Between**
Extract text between two specified strings.
You need to provide the text to search in and the start and end strings to extract the text between them.
- **Example**: Extract the price from a product description between the strings "Price: $" and "USD". 
	```
	Product Description: "This product is available at a Price: $100 USD."
	Start Text: "Price: $"
	End Text: " USD"
	Extracted Text: "100"
	```

### 7. **Default Value**
Sometimes, the response generated in previous step might be empty. In such cases, you can set a default value to be used instead. Set the default value for the response from previous step you want to use, and it will return the response value if available or the default value if not.
- **Example**: Set a default value for webhook response key "price" as "Not Available" if the key is empty.
```
Field: webhook1.price
Default Value: Not Available
```

### 8. **Truncate**
Limit text to a specific character length and truncate the rest.
- **Example**: Shorten a product description to 100 characters for a preview.

### 9. **URL Encode**
Encode text for safe use in URLs.
- **Example**: Convert spaces in a query string to `%20`.

### 10. **URL Decode**
Decode URL-encoded text back to its original form.
- **Example**: Decode `%20` back to spaces in a URL string.

#### Tips for Best Practices
- Use **Extract Pattern** with carefully crafted regex to avoid unintended matches.
- Combine **Split Text** and **Text Between** for advanced text parsing scenarios. Eg. Extracting data from structured text.
- Always test your workflows with sample data to ensure the desired output.

The Text Formatter module is highly versatile and can be integrated into various workflow scenarios, such as data cleaning, text extraction, and formatting.

By leveraging the Text Formatter module, you can streamline text processing tasks and enhance the efficiency of your workflows. If you have any questions or need assistance with a specific use case, feel free to reach out to our support team for guidance and support.

---

# Using WhatsApp Cloud API with FlowMattic

Source: https://support.flowmattic.com/kb/article/7/using-whatsapp-cloud-api-with-flowmattic

### Getting Started

Before we get started using the WhatsApp Cloud API, you need to follow these steps to create a business account, a meta app, and get your number registered and display name approved.

Lets start with creating Meta App first.

### Create Meta APP

- Go to [Meta Developers](https://developers.facebook.com/apps/)&nbsp;site and login with your Facebook account

- Click on the Create App button and choose the App type as Business then click Next.  
      
    ![](/storage/kb-images/49565d5ab0-whatsa-create-app.png)  
    

- On the next screen, fill the details - Display name, and email to be used to get notifications related to the app. If you already have a verified business profile, select it or just skip it for now. Once you feel all the details, click the Create App button to create an app.  
      
    ![](/storage/kb-images/064568c1c8-whatsa-create-app-details.png)  
    

- Once the app is created, you'll be redirected to the page where you'll be asked to add products to your app. Choose WhatsApp and click the Setup button to set it up.  
      
    ![](/storage/kb-images/112660cf28-whatsa-app-add-products.png)  
    

- WhatsApp getting started page will open. If you previously selected the Business, you won't see this step, if not, you'll be asked to select or create a Meta Business account. If you have one already, select the business from the drop-down or select&nbsp;**Create a business account**&nbsp;option. Click Continue.  
      
    ![](/storage/kb-images/f98d9a7b5c-whatsa-create-business-account.png)  
    

- Once you click the Continue button, a new Meta Business account will be created and you'll be redirected to the WhatsApp API Test page. Here, you will be able to see the following things - 
    \- Temporary Access Token  
    \- Your Phone Number to send WhatsApp notifications from  
    \- Phone Number ID - It will be used in the API calls by FlowMattic  
    \- WhatsApp Business Account ID - It will be used in the API calls by FlowMattic  
      
    ![](/storage/kb-images/32871574e8-whatsa-create-business-configuration.png)  
      
    Temporary Access Token is valid for 24 hours only. You'll need to reset it if you want to test the APIs after 24 hours. To keep your workflows running without the interruption, you'll need to have a Permanent Access Token. We will see how to create it later.  
    

- Click on the Add Phone Number button at the bottom of the screen and follow the on-screen instructions. You'll need to provide a Business Display name and Business WhatsApp number, which will be visible to your WhatsApp users. The number should not be in use for any WhatsApp account.  
    

- After adding the phone number, try sending a test message to your preferred WhatsApp number. You can set the WhatsApp number in the&nbsp;**To**&nbsp;section.&nbsp; You need to select your new WhatsApp Business number from the dropdown for the&nbsp;**From**&nbsp;number and then note down the&nbsp;**Phone Number ID**&nbsp;and&nbsp;**WhatsApp Business Account ID**. We will need these two later while configuring the FlowMattic action.  
    

- If you receive a WhatsApp message to your preferred number, you're all set to send the WhatsApp messages using FlowMattic as well. We need to get the&nbsp;**Permanent Access Token**&nbsp;only to keep running your workflows.

### Getting Permanent Access Token

- Go to&nbsp;[Meta Business Account](https://business.facebook.com/settings/)&nbsp;settings, and select your business from the list.

- Once you land on the Business settings admin page, go to Users -&gt; System Users

- Click on the Add button to add a new System User.

- A popup will open and ask you for the details as System Username and System User Role. Enter your preferred System Username and choose the User role as Admin.  
      
    ![](/storage/kb-images/e8e7b7d601-whatsa-create-system-user.png)  
    

- Click&nbsp;**Create System User**&nbsp;button. A new system user will be created.

- While you're in the System Users settings page, click the button Add Assets.

- From the popup, select the&nbsp;**Apps**&nbsp;as Asset Type, under Select Assets, choose the App you just created and under the App permissions choose&nbsp;**Full Control**. See below image for detailed info -&nbsp;  
      
    ![](/storage/kb-images/76b41d51b0-whatsa-assign-assets.png)  
    

- Click&nbsp;**Save Changes**&nbsp;and an asset will be added to the System user. Now, we are ready to generate our Permanent Access Token.

- Locate and click the button Generate Access Token. This will open up a popup and ask you to select the App you want to generate the token for.

- Select the App you created for WhatsApp. You will see a list of available permissions. Choose the following permissions only and create the Generate Token button.  
    \- whatsapp\_business\_messaging  
    \- whatsapp\_business\_management  
      
    ![](/storage/kb-images/404665a9fc-whatsa-manage-permissions.png)  
    

- Your token will be created and displayed for once only, so you need to copy it and store it somewhere before you close the popup. Once you close the popup, you will not be able to see the token unless you create a new one.

## Using WhatsApp Cloud API in FlowMattic

In order to use the WhatsApp Cloud API integration inside FlowMattic, you need to have the following things ready. We already have them all from the above steps :)

1. WhatsApp Access Token ( Either Temporary or Permanent )

3. Phone Number ID

5. WhatsApp Business Account ID

- Now go and install the&nbsp;**WhatsApp Cloud API**&nbsp;integration from your FlowMattic -&gt; Integrations admin page.

- Create a new workflow and set up your trigger step to get the data in your workflow. E.g Contact Form 7 with the user's mobile number field.

- Add an action step and select the&nbsp;**WhatsApp Cloud API**. You will be asked to provide the above required details as soon you select the app and the action step is created.

- Fill up the information of the access token, phone number and account ID etc.

- Select the phone number from your trigger step for the&nbsp;**Recipient Mobile Number.**

- Save the workflow once, so the settings will be available when you test the action.  
      
    ![](/storage/kb-images/09a5aad16d-whatsa-action-step-setup.png)  
    

- Now, choose how you want to send the message to users. You can select any option from the available actions -
    - **Send Template Message**
    
    - **Send Text Message**
    
    - **Send Image Message**
    
    - **Send Video Message**
    
    - **Send Document Message**

- For template messages, you need to pull the templates first, so locate the option for templates and click the refresh button to retrieve the templates.

- Once the templates are retrieved, you can choose any template you want to send to the user. If the template uses the dynamic variables, you'll see a list of the variables available for the template. You need to fill the variable values. You can use dynamic tags from your trigger step or enter static values as well.  
      
    ![](/storage/kb-images/6ef9acb6bc-whatsa-action-map-template.png)  
    

- For the other message types - Text, Image, Video, and Document, you will need to provide the corresponding value with the appropriate type.

- Once you're done with the settings, click on the Save and Test Action button. You'll instantly receive a message on your WhatsApp as per your preferences. If the message sending was successful, you'll receive the response as following - 
      
    ![](/storage/kb-images/8182e54d33-whatsa-action-response.png)

## FAQs

### 1\. What is WhatsApp Cloud API?

WhatsApp Cloud API is a Facebook-hosted platform of WhatsApp Business API, which helps you to send and receive messages. The Cloud API allows you to implement WhatsApp Business APIs without the cost of hosting of your own servers and also allows you to more easily scale your business messaging.

### 2\. Why should one use the WhatsApp Cloud API with FlowMattic instead of other providers?

The simple answer to this question would be - cut your costs. Other WhatsApp solution provides uses the same API, however, since they are hosting it on their servers, you need to pay additional to use it. With FlowMattic, you don't need to relay on the 3rd party providers and pay monthly.

### 3\. How does the pricing work?

The pricing for the messages is being handled by the Facebook ( Meta ) itself, and we don't have any control over it. You'll be paying to Meta for whatever your usage will be. You can read more about the pricing structure here -&nbsp;[https://developers.facebook.com/docs/whatsapp/pricing](https://developers.facebook.com/docs/whatsapp/pricing)

### 4\. Can I connect existing number of do I need a new one?

You can connect your existing number as well, just make sure it is not connected to any WhatsApp account ( personal or business ) before using it for the Cloud API.

---

# Verify Webhook Signatures from Stripe, GitHub, Shopify and More

Source: https://support.flowmattic.com/kb/article/244/verify-webhook-signatures

Anyone who knows a webhook URL can send it a request. For workflows that create orders, users or payments, that is not good enough — you want proof the request really came from Stripe, GitHub or whichever service you connected. That is what **signature verification** does: the sender signs every request with a secret only the two of you know, and FlowMattic checks the signature before the workflow runs.

FlowMattic verifies signatures from **Stripe, GitHub, Shopify, WooCommerce, Slack, Razorpay and Paddle** out of the box, plus a custom option for any other sender that signs with HMAC.

## Step 1 — Turn on authentication for the trigger

Open your webhook trigger and go to the **Configure** tab. In the **Authentication** card, switch on **Require authentication on incoming requests**, then set the **Authentication Method** to **Signature verification** — the option for services that sign their own requests. (The *Authentication key* method is for requests you send yourself, where you attach the key; signing services won't do that.)

![Signature verification selected in the webhook trigger's Authentication card](https://assets.infidesk.support/products/flowmattic/kb-images/release-72-apps/sig-01-stripe.png)

## Step 2 — Pick the sender and paste the signing secret

Choose the sender from the list. Picking it sets the header name, algorithm and encoding that service uses — there is nothing to match up by hand.

Then paste the **Signing Secret** from the sender's dashboard:

- **Stripe** — the endpoint's *signing secret* (starts with `whsec_`), shown when you create the webhook endpoint.
- **GitHub** — the *secret* you typed into the webhook settings.
- **Shopify / WooCommerce** — the webhook's *secret* / *signing secret*.
- **Slack** — the app's *Signing Secret* (Basic Information page).
- **Razorpay / Paddle** — the webhook *secret* from their dashboard.

This is **not** the same thing as the service's API key — it is a separate secret used only for webhooks.

## Step 3 — Choose what happens on failure

**On Verification Failure** has two modes:

- **Reject the request** — an unverified request is turned away with an HTTP 401 and never starts the workflow.
- **Allow it through, but record the failure** — log-only mode. The workflow still runs, and any verification failures are recorded so you can see them.

**Switching a live endpoint over? Start in log-only mode.** If the secret is wrong you'll see failures recorded without losing a single order — fix the secret, watch the failures stop, then move to *Reject*.

## Replay protection

Stripe, Slack and Paddle include a timestamp in their signatures, and FlowMattic checks it automatically: a signature older than five minutes is refused even if it is otherwise valid, which blocks captured-and-replayed requests. Nothing to configure — it comes with the sender. (A server clock that is far off can also trip this check, so verify the clock if valid requests are refused with a timestamp reason.)

## Other senders — the custom option

If your sender signs requests but isn't in the list, choose **Other / custom** and describe the signature:

![The custom sender option with header, prefix, algorithm and encoding fields](https://assets.infidesk.support/products/flowmattic/kb-images/release-72-apps/sig-02-custom.png)

- **Signature Header** — the header carrying the digest, e.g. `X-Acme-Signature`.
- **Header Prefix** — optional; some senders write `sha256=<digest>`. Leave empty if the header holds the digest alone.
- **Algorithm** — SHA-256, SHA-1 or SHA-512.
- **Encoding** — hexadecimal or Base64.

The signature is computed as an HMAC of the raw request body with your secret.

## Good to know

- **Existing workflows are untouched.** Triggers already using the authentication key keep working exactly as before — signature verification is a second method, not a replacement.
- **Both URLs are enforced equally.** The pretty webhook URL and the REST-style capture URL apply the same authentication rules.
- **A rejected request answers with HTTP 401** and a machine-readable reason, so the sender's webhook dashboard will show the failures — Stripe, for example, retries and flags the endpoint, which is your cue to check the secret.
- **Recent failures are kept per workflow** (the last ten) for diagnostics, so a misbehaving endpoint isn't a silent mystery.

---

# View, export, and store form submissions

Source: https://support.flowmattic.com/kb/article/205/view-export-and-store-form-submissions

Every submission to a FlowMattic form is stored in WordPress. This guide covers viewing responses, exporting them, and mirroring them into a Table.

## View responses

1. Open **FlowMattic → Forms**.
2. On your form's row, open the kebab (⋮) menu and click **View Submissions** (or click **View** in the **Submissions** column).
3. The **Responses** modal lists every submission. Use **Search responses…** to filter, and click **View** on any row to open its full details.

![The Responses modal for a form — the list of submissions with search and the Export all as CSV control](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-form-builder-responses-modal.png)

## Export to CSV

In the **Responses** modal opened from **View Submissions**, click **Export all as CSV** in the footer to download every submission as a CSV file (named `flowmattic-<slug>-submissions-<date>.csv`).

## Mirror submissions into a Table

To also keep submissions in a structured FlowMattic Table, open the form editor's **Settings** tab, find the **Submissions** group, turn on **Save every submission to a FlowMattic Table**, enter a **Table name**, and click **Create & link table**. New submissions are then written into the Table as they arrive, in addition to being stored as form responses.

![The Settings tab's Submissions group with Save every submission to a FlowMattic Table enabled](https://assets.infidesk.support/products/flowmattic/kb-images/fmx-form-builder-settings-submissions.png)

## Where submissions are stored

Responses are always stored in the `flowmattic_form_submissions` database table. The **Responses** viewer is the interface to that data; the CSV export and the optional FlowMattic Table are two ways to get the data out of it.

## Email notifications

Email notifications are configured in the editor's **Settings** tab under **Notifications** — **Admin email**, **Email me on each submission**, and **Send confirmation to respondent**. For conditional or formatted notifications, build a workflow on the **New Form Submission** trigger and add an email action instead. See *Connect a form to a workflow*.

---

# Webhook not capturing response

Source: https://support.flowmattic.com/kb/article/9/webhook-not-capturing-response

If your webhook is not capturing a response in FlowMattic, there could be a variety of reasons causing this issue. Here are the most common causes and steps you can take to resolve them:

* * *

### **1\. Firewall Blocking POST Requests to Your Site**

#### **Issue**:

Your server's firewall might be configured to block incoming POST requests, preventing the webhook from capturing the data.

#### **Solution**:

- Check your hosting provider's firewall settings or security plugins (e.g., Wordfence, Sucuri, or similar tools).

- Whitelist the IP addresses of the service or app sending the webhook request.

- Temporarily disable the firewall and test the webhook to confirm if this is the issue.

* * *

### **2\. Cloudflare Blocking POST Requests**

#### **Issue**:

Cloudflare's security rules might block incoming POST requests if they are considered suspicious or if specific firewall rules are enabled.

#### **Solution**:

- Log in to your Cloudflare account and navigate to the **Firewall Rules** or **Security** section.

- Check for any rules that might block POST requests and disable them temporarily.

- Add a **Page Rule** in Cloudflare to bypass security for your webhook URL:
    - URL Pattern: `https://yoursite.com/webhook/*`
    
    - Set the rule to disable security features like **Firewall**, **Browser Integrity Check**, or **Rate Limiting** for this path.

- Test the webhook after applying the changes.

* * *

### **3\. Permalink Settings Set to Default**

#### **Issue**:

If your WordPress **Permalink Settings** are set to "Plain" (default), the webhook URL may not be correctly routed to the appropriate endpoint.

#### **Solution**:

- Navigate to **Settings &gt; Permalinks** in your WordPress admin dashboard.

- Change the permalink structure to any other format (e.g., **Post Name** or **Custom Structure**).

- Save the changes and test the webhook again.

* * *

### **4\. Website Behind an Under Construction or Login Proxy**

#### **Issue**:

If your site is in **Under Construction Mode** or requires a login to access, the webhook request may be blocked before reaching FlowMattic.

#### **Solution**:

- Temporarily disable any **Under Construction** or **Maintenance Mode** plugins and test the webhook.

- If your site requires a login to access:
    - Use FlowMattic's **Webhook URL Base** setting and switch it to **REST API** mode. This often works better for sites behind login proxies.
    
    - Alternatively, whitelist the webhook URL or exclude it from the restriction in your maintenance mode or login settings.

* * *

### **Additional Tips for Debugging**

1. **Test the Webhook URL**:
    - Use tools like **Postman** or **Webhook.site** to manually send a POST request to your webhook URL.
    
    - Verify if the request is received in FlowMattic's **Webhook Listener**.

3. **Enable Debug Mode**:
    - If you're unable to determine the cause, enable debug mode in your WordPress site or hosting server to log incoming requests.

5. **Check Server Logs**:
    - Access your server's error logs to check if POST requests are being blocked or timing out.

7. **Contact Your Hosting Provider**:
    - If none of the above resolves the issue, contact your hosting provider to ensure POST requests to your site are not blocked by server settings.

* * *

### **Conclusion**

Webhook response issues often stem from server configurations or external security measures. By systematically addressing the potential causes listed above, you can quickly identify and resolve the problem. If the issue persists, FlowMattic’s support team is always here to assist!

---

# Webhooks by FlowMattic

Source: https://support.flowmattic.com/kb/article/12/webhooks-by-flowmattic

A webhook is a way for an application or service to automatically send real-time data to another application or service when a certain event occurs. It is a mechanism for web applications to communicate with each other in real-time.

When a webhook is set up, it typically involves the sending application making an HTTP request to the receiving application, along with some relevant data to the event that just occurred. The receiving application can then take that data and use it in whatever way is necessary to respond to the event.

Webhooks by FlowMattic is a feature the FlowMattic plugin provides that allows users to receive real-time notifications and updates from their applications or services. A webhook is a way for an application or service to send automated notifications to other applications or services when a specific event occurs. With webhooks, you can automate workflows and streamline your business processes, making managing and growing your business easier

Here is a step-by-step guide to help you set up your webhook with FlowMattic:

### **Step 1: Create a workflow**

Click on the “New Workflow” button in FlowMattic dashboard to create a new workflow. Then select “Webhooks by FlowMattic” as trigger. You can use webhook trigger to capture data from any external application as well. Make sure that the application has webhook support.

![](/storage/kb-images/67aa4c4834-image-16.png)

### **Step 2: Get the Webhook URL**

Webhook URL will be automatically generated by the application, so there is no need to manually create one. Once the webhook URL is generated, you simply need to copy it and use it in your application or service. It is important to note that the webhook URL should always be publicly accessible, otherwise, no application will be able to send data to the webhook URL.

![](/storage/kb-images/20a4f52186-image-15.png)

### **Step 3: Define Custom Webhook Responses**

Customize your webhook response by choosing the response you want to receive whenever you or the application access your Webhook URL. FlowMattic provides a response in form of JSON data, which is the default response. However, you can also create a custom response by entering your custom text or providing valid JSON code.

![](/storage/kb-images/356512d25a-image-14.png)

For example, if you want to receive the response user should enter the string in the custom response input as per their requirement, in this case, enter "OK" as the response text. &nbsp; Ensure that your JSON code is correct and properly formatted to avoid errors.&nbsp;

![](/storage/kb-images/f8fef6e165-image-13.png)

### **Step 4: Enable Webhook Authentication**

Decide whether you need authentication for your webhook. If authentication is required, FlowMattic will share a secret key with you, which you can use to authenticate your requests. If you enable this option, you will receive an authentication key that you need to provide along with the bearer token or API key. If you have enabled authentication, you must share the secret key with the application you want to integrate with FlowMattic. This is to ensure that the application can access your webhook URL securely.

![](/storage/kb-images/77f0b5a8a3-image-12.png)

### **Step 5: Define a Simple Response**

FlowMattic captures all the data it receives irrespective of the toggle being enabled or disabled. However, the toggle serves a different purpose. When the toggle is disabled, FlowMattic still captures all the data but only displays the parent level keys. The nested objects are set as JSON to the value of the respective parent key.

![](/storage/kb-images/1273c0ed27-image-11.png)

On the other hand, when the toggle is enabled, FlowMattic displays all the data including the nested objects, providing greater control over which data points are visible and which ones are not. This feature helps in streamlining the data collection process, making it more efficient.

![](/storage/kb-images/02b55f645b-image-10.png)

### **Step 6: Save the Workflow**

Once you have defined your webhook settings, click "Save" to save the workflow. Your webhook is now set up and ready to be triggered by the specified URL.

![](/storage/kb-images/5069f351fd-image-9.png)

## **Conclusion**

Setting up a webhook with FlowMattic requires you to choose your application, set up your webhook URL, customize your webhook response, validate your JSON code, decide on authentication, share the secret key, and receive a simple response. Following these steps will help you set up your webhook successfully and receive real-time data updates. If you need any assistance or have any questions, don't hesitate to get in touch with FlowMattic's customer support.

---

# Webpage Parser

Source: https://support.flowmattic.com/kb/article/42/webpage-parser

FlowMattic’s Webpage Parser is a versatile tool designed to streamline the process of extracting and utilizing data from web pages in your automated workflows. Whether you need to parse the content of a webpage into JSON format or retrieve metadata for analysis, this parser simplifies the task. By leveraging the Webpage Parser, you can automate data extraction and seamlessly integrate it into your workflows, saving time and effort.

With the Webpage Parser, you can process webpage data efficiently, enabling smooth interactions between various applications and systems. This feature empowers you to handle webpage content dynamically, making it a valuable addition to your automation toolkit.

#### Here is a Step-by-Step Guide to Help You Set Up Your Webpage Parser with FlowMattic

### Step 1: Create a New Workflow

Go to the FlowMattic Dashboard, where you can manage and create workflows. To start a new workflow, click the **“New Workflow”** button located in the top-right corner of the Dashboard. This will begin the process of creating your new workflow.

### Step 2: Add the Webpage Parser as an Action Step

- Click the “+” icon in your workflow to add a new action step.

- In the search bar that appears, type “Webpage Parser” and select it from the list of available actions. This will add the Webpage Parser to your workflow, allowing you to proceed with its configuration.

### Step 3: Choose the Action Event

The Webpage Parser offers two action events. Select the one that suits your requirement:

- **Parse Webpage by URL** : This action parses the content of any webpage URL and converts it into JSON data. This enables the data to be utilized in subsequent workflow steps.

- **Get Metadata** : This action retrieves metadata such as meta tags from any webpage URL. This is particularly useful for SEO analysis or webpage indexing tasks.

### Step 4: Configure the Settings

- Enter the publicly accessible URL of the webpage you want to process. Ensure the URL is accurate and accessible, as the parser will directly retrieve data from this location.

- Depending on the selected action event, the parser will either extract the webpage content or retrieve its metadata.

### Step 5: Test and Save Your Workflow

- Run a test to ensure the Webpage Parser is working as expected. Confirm that the webpage content or metadata is parsed and ready for use in the next steps of your workflow.

- Once the test is successful, save your workflow. You can now utilize the extracted data or metadata in other actions or processes within the same workflow.

---

# What is FlowMattic?

Source: https://support.flowmattic.com/kb/article/26/what-is-flowmattic

FlowMattic is a powerful automation tool designed to simplify and enhance workflows for WordPress users by facilitating easy connections between WordPress plugins, SaaS platforms, and web applications. It offers a no-code solution with a user-friendly interface, allowing for the creation of complex automations through drag-and-drop actions. This feature-rich platform includes unlimited workflows, dynamic data mapping, and advanced webhook functionalities, making it ideal for businesses seeking to improve efficiency and productivity without extensive technical knowledge.

By automating repetitive tasks and integrating various applications seamlessly, FlowMattic enables users to focus on more strategic aspects of their business, potentially leading to significant time savings and operational efficiencies. Its ability to customize workflows and adapt to specific business needs makes it a versatile tool for enhancing productivity across different domains.

---

# What is MCP Server?

Source: https://support.flowmattic.com/kb/article/72/what-is-mcp-server

# Understanding MCP Servers: A Complete Beginner's Guide to Model Context Protocol

## What is MCP? The Simple Explanation

Imagine you have a brilliant assistant who knows a lot about the world, but they're stuck in a room with no phone, no internet, and no way to access your personal files, calendar, or company databases. That assistant is like an AI model such as Claude - incredibly knowledgeable, but limited to what they learned during training.

**Model Context Protocol (MCP)** is like giving that assistant a secure phone line and access cards to connect with the outside world. It's a standardized way for AI models to safely interact with external data sources, tools, and services while maintaining security and user control.

## The Problem MCP Solves

Before MCP, AI models faced a significant limitation: they could only work with information they were trained on (which has a cutoff date) and whatever you directly shared in your conversation. They couldn't:

- Access your Google Drive documents
- Check your calendar for availability
- Pull data from your company's database
- Interact with your project management tools
- Connect to live APIs for real-time information

This meant you'd have to manually copy and paste information, explain context repeatedly, and couldn't leverage the AI's full potential for tasks involving your personal or business data.

## How MCP Works: A Simple Analogy

Think of MCP like a hotel concierge system:

**You (the guest)** have needs and requests
**The AI model (the concierge)** wants to help you
**MCP servers (specialized hotel staff)** each have access to different services

When you ask the concierge to "book me a dinner reservation," they don't personally call every restaurant. Instead, they connect with the restaurant booking specialist (an MCP server) who handles that specific task.

Similarly, when you ask Claude to "find my presentation about Q3 sales," Claude connects to a Google Drive MCP server that securely accesses your files and retrieves the information.

### MCP vs. Traditional Automation Tools

If you've used automation platforms like **Zapier** or **FlowMattic**, you already understand the concept of connecting different services together. However, there's a key difference:

- **Zapier/FlowMattic:** Create automated workflows that trigger when specific events happen (like "when I get an email, create a calendar event")
- **MCP Servers:** Enable real-time, conversational access to services through AI (like "check my calendar and suggest the best time for a meeting")

Think of traditional automation as setting up dominos that fall in sequence, while MCP is like having a smart assistant who can instantly access and work with any of your tools based on what you ask for in natural language.

## Key Components of MCP

### 1. MCP Servers
These are specialized programs that act as bridges between the AI model and external services. Each server typically focuses on one type of service or data source.

**Think of them like super-powered connectors:** If you've used FlowMattic or Zapier, you know how these platforms connect to services like Gmail, Google Sheets, Slack, etc. MCP servers work similarly, but instead of creating automated workflows, they provide real-time access for AI conversations. For example:

- A **Gmail MCP server** lets Claude read and search your emails when you ask "What did John say about the project?"
- A **Google Sheets MCP server** allows Claude to analyze your data when you ask "What were our best-selling products last month?"
- A **FlowMattic MCP server** could let Claude trigger specific workflows you've created when you say "Start my morning routine automation"

### 2. MCP Clients
These are applications (like Claude) that can connect to and communicate with MCP servers.

### 3. The Protocol Itself
This is the "language" that clients and servers use to communicate securely and efficiently.

## Real-World Use Cases for MCP Servers

### **Personal Productivity**

**Scenario:** You're planning a business trip
- **Without MCP:** You'd manually check your calendar, search for flights, copy hotel bookings, and paste everything into separate conversations
- **With MCP:** "Help me plan my trip to New York next month" - Claude connects to your calendar MCP server, travel booking APIs, and expense management tools to create a complete itinerary

**Scenario:** Managing your daily schedule
- **Without MCP:** "Let me copy my calendar events... I have a meeting at 2 PM, another at 4 PM..."
- **With MCP:** "What's my schedule looking like today?" - Claude checks your calendar directly and can even suggest optimal times for new tasks

### **Business and Enterprise**

### **Business Process Enhancement**

**For FlowMattic/Zapier Users:**
If you already use automation platforms, MCP servers can supercharge your existing workflows:

- **Scenario:** You have a FlowMattic workflow that creates tasks when emails arrive
- **With MCP:** "Analyze my incoming support emails and suggest which ones need immediate attention" - Claude can read emails, understand context, and even trigger your existing FlowMattic workflows for high-priority issues

**Advanced Workflow Management**
- **Traditional Zapier approach:** Set up triggers like "When invoice is paid → Send thank you email → Update spreadsheet"
- **MCP-enhanced approach:** "Review this month's invoice payments and handle follow-ups" - Claude can analyze payment patterns, identify issues, decide which follow-up actions are needed, and trigger the appropriate Zapier workflows

**Dynamic Business Decisions**
- **Challenge:** Your automated workflows are rigid - they do the same thing every time
- **MCP Solution:** Claude can make intelligent decisions about which workflows to trigger based on context, data analysis, and current business conditions

**Data Analysis and Reporting**
- **The Challenge:** Creating reports requires data from multiple sources (sales databases, marketing analytics, financial systems)
- **MCP Solution:** "Generate a quarterly performance report" - the AI connects to various MCP servers to gather, analyze, and synthesize data from multiple business systems

**Project Management**
- **The Challenge:** Tracking project status across different tools (Jira, Slack, GitHub, time tracking)
- **MCP Solution:** "What's blocking our mobile app release?" - the AI checks all connected project management MCP servers to identify bottlenecks and dependencies

### **Development and Technical Tasks**

**Code Repository Management**
- **Scenario:** A developer needs to understand a large codebase
- **MCP Solution:** The AI connects to GitHub/GitLab MCP servers to analyze code structure, recent changes, and suggest improvements

**Database Operations**
- **Scenario:** Analyzing business data stored in databases
- **MCP Solution:** Instead of writing SQL queries manually, you can ask "Show me our top customers this quarter" and the AI queries the database through an MCP server

**Infrastructure Monitoring**
- **Scenario:** Checking system health across multiple services
- **MCP Solution:** "Is everything running smoothly?" - the AI connects to monitoring MCP servers to check server status, performance metrics, and alert conditions

### **Content and Knowledge Management**

**Research and Writing**
- **Scenario:** Writing a comprehensive report on industry trends
- **MCP Solution:** The AI connects to research database MCP servers, news API servers, and internal knowledge base servers to gather current information

**Documentation Management**
- **Scenario:** Finding specific information across multiple documentation sources
- **MCP Solution:** "How do we handle customer refunds?" - the AI searches through connected knowledge base and policy document MCP servers

## MCP vs. FlowMattic/Zapier: Understanding the Difference

If you're familiar with automation platforms like FlowMattic or Zapier, here's how MCP compares:

### **Traditional Automation (FlowMattic/Zapier)**
- **Purpose:** Automate repetitive tasks with predetermined workflows
- **How it works:** "When X happens, do Y" (trigger-based)
- **Example:** "When I receive a new lead email, create a CRM contact and send a welcome sequence"
- **Strengths:** Great for consistent, predictable processes
- **Limitations:** Rigid rules, can't adapt to context or make complex decisions

### **MCP Servers**
- **Purpose:** Enable AI to access and work with your data in real-time
- **How it works:** "Help me with X" using whatever data and tools are needed (conversation-based)
- **Example:** "Help me follow up with leads from this week" - AI analyzes all leads, determines best approach for each, and can trigger appropriate FlowMattic workflows
- **Strengths:** Flexible, context-aware, can handle complex multi-step reasoning
- **Limitations:** Requires AI model, newer technology with fewer pre-built integrations

### **The Perfect Combination**
The most powerful setup combines both approaches:
- **Use FlowMattic/Zapier for:** Reliable, repetitive tasks that should always happen the same way
- **Use MCP with AI for:** Complex decision-making, data analysis, and determining when and which automations to trigger
- **Example workflow:** AI analyzes customer support tickets through MCP → decides on priority and category → triggers appropriate FlowMattic automation for each ticket type

### **For Users:**
- **Seamless Experience:** No more copying and pasting between applications
- **Real-time Information:** Access to current data, not just training data
- **Personalized Assistance:** AI can work with your specific data and preferences
- **Increased Productivity:** Complex tasks involving multiple systems become simple conversations

### **For Organizations:**
- **Security:** Controlled access to sensitive data through proper authentication
- **Standardization:** One protocol works with many different systems
- **Scalability:** Easy to add new data sources and capabilities
- **Compliance:** Audit trails and permission controls for data access

### **For Developers:**
- **Reusability:** Build once, use with any MCP-compatible AI
- **Flexibility:** Easy to create custom servers for specific needs
- **Community:** Shared ecosystem of MCP servers and tools

## Security and Privacy Considerations

MCP is designed with security in mind:

- **Authentication:** Users must explicitly grant access to each MCP server
- **Permissions:** Fine-grained control over what data the AI can access
- **Audit Logs:** Track what information was accessed and when
- **Local Control:** Many MCP servers can run locally, keeping sensitive data on your own systems

## Getting Started with MCP

### For End Users:
1. **Choose an MCP-compatible AI client** (like Claude Desktop)
2. **Install relevant MCP servers** for the services you use
3. **Configure authentication** for each service
4. **Start using natural language** to interact with your connected data

**If you already use FlowMattic or Zapier:**
- **Keep your existing automations** - they'll continue working as before
- **Add MCP servers** for the same services to enable AI interaction
- **Start simple:** Try asking AI to "check my latest Zapier runs" or "analyze my FlowMattic workflow performance"
- **Gradually expand:** Use AI to make smarter decisions about when and which automations to trigger

### For FlowMattic/Zapier Power Users:
Consider building MCP servers that can:
- **Monitor your automation platforms:** "How are my workflows performing this week?"
- **Trigger specific workflows:** "Start my end-of-month reporting automation"
- **Analyze automation data:** "Which of my FlowMattic workflows are most valuable?"
- **Suggest optimizations:** "Review my Zapier usage and suggest improvements"

### For Developers:
1. **Learn the MCP specification** (available in Anthropic's documentation)
2. **Choose a programming language** (Python, TypeScript, and other SDKs available)
3. **Build your MCP server** for specific data sources or tools
4. **Test with MCP clients** to ensure compatibility
5. **Share with the community** to help others

## The Future of MCP

MCP represents a fundamental shift in how we interact with AI systems. Instead of AI being limited to pre-trained knowledge, we're moving toward AI that can:

- Access real-time information from any connected source
- Perform actions on your behalf across multiple platforms
- Provide personalized assistance based on your specific context and data
- Integrate seamlessly into existing workflows and business processes

As more organizations adopt MCP, we can expect to see:
- A growing ecosystem of specialized MCP servers
- Better integration between different business tools
- More sophisticated AI assistants that truly understand your unique context
- New possibilities for automation and intelligent workflows

## Conclusion

Model Context Protocol is transforming AI from a knowledgeable but isolated assistant into a connected, context-aware partner that can work with your real data and tools. Whether you're managing personal tasks, running a business, or developing software, MCP opens up new possibilities for AI assistance that's both powerful and practical.

The key insight is simple: the most useful AI isn't just the smartest one - it's the one that can connect to and work with the information and tools that matter to you. MCP makes that connection possible, secure, and standardized.

As this technology continues to evolve, we're likely to see AI assistants become even more integrated into our daily workflows, making complex tasks feel as simple as having a conversation with a well-informed colleague who has access to all the right information at just the right time.

---

# What is Workflow?

Source: https://support.flowmattic.com/kb/article/33/what-is-workflow

A workflow in FlowMattic is an automated sequence of actions that connects different tasks, events, or processes within the platform. It defines the steps required to accomplish a specific goal or complete a task efficiently and effectively. Each workflow consists of a "Trigger" and one or more "Actions." When the trigger event occurs within FlowMattic, the specified actions are automatically executed, streamlining processes, reducing manual effort, and improving productivity.

In a workflow:

- **Trigger**: The starting point of the workflow, representing an event or condition that initiates the automated sequence of actions.

- **Actions**: The tasks or operations performed in response to the trigger event, such as creating tasks, sending notifications, updating records, or integrating with external tools and platforms.

Workflows in FlowMattic enable users to automate repetitive tasks, integrate various tools and systems, and orchestrate complex processes with ease. Whether it's managing sales leads, processing customer orders, or coordinating project tasks, workflows empower users to streamline their workflow, increase efficiency, and focus on higher-value activities.

Here are some examples of workflows in FlowMattic:

1. **New Order Notification Workflow**:
    - **Trigger**: A new order is placed on your WooCommerce website.
    
    - **Action**: FlowMattic sends a notification email to the sales team and adds the order details to a Google Sheet for record-keeping.
    
    - **Workflow**: This automated workflow in FlowMattic ensures that whenever a new order is received on your WooCommerce website, FlowMattic triggers the notification email to the sales team and updates the order information in a Google Sheet, streamlining communication and record-keeping processes.

3. **Contact Form Integration Workflow**:
    - **Trigger**: A new contact form submission is received on your website.
    
    - **Actions**:
        - FlowMattic creates a new contact in WordPress.
        
        - FlowMattic adds the contact to your email marketing list in Mailchimp.
    
    - **Workflow**: When someone submits a contact form on your website, FlowMattic automatically creates a new contact in WordPress and adds them to your Mailchimp email list, ensuring efficient lead capture and seamless integration between your website, CRM, and email marketing platform.

5. **Lead Management Workflow**:
    - **Trigger**: A new lead is added to your CRM system.
    
    - **Actions**:
        - FlowMattic assigns a follow-up task to a sales representative in your project management tool (e.g., Asana or Trello).
        
        - FlowMattic sends a personalized follow-up email to the lead using your email marketing platform.
    
    - **Workflow**: Upon the addition of a new lead in your CRM system, FlowMattic triggers the assignment of a follow-up task to a designated sales representative and simultaneously sends a personalized follow-up email, ensuring prompt follow-up and efficient lead nurturing.

In these examples, FlowMattic serves as the platform for orchestrating automated workflows, by connecting different actions and events to streamline processes and improve productivity.

---

# What's new in the FlowMattic 7.0 admin

Source: https://support.flowmattic.com/kb/article/217/whats-new-in-the-flowmattic-70-admin

FlowMattic 7.0 rebuilt the admin around a persistent sidebar that stays with you across every FlowMattic screen. If you have been using FlowMattic for a while, a few things have moved. This article covers where everything went.

**Nothing was removed.** The FlowMattic sidebar is an additional, in-page navigation — the standard WordPress submenu under **FlowMattic** still lists everything it always did. If you cannot find something in the new sidebar, it is still in the WordPress menu.

![The FlowMattic 7.0 admin: the persistent sidebar on the left with its six sections, next to the dashboard](https://assets.infidesk.support/products/flowmattic/kb-images/v70/217-admin-sidebar.png)

## How the sidebar is organised

Six sections:

- **Overview** — Dashboard
- **Automate** — Workflows, AI Assistants, MCP Server
- **Connect** — Integrations, Connects, Custom Apps
- **Data** — WP Tables, Variables, Email Templates, PDF Templates, Image Templates, Forms, Bookings, FlowMattic Tables
- **Monitor** — History, Status
- **System** — Settings, Patcher

## What was renamed

### "Tables" is now "WP Tables"

This is the one that catches people out. The tables feature you have been using is now labelled **WP Tables**, and it sits in the **Data** section. Your tables and data are exactly where they were — only the label changed.

Directly below it you will see **FlowMattic Tables**. That is a **different, premium product** — a managed database hosted by us. If you have not subscribed to it, that screen shows the plans rather than your data.

So: **your existing tables are under WP Tables.**

### Others

- **Task History** now appears as **History** in the sidebar. The page itself is still titled Task History and the URL is unchanged.
- **Status Page** now appears as **Status**.

## Two things that are not in the sidebar

- **License** has no sidebar entry. Reach it from the small padlock license card at the bottom of the sidebar, or from the WordPress menu under **FlowMattic → License**.
- **MCP Tools History** is reachable from the WordPress menu under FlowMattic.

## The search box and ⌘K

At the top of the sidebar there is a search box, and pressing **⌘K** (Mac) or **Ctrl+K** (Windows/Linux) jumps your cursor into it.

**It searches the FlowMattic menu, not your data.** Type "book" and it filters the sidebar down to Bookings. It is a fast way to jump between screens without reaching for the mouse.

It does **not** search inside your workflows, connects, tasks or templates. If you are looking for a particular workflow by name, use the search on the Workflows screen itself.

One cosmetic note: the hint badge shows the ⌘ symbol on every platform. On Windows and Linux, **Ctrl+K** is the shortcut that works.

## Where the sidebar does not appear

The **Workflow Builder** and the **onboarding wizard** deliberately run without it — both need the full width of the screen for the canvas. Closing the builder returns you to a screen with the sidebar. This is intended, not a glitch.

## On smaller screens

Below about 1100px wide the sidebar collapses into a drawer behind a menu button in a sticky bar at the top. Tap the button to slide it out; tap outside it, choose an item, or press Escape to close it.

## A couple of things worth knowing

- **The counts next to menu items refresh about once a minute.** If you have just created a workflow and the number has not moved yet, give it a moment — your data is fine.
- **Settings, Status, License and Patcher are only visible to administrators.** That has always been the case; if a non-admin colleague cannot see them, this is not new behaviour.
- **Integrations can be hidden** by a setting. If it is missing from your sidebar and you are not an administrator, check **FlowMattic → Settings** with someone who is.

## If the sidebar looks broken

If the sidebar appears misaligned, unstyled or overlapping other content, it is nearly always another plugin combining or reordering WordPress admin stylesheets — commonly an optimisation or caching plugin with CSS concatenation enabled. Try excluding FlowMattic's admin styles from that plugin, or disable CSS concatenation and reload. If that fixes it, let us know which plugin it was so we can look at compatibility.

---

# Whitelisting FlowMattic Webhook Endpoints on Cloudflare

Source: https://support.flowmattic.com/kb/article/126/whitelisting-flowmattic-webhook-endpoints-on-cloudflare

When using FlowMattic with Cloudflare or similar security services, you may encounter issues where webhooks fail or return **403 Forbidden** errors, Or your Connect fails the authentication. This happens because Cloudflare's security features (Bot Management, WAF, Browser Integrity Check) can mistakenly block legitimate webhook requests from external applications.

This guide will walk you through the process of whitelisting FlowMattic webhook endpoints in Cloudflare to ensure your automations work seamlessly.

---

## Why Whitelisting is Necessary

FlowMattic uses webhook endpoints to receive data from external applications such as:

- Zapier, Make (Integromat), Pabbly Connect
- Payment gateways (Stripe, PayPal, Razorpay)
- CRM systems (HubSpot, Salesforce)
- Email marketing platforms (Mailchimp, ConvertKit)
- Custom integrations and third-party services

When Cloudflare's security rules are active, these webhook requests may be blocked, causing:

- Webhooks to fail with 403 Forbidden errors
- Workflow triggers not firing
- Data not being received from external applications
- Integration failures with third-party services
- Authentication failing for apps that use OAuth callbacks via webhooks

---

## FlowMattic Webhook Endpoints to Whitelist

FlowMattic provides two webhook URL formats that need to be whitelisted:

| Endpoint Pattern | Description |
|-----------------|-------------|
| `/wp-json/webhook/capture/*` | REST API webhook endpoint |
| `/webhook/capture/*` | Shortened webhook URL (custom rewrite) |

### Example Webhook URLs

```
https://example.com/wp-json/webhook/capture/abc123
https://example.com/webhook/capture/abc123
```

> **Note:** The `abc123` portion is your unique workflow ID. The whitelist rules use wildcards to cover all workflow IDs.

---

## Step-by-Step Cloudflare Configuration

### Step 1: Access Cloudflare Dashboard

1. Log in to your [Cloudflare Dashboard](https://dash.cloudflare.com/)
2. Select your domain from the list
3. You'll be configuring rules in the **Security** and **Caching** sections

![Cloudflare Dashboard](/storage/kb-images/33c0a7bf10-inline.png)

---

### Step 2: Create Security Custom Rules

Navigate to **Security** → **Security rules**  and create a new custom rule.

#### Rule Configuration:

**Rule name:** `Allow FlowMattic Webhooks`

**Expression (Edit expression):**
```
(http.request.uri.path contains "/wp-json/webhook/capture/") or
(http.request.uri.path contains "/webhook/capture/")
```

**Action:** Select **Skip** and check the following options:

- ✅ All remaining custom rules
- ✅ Rate limiting rules
- ✅ User Agent Blocking
- ✅ Browser Integrity Check
- ✅ All managed rules (if using WAF managed rules)

![Security Security rules.png](/storage/kb-images/ab4a25cd74-inline.png)

Click **Deploy** to save the rule.

> **Important:** Make sure this rule is placed at the **top** of your rules list so it executes first.

---

### Step 3: Configure Bot Fight Mode Exception

If you have **Bot Fight Mode** or **Super Bot Fight Mode** enabled, you need to create an exception for webhook requests.

Navigate to **Security** → **Bots** and configure:

1. If using **Super Bot Fight Mode**, click **Configure**
2. Add the FlowMattic webhook paths to the skip list

Alternatively, create a **Configuration Rule**:

1. Go to **Rules** → **Configuration Rules**
2. Click **Create rule**
3. Set the expression:

```
(http.request.uri.path contains "/wp-json/webhook/capture/") or
(http.request.uri.path contains "/webhook/capture/")
```

4. Under **Bot Management**, select **Skip**

![Security Security rules jsonlint.me InfiWebs Pvt. Ltd. Cloudflare 2026-01-24 at 8.39.59 PM.png](/storage/kb-images/517907b71a-inline.png)

---

### Step 4: Create Cache Bypass Rules

Webhook endpoints should never be cached. Navigate to **Caching** → **Cache Rules** and create a new rule.

**Rule name:** `Bypass Cache for FlowMattic Webhooks`

**Expression:**
```
(http.request.uri.path contains "/wp-json/webhook/capture/") or
(http.request.uri.path contains "/webhook/capture/")
```

**Cache eligibility:** Select **Bypass cache**

![Caching Cache Rules.png](/storage/kb-images/c0a8fa82ea-inline.png)

Click **Deploy** to save.

---

### Step 5: Disable Under Attack Mode for Webhooks (Optional)

If you frequently use **Under Attack Mode**, create a rule to exclude webhook endpoints:

1. Go to **Rules** → **Configuration Rules**
2. Create a new rule with the same expression as above
3. Set **Security Level** to **Essentially Off** for these paths

---

## Alternative Method: Page Rules (Legacy)

If you prefer using Page Rules (legacy method), create rules for each pattern:

| URL Pattern | Settings |
|------------|----------|
| `*example.com/wp-json/webhook/capture/*` | Cache Level: Bypass, Security Level: Essentially Off, Browser Integrity Check: Off |
| `*example.com/webhook/capture/*` | Cache Level: Bypass, Security Level: Essentially Off, Browser Integrity Check: Off |

> **Note:** Replace `example.com` with your actual domain name.

![Page Rules.png](/storage/kb-images/a2a404dfa5-inline.png)

---

## Verifying Your Configuration

After setting up the rules, test your FlowMattic webhooks:

### Test Webhook Endpoint

1. Go to **FlowMattic** → **Workflows**
2. Open a workflow with a Webhook trigger
3. Copy the webhook URL
4. Use a tool like [Postman](https://www.postman.com/) or [Webhook.site](https://webhook.site/) to send a test POST request
5. Verify the workflow executes successfully

### Check Cloudflare Logs

1. Go to **Security** → **Events**
2. Filter by URI path containing `/webhook/capture/`
3. Verify requests are being **allowed** (not challenged or blocked)

---

## Troubleshooting

### Still Getting 403 Errors?

1. **Check rule order** - Ensure the Allow rule is at the top of the rules list
2. **Verify expression syntax** - Double-check the expressions match exactly
3. **Disable Bot Fight Mode temporarily** - Turn it off briefly to confirm it's the cause
4. **Check origin server** - Ensure your hosting server isn't also blocking requests

### Webhooks Timing Out?

1. **Check caching** - Ensure cache bypass is working
2. **Review firewall logs** - Look for blocked requests in Cloudflare events
3. **Test without Cloudflare** - Pause Cloudflare temporarily to isolate the issue

### Webhooks Working Intermittently?

1. **Rate limiting** - Ensure rate limiting rules are skipped for webhook endpoints
2. **Challenge actions** - Check if Cloudflare is presenting challenges to webhook requests
3. **Geographic restrictions** - Verify your security rules aren't blocking requests from certain regions

---

## Other Security Plugins

If you're using additional security plugins alongside Cloudflare, you may need to whitelist webhook endpoints in those as well:

### Wordfence

1. Go to **Wordfence** → **Firewall** → **All Firewall Options**
2. Scroll to **Whitelisted URLs**
3. Add:
   - `/wp-json/webhook/capture/`
   - `/webhook/capture/`

### Sucuri

1. Access your Sucuri dashboard
2. Navigate to **Firewall** → **Whitelist**
3. Add the webhook endpoint paths

### Jetpack

1. Go to **Jetpack** → **Settings** → **Security**
2. Configure brute force protection exceptions for webhook URLs

---

## Summary

To ensure FlowMattic webhooks work correctly with Cloudflare:

1. ✅ Create WAF custom rules to skip security checks for webhook endpoints
2. ✅ Configure Bot Fight Mode exceptions
3. ✅ Set up cache bypass rules
4. ✅ Test webhooks after configuration
5. ✅ Monitor Cloudflare events for any blocked requests

**Endpoints to whitelist:**
- `/wp-json/webhook/capture/*`
- `/webhook/capture/*`

By following these steps, your FlowMattic webhook automations will work seamlessly while maintaining security for the rest of your website.

---

*Last updated: January 2026*

---

# Why is FlowMattic Tables a paid add-on?

Source: https://support.flowmattic.com/kb/article/210/why-is-flowmattic-tables-a-paid-add-on

FlowMattic Tables is priced separately from your FlowMattic license, and the fairest way to explain that is simple: **your FlowMattic license pays for software; FlowMattic Tables pays for a service that runs continuously on our servers.**

This article explains what the subscription covers and answers the questions we hear most.

## The short version

Everything else in FlowMattic — workflows, integrations, WP Tables, the builders — is software that runs on **your** hosting. We build it, you run it, and a license covers that fairly.

FlowMattic Tables is different. When you subscribe, we provision a **private managed database for your site on our infrastructure** and keep it running around the clock:

- Storage for your records, **replicated and backed up** continuously
- Compute for every query your grid and workflows make
- **30-day point-in-time recovery**, scheduled exports, and monitoring
- Capacity planning, security patching, and upgrades — no servers for you to run

Those are real, recurring, per-site costs that exist **whether or not the plugin gets an update**. Bundling them into the plugin price would mean charging every FlowMattic user for infrastructure only some use. Keeping Tables as an opt-in add-on means you only pay for it if you actually use it — and the entry plan costs less than a coffee: **Starter is $5/month**.

## What you get for the money

| | Starter | Pro | Business |
|---|---|---|---|
| Price (monthly) | $5/mo | $15/mo | $39/mo |
| Price (annual) | $49/yr | $149/yr | $399/yr |
| Records | 100,000 | 500,000 | 2,000,000 |
| Writes per month | 250,000 | 2,000,000 | 10,000,000 |
| Reads | Unlimited | Unlimited | Unlimited |
| Exports | 1 per day | On demand | Nightly automatic + on demand |
| Recovery | 30-day point-in-time | 30-day point-in-time | Self-serve point-in-time restore |
| Tables / fields | 500 tables, 100 fields each | 500 tables, 100 fields each | 500 tables, 100 fields each |

Every plan includes the full feature set: all premium column types (Person, Tags, Attachments, Currency, Calculate, Relation, AI Text, and more), Summarize footers, saved Views, CSV import with automatic type detection, and every workflow action and trigger.

## Frequently asked questions

### I already paid for FlowMattic. Why do I have to pay again?

Your FlowMattic license covers the plugin — software that runs on your own hosting. FlowMattic Tables is a **hosted service**: your records live on our servers, in a database we provision, back up, monitor, and scale for your site every hour of every month. A one-time or flat plugin fee can't fund infrastructure that bills us continuously per site, so Tables is priced as what it is — a service — and only the people who use it pay for it.

### Can't I just store my data in WordPress for free?

You can, and FlowMattic ships **WP Tables free** for exactly that. It's a great fit for small datasets. FlowMattic Tables exists for the cases where that stops being a good idea: tens or hundreds of thousands of rows of automation data will bloat your WordPress database, slow your site's backups, and drag every page load through the same overloaded MySQL instance. A FlowMattic Table is **isolated from your site's database** — heavy workflow data stays off your hosting entirely — and comes with premium column types, Views, Summarize, and fault-tolerant CSV import that WP Tables doesn't have.

### What am I actually paying for each month?

Storage, replication, and backups for your records; compute for every read and write your site makes; 30-day point-in-time recovery; scheduled exports; and the monitoring and maintenance that keep it all running. None of that stops when the plugin sits idle — which is why it's a subscription rather than a one-time fee.

### What happens when I hit a plan limit?

We tell you — **we never bill you**. Limits on records and writes are hard caps with clear warnings in your dashboard as you approach them. There are no overage charges, ever, and reads are always unlimited on every plan. If you outgrow a cap, upgrading takes one click and applies immediately.

### What happens to my data if I cancel?

Nothing sudden. Your database is kept intact for **30 days** after cancellation — resubscribe in that window and everything is exactly as you left it. After the grace period we take a **final export and retain it for 90 days** before the database is removed, so even a lapsed subscription doesn't mean instant data loss. You can also download your own export (.sql or .csv) at any time while subscribed.

### Am I locked in?

No. Exports are yours to download whenever you want — Starter includes one export per day, Pro exports on demand, and Business adds an automatic nightly export on top of the same on-demand allowance. The export is standard SQL/CSV you can load anywhere.

### Do I need to create an account somewhere else or manage a server?

No. Everything happens inside your WordPress admin: pick a plan on the FlowMattic Tables page, complete checkout, and your database is provisioned in about a minute. Billing is managed from the same screen via the **Manage billing** button.

### Is my data private?

Yes. Each site gets its **own isolated database** — your data is never mixed with other customers' data, and it's only accessible with your site's own API credentials.

### How does this compare to Airtable or a separate database service?

Comparable hosted data tools start around $20–$24 per user per month. FlowMattic Tables starts at $5 per site per month, has no per-user pricing, and — unlike an external tool — is wired directly into your workflows: native insert/update/find/delete actions, row-change triggers, and typed fields with no API keys, no connectors, and no sync delays.

### Which plan should I start with?

Start with **Starter** ($5/mo) if you're trying Tables out or automating a modest dataset. Move to **Pro** when you pass 100k records or need on-demand exports. **Business** is for heavy pipelines — millions of writes a month, nightly automatic exports on top of on-demand, and self-serve restore. Switch the billing toggle to annual to save — two months free on Starter and Pro, $69 off Business.

---

# Workflow Error Handling & Failover Notifications in FlowMattic

Source: https://support.flowmattic.com/kb/article/152/workflow-error-handling-failover-notifications-in-flowmattic

**Never miss a workflow failure again — even when your email provider is down.**

FlowMattic's error handling system gives you multiple independent notification channels so you're always informed when something goes wrong. Whether it's a rate-limited API, a failed webhook, or a crashed workflow — you'll know about it instantly via Slack, Discord, Teams, Pushover, PagerDuty, or any webhook-compatible service.


## The Problem: Why Email-Only Notifications Aren't Enough

Previously, FlowMattic could only notify you of workflow failures via email. This created a critical blind spot: if your SMTP provider was down, rate-limited, or misconfigured, the error notification email itself would fail — silently. You wouldn't know something went wrong until a client complained days later.

This is especially common for high-volume users who process thousands of FlowMattic transactions per day. During peak periods, email providers like Microsoft 365 and Google Workspace enforce rate limits, which can block both your workflow emails and the failure notification emails.

The error handling system solves this by providing **four independent notification channels** that work simultaneously:

1. **Email notifications** (existing)
2. **"Workflow Failed" trigger** (build any notification workflow)
3. **API-level error webhook** (per-step webhook forwarding)
4. **Global error webhook** (site-wide webhook for all failures)

If one channel goes down, the others still deliver.

---

## Overview of the Error Handling System

![ChatGPT Image Mar 24, 2026, 05_08_08 PM.png](https://assets.infidesk.support/products/flowmattic/kb-images/wf-error-handling-01-chatgpt-image-mar-24-2026-05-08-08-pm.png)

| Channel | Scope | Best For |
|---|---|---|
| **Email Notifications** | Site-wide | Traditional email alerts |
| **Workflow Failed Trigger** | Site-wide | Building custom notification workflows with full control |
| **API Error Webhook URL** | Per API step | Monitoring specific API integrations |
| **Global Error Webhook URL** | Site-wide | Quick site-wide webhook setup without building workflows |

---

## Feature 1: The "Workflow Failed" Trigger

The **Workflow Failed** trigger is a new FlowMattic trigger application that fires automatically whenever any workflow on your site encounters an error. It gives you the full power of the FlowMattic workflow builder to decide how, where, and when error notifications are sent.

### How It Works

1. A workflow fails during execution (e.g., an API returns a 500 error, a webhook is unreachable, or a rate limit is hit after retries).
2. FlowMattic collects all error details — workflow name, failed steps, error messages, timestamps, and more.
3. Every active workflow that uses the **Workflow Failed** trigger is executed with the full error payload.
4. Your error-handling workflow sends notifications to Slack, Discord, Teams, Pushover, SMS, or anywhere else.

This means your error notifications are **not dependent on email at all**. If SMTP is down, your Slack/Discord/webhook notifications still fire.

### Setting Up a Workflow Error Handler

**Step 1:** Create a new workflow in FlowMattic.

**Step 2:** Select **Workflow Error by FlowMattic** as the trigger application.

![Workflow Builder - workflow error trigger](https://assets.infidesk.support/products/flowmattic/kb-images/wf-error-handling-02-workflow-builder-workflow-error-trigger.png)

**Step 3:** Select the **Workflow Failed** trigger event.

**Step 4:** Click **Capture** to load sample data. FlowMattic provides realistic sample data immediately so you can see all available fields and build your workflow without waiting for an actual failure.

![workflow failed trigger capture response sample.png](https://assets.infidesk.support/products/flowmattic/kb-images/wf-error-handling-03-workflow-failed-trigger-capture-response-sample.png)

**Step 5:** Add your notification action step. For example:

- **Webhook Outgoing** — Send a JSON POST to Slack, Discord, or any webhook URL
- **API by FlowMattic** — Call any REST API (PagerDuty, Opsgenie, Twilio SMS, etc.)
- **Any FlowMattic integration** — Use Gmail, SendGrid, Telegram, or any connected app as a fallback

**Step 6:** Use dynamic tags from the trigger data to compose your notification message. For example:

```
Workflow "{workflow_error1.workflow_name}" failed at {workflow_error1.timestamp}.
Error: {workflow_error1.first_error_message}
Step: {workflow_error1.first_error_step} ({workflow_error1.first_error_app})
View: {workflow_error1.workflow_url}
```

**Step 7:** Turn on the workflow and save.

![Workflow Builder - send workflow failure notification to slack](https://assets.infidesk.support/products/flowmattic/kb-images/wf-error-handling-04-workflow-builder-send-workflow-failure-notification-to-slack.png)

### Available Data Fields

When the **Workflow Failed** trigger fires, the following data fields are available as dynamic tags:

| Field | Dynamic Tag | Description |
|---|---|---|
| Workflow ID | `{workflow_error1.workflow_id}` | The ID of the failed workflow |
| Workflow Name | `{workflow_error1.workflow_name}` | Human-readable name of the workflow |
| Workflow URL | `{workflow_error1.workflow_url}` | Direct admin link to the failed workflow |
| Error Message | `{workflow_error1.error_message}` | Human-readable summary (e.g., `api: Rate limit error (HTTP 429)`) |
| First Error App | `{workflow_error1.first_error_app}` | Application that caused the first error (e.g., `api`, `webhook_outgoing`) |
| First Error Step | `{workflow_error1.first_error_step}` | Step title where the first error occurred |
| First Error Message | `{workflow_error1.first_error_message}` | Detailed error message from the first failed step |
| First Error Code | `{workflow_error1.first_error_code}` | HTTP status code (e.g., `429`, `500`, `403`) |
| First Error Type | `{workflow_error1.first_error_type}` | Error classification (`rate_limit`, `http_error`, `empty_response`) |
| Failed Steps (JSON) | `{workflow_error1.failed_steps}` | Full JSON array of all failed steps with complete error details |
| Task History ID | `{workflow_error1.task_history_id}` | ID to look up the full execution log in Task History |
| Site URL | `{workflow_error1.site_url}` | Your WordPress site URL |
| Site Name | `{workflow_error1.site_name}` | Your WordPress site name |
| Timestamp | `{workflow_error1.timestamp}` | When the error occurred (Y-m-d H:i:s format) |
| Error Severity | `{workflow_error1.error_severity}` | Severity level (`critical` or `warning`) |
| Total Steps | `{workflow_error1.total_steps}` | Total number of steps in the failed workflow |
| Failed Step Count | `{workflow_error1.failed_step_count}` | Number of steps that failed |

> **Tip:** For most notification use cases, the `first_error_*` fields give you everything you need without parsing JSON. Use `failed_steps` only if you need the full details of every failed step in multi-step failures.

### Monitoring a Specific Workflow

By default, the Workflow Failed trigger fires for **all** workflow failures on your site. If you want to monitor only a specific workflow, enter its Workflow ID in the **Monitor Specific Workflow** field.

![workflow failed trigger- execute specific workflow only.png](https://assets.infidesk.support/products/flowmattic/kb-images/wf-error-handling-05-workflow-failed-trigger-execute-specific-workflow-only.png)

You can find a workflow's ID in the URL when editing it: `workflow-id=YOUR_ID_HERE`.

This is useful when you want different notification channels for different workflows — for example, sending critical payment workflow failures to PagerDuty while sending non-critical failures to a Slack channel.

### Infinite Loop Protection

FlowMattic includes built-in protection against infinite error loops:

1. **Self-triggering prevention:** An error workflow will never trigger itself.
2. **Cascade prevention:** If an error-handling workflow fails, it will **not** trigger other error-handling workflows. This prevents A → B → A infinite chains.

This means your error-handling workflows are safe to deploy without worrying about runaway loops.

---

## Feature 2: API Module Error Webhook Forwarding

The API module now includes an **Error Webhook URL** field that forwards API errors directly to any webhook-compatible service. This is a per-step setting — you can configure different webhook URLs for different API steps.

### Configuring the Error Webhook URL

**Step 1:** Open any API step in your workflow.

**Step 2:** Scroll down to the **Error Handling** section.

**Step 3:** Enter your webhook URL in the **Error Webhook URL** field.

![FlowMattic error handling - api module error webhook.png](https://assets.infidesk.support/products/flowmattic/kb-images/wf-error-handling-06-flowmattic-error-handling-api-module-error-webhook.png)

This works **independently** of the email notification settings. You can use both, either, or neither.

### What Gets Sent to the Webhook

When an API error occurs, FlowMattic sends a JSON POST request to your webhook URL with the following payload:

```json
{
  "event": "api_error",
  "workflow_id": "abc123",
  "workflow_name": "My API Workflow",
  "workflow_url": "https://yoursite.com/wp-admin/admin.php?page=...",
  "error_type": "rate_limit",
  "error_message": "Rate limit error. Failed after 3 retries.",
  "response_code": 429,
  "api_endpoint": "https://api.example.com/data",
  "http_method": "POST",
  "raw_response": "{ \"error\": \"too many requests\" }",
  "site_url": "https://yoursite.com",
  "site_name": "My Website",
  "timestamp": "2026-03-24 14:30:00",
  "retry_count": 3
}
```

The request includes these headers:

- `Content-Type: application/json`
- `User-Agent: FlowMattic/{version}`
- `X-FlowMattic-Event: api_error`

### Rate Limit Handling

When an API returns an HTTP 429 (Too Many Requests) response, FlowMattic automatically:

1. **Reads the `Retry-After` header** from the API response. If present, FlowMattic waits the specified duration (capped at 60 seconds) before retrying.
2. **Retries up to 3 times** with the appropriate delay between each attempt.
3. **After 3 failed retries**, triggers the error handling chain:
   - Sends an error notification email (if configured)
   - Forwards the error to the Error Webhook URL (if configured)
   - Returns a detailed error response to the workflow

The error response in your task history will clearly show what happened:

```json
{
  "status": "error",
  "error_type": "rate_limit",
  "response_code": 429,
  "message": "Rate limit error (HTTP 429). API returned Too Many Requests. FlowMattic retried 3 times with 30-second intervals before giving up.",
  "retry_attempts": 3,
  "retry_interval": "30 seconds between each retry",
  "error_handling": "Error email sent to admin@example.com | Error forwarded to webhook: https://hooks.slack.com/..."
}
```

> **Note:** Rate limit retries apply to all HTTP methods — GET, POST, PUT, PATCH, and DELETE.

---

## Feature 3: Global Error Webhook URL

The **Global Error Webhook URL** is a site-wide setting that sends all workflow failure notifications to a single webhook endpoint. It's the fastest way to set up webhook-based error alerting without building a separate workflow.

### Setting Up the Global Webhook

**Step 1:** Go to **FlowMattic → Settings**.

**Step 2:** Scroll to the **Failed Task Notifications** section.

**Step 3:** Enter your webhook URL in the **Error Webhook URL** field.

![FlowMattic settings webhook url.png](https://assets.infidesk.support/products/flowmattic/kb-images/wf-error-handling-07-flowmattic-settings-webhook-url.png)

**Step 4:** Click **Save Settings**.

That's it. Every workflow failure on your site will now send a JSON POST to your webhook URL with the full error payload — the same data available in the Workflow Failed trigger.

The global webhook fires as a **non-blocking request**, meaning it won't slow down your workflow execution.

---

## How All Three Channels Work Together

Here's what happens when a workflow fails:

```
Workflow Fails
    │
    ├─→ Email Notification (if enabled in Settings)
    │       └─ Depends on SMTP — may fail if email provider is down
    │
    ├─→ Global Error Webhook (if URL configured in Settings)
    │       └─ Non-blocking HTTP POST — independent of email
    │
    ├─→ "Workflow Failed" Trigger (fires all error-handling workflows)
    │       └─ Can send to Slack, Discord, Teams, SMS, or anything
    │
    └─→ API Error Webhook (if URL configured on the failed API step)
            └─ Fires for API-specific errors including rate limits
```

All four channels fire **independently and simultaneously**. If your SMTP provider is rate-limited, your Slack webhook still fires. If your Slack webhook is down, your Discord workflow still runs. There is no single point of failure.

---

## Practical Examples

### Send Workflow Errors to Slack

**Using the Workflow Failed trigger:**

1. Create a new workflow with the **Workflow Error** trigger.
2. Add a **Webhook Outgoing** step.
3. Set the webhook URL to your Slack Incoming Webhook URL.
4. Configure the parameters:

| Key | Value |
|---|---|
| `text` | `Workflow "{workflow_error1.workflow_name}" failed at {workflow_error1.timestamp}. Error: {workflow_error1.first_error_message} (Code: {workflow_error1.first_error_code}). View: {workflow_error1.workflow_url}` |


### Send Workflow Errors to Discord

1. Create a new workflow with the **Workflow Error** trigger.
2. Add a **Webhook Outgoing** step.
3. Set the webhook URL to your Discord channel's webhook URL.
4. Configure the parameters:

| Key | Value |
|---|---|
| `content` | `**Workflow Failed:** {workflow_error1.workflow_name}\n**Error:** {workflow_error1.first_error_message}\n**Step:** {workflow_error1.first_error_step}\n**Time:** {workflow_error1.timestamp}\n**Link:** {workflow_error1.workflow_url}` |

### Forward API Errors to PagerDuty

For critical API integrations (e.g., payment processing), you can forward errors directly from the API step to PagerDuty:

1. Open your critical API step.
2. In the **Error Webhook URL** field, enter your PagerDuty Events API v2 endpoint.
3. PagerDuty will receive a JSON payload with full error details including the API endpoint, response code, and error type.

---

## Testing Your Error Handlers

You can test your error handling setup using free public API endpoints that return specific error codes:

| Test URL | What It Does |
|---|---|
| `https://httpbin.org/status/429` | Returns 429 — triggers rate limit retries, then fires error handlers |
| `https://httpbin.org/status/500` | Returns 500 — triggers immediate workflow failure |
| `https://httpbin.org/status/403` | Returns 403 — triggers HTTP error handling |
| `https://httpbin.org/delay/120` | Times out after 60s — triggers timeout error |

**To see your webhook payloads**, use a free webhook inspection tool like [webhook.site](https://webhook.site). Copy your unique URL and paste it as the Error Webhook URL to see exactly what data FlowMattic sends.

**Recommended test flow:**

1. Get a unique URL from webhook.site.
2. Create a test workflow with an API step pointing to `https://httpbin.org/status/429`.
3. Paste the webhook.site URL in the API step's **Error Webhook URL** field.
4. Run the workflow and check webhook.site for the JSON payload.
5. Set up a **Workflow Failed** trigger workflow pointing to webhook.site to verify the trigger fires too.

---

## Frequently Asked Questions

#### Does the Workflow Failed trigger fire for API rate limit errors?

**Yes.** When an API step hits a rate limit (HTTP 429), FlowMattic retries 3 times. If all retries fail, the step is marked as failed, which triggers the Workflow Failed trigger along with all other configured notification channels.

#### Can I use the Workflow Failed trigger to send notifications to multiple channels?

**Yes.** Your error-handling workflow can have as many action steps as you need. Send to Slack, Discord, and SMS all from the same workflow. You can also create multiple error-handling workflows — all of them will fire when any workflow fails.

#### Will my error-handling workflow cause an infinite loop if it fails?

**No.** FlowMattic has built-in infinite loop protection. Error-handling workflows tag their payloads so that if they themselves fail, they will not re-trigger other error-handling workflows. Self-triggering is also prevented.

#### Can I monitor only specific workflows?

**Yes.** In the Workflow Failed trigger setup, enter a specific workflow ID in the **Monitor Specific Workflow** field. The trigger will only fire for that workflow's failures. Leave it empty to monitor all workflows.

#### Does the Error Webhook URL work during the "Test Action" in the workflow builder?

**Yes.** When you test an API step that fails, the error webhook fires just like it would during live execution. The test response also shows detailed information about what error handling actions were taken.

#### What's the difference between the Global Error Webhook and the Workflow Failed trigger?

The **Global Error Webhook** is a simple, fire-and-forget HTTP POST to a single URL. It requires no workflow setup — just paste a URL in Settings. The **Workflow Failed trigger** is more powerful — it lets you build complete workflows with conditional logic, multiple notification channels, data transformation, and routing. Use the global webhook for quick setup; use the trigger for advanced scenarios.

#### Are the webhook requests blocking?

**No.** Both the global error webhook and the API-level error webhook use non-blocking HTTP requests. They will not slow down your workflow execution or delay the error response.

---

# Workflow Folder Management

Source: https://support.flowmattic.com/kb/article/116/workflow-folder-management

Learn how to organise your workflows using FlowMattic's folder system. Create folders, assign workflows, and keep your automation workspace tidy as your workflow library grows.

## Overview

FlowMattic's folder management helps you organise workflows into logical groups. Whether you're managing 10 workflows or 100, folders make it easy to find, filter, and manage your automations.

You can manage folders from three locations:
1. **Workflows page** - Centralized folder dashboard and bulk operations
2. **Individual workflow settings** - Assign workflows to folders while building
3. **FlowMattic Settings** - Set your default folder for new workflows

## Managing Folders from the Workflows Page

The workflows page provides a centralized dashboard for managing all your folders and bulk-assigning workflows.

### Opening the Folder Manager

1. Navigate to **FlowMattic → Workflows**
2. Click the **Folders** button at the top of the page
3. The Folder Manager modal will open, showing all your existing folders

The Folder Manager displays:
- Folder names
- Number of workflows in each folder
- Creation date
- Action buttons (Rename, Delete)

### Creating a New Folder

To create a new folder from the Folder Manager:

1. Click the **Create New Folder** button in the Folder Manager modal
2. Enter a descriptive folder name (e.g., "WooCommerce Automations", "Lead Generation", "Email Campaigns")
3. Click **Create**
4. Your new folder appears in the list immediately

**Tip:** Use clear, descriptive folder names that reflect the purpose or category of workflows they contain.

### Renaming a Folder

To rename an existing folder:

1. Open the Folder Manager
2. Find the folder you want to rename
3. Click the **Rename** button next to the folder name
4. Enter the new folder name
5. Click **Save**

All workflows in this folder will remain assigned—only the folder name changes.

### Deleting a Folder

To delete a folder:

1. Open the Folder Manager
2. Find the folder you want to delete
3. Click the **Delete** button
4. Confirm the deletion when prompted

**Important:** When you delete a folder, workflows inside it are automatically moved to the "Default" folder. The workflows themselves are not deleted.

### Bulk Moving Workflows to Folders

To move multiple workflows to a folder at once:

1. On the Workflows page, select the checkboxes next to the workflows you want to move
2. Click the **Bulk Actions** dropdown at the top
3. Select **Move to Folder**
4. Choose the destination folder from the list
5. Click **Move**

A progress indicator shows you how many workflows are being moved. You'll see a success message when the operation completes.

**Tip:** Use bulk move when reorganising your workspace or setting up new folder structures.

### Filtering Workflows by Folder

To view workflows from a specific folder:

1. On the Workflows page, locate the **Folders** column and click it
2. Select the folder name you want to view
3. The workflow list updates to show only workflows in that folder

The filter displays the folder name and the number of workflows it contains. Select "All Folders" to view all workflows again.

### Viewing Workflow's Current Folder

Each workflow displays its folder assignment in the workflow list:

- Look for the folder name badge next to the workflow name
- The "Default" folder is shown for workflows not assigned to any custom folder
- This helps you quickly identify where workflows are organised

## Managing Folders from Individual Workflow Settings

You can assign workflows to folders while building or editing them.

### Assigning a Workflow to a Folder

When creating or editing a workflow:

1. Open the workflow in the workflow builder
2. Go to the **Settings** tab in the right sidebar
3. Find the **Add to Folder...** field
4. Click the folder icon to see the list of available folders
5. Select the folder you want to assign this workflow to

The workflow is immediately assigned to the selected folder.

### Creating a New Folder from Workflow Settings

You can create new folders without leaving the workflow builder:

1. In the workflow settings, find the **Add to Folder...** field
2. Click the **New** button (with the + icon)
3. Enter the folder name in the modal
4. Click **Create**
5. The workflow is automatically assigned to the new folder

This is useful when you're building workflows and realise you need a new category.

### Refreshing the Folders List

If you've created or modified folders in another browser tab or window:

1. In the workflow settings, find the **Add to Folder...** field
2. Click the **Refresh** icon (circular arrow)
3. The folder list updates with the latest folders

This ensures you're always seeing the most current folder structure.

### Changing a Workflow's Folder

To move a workflow to a different folder:

1. Open the workflow in the workflow builder
2. Open the settings panel by clicking on the gear icon from the left side menu panel
3. Click the folder icon next to **Add to Folder...**
4. Select the new folder from the list
5. The workflow moves to the new folder immediately when you click **Save Workflow** button

## Setting a Default Folder for New Workflows

You can configure which folder new workflows are automatically assigned to.

### Configuring the Default Folder

1. Navigate to **FlowMattic → Settings**
2. Locate the **Workflow Builder Settings** setting section
3. Look for the **Default Folder** setting
4. Select the folder you want to use as the default from the dropdown
5. Click **Save Settings**

From now on, all new workflows you create will automatically be assigned to this folder.

**Use case:** If most of your new workflows belong to a specific category (e.g., "Client Projects"), set that as the default to save time during workflow creation.

### Resetting to Default

To use the built-in "Default" folder for new workflows:

1. Go to **FlowMattic → Settings**
2. Set the **Default Folder** dropdown to "Default"
3. Save your settings

New workflows will now use the standard Default folder.

## Best Practises for Folder Organisation

Here are some tips for keeping your workflows organised:

### Organise by Purpose
Create folders based on what the workflows do:
- Customer Communication
- Order Processing
- Lead Generation
- Reporting & Analytics
- Data Synchronisation

### Organise by Integration
Group workflows by the main service they integrate with:
- WooCommerce Automations
- CRM Workflows
- Email Marketing
- Payment Processing

### Organise by Client or Project
If you manage workflows for multiple clients or projects:
- Client A - E-commerce
- Client B - Membership Site
- Internal Workflows
- Testing & Development

### Regular Maintenance
- Review your folders monthly as your workflow library grows
- Consolidate similar folders by bulk-moving workflows and deleting empty folders
- Delete empty or unused folders
- Move test workflows to a dedicated "Testing" folder

### Start Simple
- Don't create too many folders initially
- Begin with 3-5 broad categories
- Add more specific folders as needed
- Use the bulk move feature when reorganising

## Common Questions

**Q: Can a workflow belong to multiple folders?**
A: No, each workflow can only belong to one folder at a time.

**Q: What happens to workflows when I delete a folder?**
A: Workflows are automatically moved to the "Default" folder. The workflows themselves are not deleted.

**Q: Can I rename the "Default" folder?**
A: No, the "Default" folder is a system folder and cannot be renamed or deleted.

**Q: Is there a limit to how many folders I can create?**
A: No, you can create as many folders as needed to organise your workflows.

**Q: Do folders affect workflow execution?**
A: No, folders are purely for organisation. They don't impact how workflows run or their performance.

**Q: Can I export/import folder structures?**
A: Currently, folder assignments are stored in your WordPress database. When you export workflows, their folder assignments are preserved.

**Q: Will folder filtering affect workflow execution?**
A: No, filtering only changes what you see in the admin interface. All workflows continue to run normally regardless of folder filters.

## Troubleshooting

### Folder not appearing in the list

If you create a folder but don't see it:
1. Click the **Refresh** icon next to the folder dropdown
2. Close and reopen the Folder Manager modal
3. Refresh your browser page

### Can't delete a folder

If the delete button isn't working:
1. Ensure the folder doesn't contain workflows (move them out first, or use the bulk move feature)
2. You cannot delete the "Default" system folder
3. Check that you have proper admin permissions

### Workflows not showing in folder filter

If workflows don't appear when filtering by folder:
1. Verify the workflows are actually assigned to that folder
2. Check if any other filters are active (status, search terms)
3. Refresh the page and try again

### Bulk move operation not completing

If bulk move stops or fails:
1. Check your internet connection
2. Try moving fewer workflows at once
3. Refresh the page and try again
4. Check the browser console for any error messages

## Summary

FlowMattic's folder management system helps you keep workflows organised as your automation library grows. With centralised folder management, bulk operations, and flexible assignment options, you can structure your workspace exactly how you need it.

Start with a few broad categories, use the bulk move feature to reorganise existing workflows, and set a default folder if most of your new workflows belong to one category. Regular maintenance keeps your workspace clean and efficient.

---

# Workflow stops executing after a certain number of steps

Source: https://support.flowmattic.com/kb/article/48/workflow-stops-executing-after-a-certain-number-of-steps

#### Overview

FlowMattic workflows are designed to run indefinitely, but there might be instances where workflows stop executing after a certain number of steps. Here are a few common reasons that may cause this behaviour:

1. **Action Step Error**: An error in an action step can halt the workflow.
2. **Filter Module Condition Not Met**: If a filter condition is not satisfied, the workflow will stop executing further steps.
3. **PHP Memory or Execution Time Limits**: Reaching the PHP memory limit or execution time limit can stop the workflow.
4. **PHP Max Input Vars Limit**: Exceeding the PHP max input vars limit can also interrupt the workflow.

#### Steps to Troubleshoot Workflow Stoppage

##### 1. Check the Debug Log
To identify errors or warnings causing the workflow to stop, enable debugging in your WordPress installation:

1. Edit your `wp-config.php` file.
2. Add the following lines of code:

   ```php
   define( 'WP_DEBUG', true );
   define( 'WP_DEBUG_LOG', true );
   define( 'WP_DEBUG_DISPLAY', false );
   ```

3. This will create a `debug.log` file in the `wp-content` directory, where you can review errors and warnings.

##### 2. Verify Filter Module Conditions
If you're using a Filter module, ensure that the filter conditions are correctly set and being met. If not, adjust the conditions to align with your workflow requirements.

##### 3. Increase PHP Memory and Execution Time Limits
If the workflow stops due to memory or execution time constraints, update your `php.ini` file with the following recommended values:

```ini
memory_limit = 512M
max_execution_time = 300
```


##### 4. Increase PHP Max Input Vars Limit
If the max input vars limit is causing the issue, modify your `php.ini` file to increase the limit. Recommended value:

```ini
max_input_vars = 5000
```

 
 :::Info
Note: These values are recommendations only, and not requirements. Adjust them based on your server configuration and specific workflow needs.
 :::

#### Additional Tips
- After making changes to the `php.ini` file, restart your web server to apply the new settings.
- Consult your hosting provider if you're unable to modify server configurations directly.

#### Further Assistance
If the above steps do not resolve the issue, contact FlowMattic support for expert assistance. Provide them with relevant details, including the debug log and any specific configurations in your workflow.

By following these steps, you can effectively troubleshoot and resolve issues causing your workflow to stop after several steps.

---

# XML Parser

Source: https://support.flowmattic.com/kb/article/41/xml-parser

FlowMattic’s XML Parser is an essential tool designed to streamline data integration and processing in your workflows. It allows users to parse XML files or URLs and convert them into JSON format for further utilization. This capability is especially useful for automating data transformations, enabling seamless compatibility with a variety of tools and systems. With FlowMattic’s XML Parser, you can simplify complex data operations and focus on your workflow’s core objectives.

By using the XML Parser, you eliminate the need for manual handling of XML data, reducing errors and saving time. Whether you're integrating data from an external API, processing content for reporting, or automating tasks that require structured data, this feature empowers you to automate efficiently an

#### Here is a step-by-step guide to help you set up your XML Parser with FlowMattic

### Step 1: Create a New Workflow

Go to the FlowMattic Dashboard, where you can manage and create workflows. To start a new workflow, click the “New Workflow” button located in the top-right corner of the Dashboard. This will begin the process of creating your new workflow.

### Step 2: Add the XML Parser as an Action Step

- Click the “+” icon in your workflow to add a new action step.

- In the search bar that appears, type “XML Parser” and select it from the list of available actions. This will add the XML Parser to your workflow, allowing you to proceed with its configuration.

### Step 3: Choose the Action Event

- Once the XML Parser is added, you’ll need to specify the action event.Select the action event “Parse XML File,” which is designed to convert an XML file or its URL into JSON format. This transformation is crucial for making the data usable in subsequent workflow steps.

### Step 4: Configure the Settings

- Provide the publicly accessible URL of the XML file you want to parse. Ensure that the URL is accurate and accessible, as the parser will retrieve the XML data directly from this location.

- After entering the URL, proceed to test the action step to ensure that the data is parsed correctly. This step validates that the XML file is being read and converted as intended.

### Step 5: Test and Save Your Workflow

- Run a test to ensure the XML Parser is functioning as expected. This will help you confirm that the XML data is being converted to JSON format and is ready for use in the next steps of your workflow.

- Once the test is successful, save your workflow. You can now integrate the parsed data into other actions or processes within the same workflow, creating a seamless automation chain.

---

# ZIP Archive Integration in FlowMattic

Source: https://support.flowmattic.com/kb/article/131/zip-archive-integration-in-flowmattic

The ZIP Archive app is a built-in FlowMattic application that lets you create, extract, inspect, and modify ZIP archives from file URLs — with automatic WordPress Media Library integration. No external connection or API key is required.

---

## Overview

The ZIP Archive app enables you to bundle files into ZIP archives, extract contents from existing archives, inspect archive contents, and add or remove files — all within your automated workflows. Created and extracted files are automatically uploaded to the WordPress Media Library.

---

## Connection Setup

The ZIP Archive is a **core utility app** — no connection setup is needed.

- No API key required
- No external service to configure
- Available immediately in all FlowMattic installations
- Requires PHP's `ZipArchive` extension (included in PHP 5.3+)

Simply select **ZIP Archive** when adding an action step to your workflow.

---

## Available Actions

The ZIP Archive app provides **5 actions** for working with ZIP files.

![zip archive integration actions.png](/storage/kb-images/9cc43ff4b2-inline.png)

### 1. Create ZIP Archive

Create a new ZIP archive from file URLs and save it to the WordPress Media Library.

**Configuration:**

| Field | Required | Description |
|-------|----------|-------------|
| File URLs | Yes | File URLs to include. Accepts comma-separated URLs, JSON array of strings, or JSON array of objects with a `url` key. |
| Archive Name | Yes | Name for the ZIP file. The `.zip` extension is added automatically if not provided. |
| Base Folder | No | Optional folder name inside the ZIP to place all files into. Leave empty to add files to the root. |

**Supported Input Formats for File URLs:**

```
# Comma-separated
https://example.com/file1.pdf, https://example.com/file2.jpg

# JSON array of strings
["https://example.com/file1.pdf", "https://example.com/file2.jpg"]

# JSON array of objects
[{"url": "https://example.com/file1.pdf"}, {"url": "https://example.com/file2.jpg"}]
```

**Output:**

| Field | Description |
|-------|-------------|
| `status` | `success` or `error` |
| `media_id` | WordPress Media Library attachment ID |
| `media_url` | URL to the created ZIP file |
| `file_name` | Name of the ZIP file |
| `file_count` | Number of files in the archive |
| `file_size` | Human-readable file size (e.g., "2.5 MB") |
| `file_size_bytes` | File size in bytes |
| `files_added` | Array of file names added to the archive |
| `failed_files` | Array of files that failed to download (with error details) |

![create zip archive action.png](/storage/kb-images/7a1fde1ef9-inline.png)

> **Tip:** Use the **PHP Array > Convert to List** action to generate a comma-separated URL list from an array of file URLs.

---

### 2. Extract ZIP Archive

Extract files from a ZIP archive and save them to the WordPress Media Library.

**Configuration:**

| Field | Required | Description |
|-------|----------|-------------|
| ZIP File URL | Yes | URL of the ZIP file to extract. |
| Password | No | Password if the ZIP is password-protected. Leave empty for unprotected archives. |

**Output:**

| Field | Description |
|-------|-------------|
| `status` | `success` or `error` |
| `total_files` | Number of files extracted |
| `extracted_files` | Array of extracted files with `file_name`, `relative_path`, `media_id`, and `media_url` |

Each extracted file contains:

| Field | Description |
|-------|-------------|
| `file_name` | Name of the extracted file |
| `relative_path` | Original path inside the ZIP archive |
| `media_id` | WordPress Media Library attachment ID |
| `media_url` | URL to the extracted file |
| `error` | Error message if extraction failed for this file |

![extract zip archive.png](/storage/kb-images/87c8c1793a-inline.png)

> **Note:** Extracted files are automatically uploaded to the WordPress Media Library. File types must comply with WordPress upload settings.

---

### 3. List ZIP Contents

Inspect all files and folders inside a ZIP archive without extracting it.

**Configuration:**

| Field | Required | Description |
|-------|----------|-------------|
| ZIP File URL | Yes | URL of the ZIP file to inspect. |

**Output:**

| Field | Description |
|-------|-------------|
| `status` | `success` or `error` |
| `total_entries` | Number of entries in the archive |
| `total_size` | Total uncompressed size (human-readable) |
| `total_size_bytes` | Total uncompressed size in bytes |
| `total_compressed_size` | Total compressed size (human-readable) |
| `total_compressed_size_bytes` | Total compressed size in bytes |
| `compression_ratio` | Compression percentage (e.g., "21.0%") |
| `files` | Array of file/folder entries |

Each entry in the `files` array contains:

| Field | Description |
|-------|-------------|
| `name` | File or folder path |
| `size` | Uncompressed size (human-readable) |
| `size_bytes` | Uncompressed size in bytes |
| `compressed_size` | Compressed size (human-readable) |
| `compressed_size_bytes` | Compressed size in bytes |
| `modified` | Last modification timestamp |
| `is_directory` | `true` for directories, `false` for files |

> **Use Case:** Inspect archive contents before extracting, or use the file paths from this action with the "Remove Files from ZIP" action.

---

### 4. Add Files to ZIP

Add new files to an existing ZIP archive.

**Configuration:**

| Field | Required | Description |
|-------|----------|-------------|
| ZIP File URL | Yes | URL of the existing ZIP archive. |
| File URLs to Add | Yes | File URLs to add. Same formats as Create ZIP Archive. |
| Base Folder | No | Optional folder name inside the ZIP to place the new files into. |

**Output:**

| Field | Description |
|-------|-------------|
| `status` | `success` or `error` |
| `media_id` | WordPress Media Library attachment ID |
| `media_url` | URL to the updated ZIP file |
| `file_name` | Name of the ZIP file |
| `total_files` | Updated total file count |
| `files_added` | Array of file names that were added |
| `failed_files` | Array of files that failed to download |

> **Note:** The existing archive contents are preserved — new files are appended to the archive.

---

### 5. Remove Files from ZIP

Remove specific files from an existing ZIP archive.

**Configuration:**

| Field | Required | Description |
|-------|----------|-------------|
| ZIP File URL | Yes | URL of the ZIP archive. |
| File Names to Remove | Yes | Comma-separated list of file paths to remove. Use exact paths as shown in the List ZIP Contents action. |

**Output:**

| Field | Description |
|-------|-------------|
| `status` | `success` or `error` |
| `media_id` | WordPress Media Library attachment ID |
| `media_url` | URL to the updated ZIP file |
| `file_name` | Name of the ZIP file |
| `total_files` | Updated total file count |
| `files_removed` | Array of file paths that were removed |
| `not_found` | Array of file paths that were not found in the archive |

**Example:**

If **List ZIP Contents** shows these files:
```
documents/report.pdf
images/photo.jpg
readme.txt
```

Then **File Names to Remove** should be:
```
documents/report.pdf, images/photo.jpg
```

> **Important:** File paths are case-sensitive and must match exactly as shown in the List ZIP Contents output, including any folder paths.

---

## Workflow Examples

### Example 1: Bundle Reports into a ZIP

Generate multiple files and bundle them into a single downloadable archive.

1. **HTTP Request** — Generate or fetch report files.
2. **ZIP Archive > Create ZIP Archive** — Bundle all file URLs into `monthly-report.zip`.
3. **Email** — Send the ZIP download link to the recipient.

### Example 2: Extract and Process Uploaded Files

Extract files from a ZIP uploaded by a user and process each file individually.

1. **Webhook Trigger** — Receive a ZIP file URL.
2. **ZIP Archive > Extract ZIP Archive** — Extract all files to Media Library.
3. **Iterator** — Loop through `{ZIPArchive1.extracted_files}`.
4. *(Process each file — rename, move, send, etc.)*

### Example 3: Archive Management

Inspect an archive, remove outdated files, and add new ones.

1. **ZIP Archive > List ZIP Contents** — Inspect `archive.zip`.
2. **ZIP Archive > Remove Files from ZIP** — Remove `old-report.pdf`.
3. **ZIP Archive > Add Files to ZIP** — Add `new-report.pdf`.
4. **Slack** — Notify team that the archive has been updated.

### Example 4: Password-Protected Archive Extraction

Extract files from a password-protected ZIP received via webhook.

1. **Webhook Trigger** — Receive ZIP URL and password.
2. **ZIP Archive > Extract ZIP Archive** — Extract using `{Trigger1.password}`.
3. **Email** — Send extracted file URLs to the admin.

---

## File Storage

- **Created ZIP files** and **extracted files** are saved to the WordPress Media Library.
- Physical location: `wp-content/uploads/{YYYY/MM}/`
- Files are accessible via WordPress media queries and standard URLs.
- Temporary files created during processing are automatically cleaned up.

---

## Error Handling

| Error Message | Cause | Solution |
|---------------|-------|----------|
| "File URLs are required" | No URLs provided in the input field. | Enter at least one valid file URL. |
| "No valid file URLs provided" | All provided URLs were invalid or inaccessible. | Check URL format and ensure files are publicly accessible. |
| "Failed to create ZIP archive" | PHP couldn't create the ZIP file. | Check file permissions and available disk space. |
| "Failed to open ZIP archive" | The ZIP file is corrupted or invalid. | Verify the ZIP file is valid and not corrupted. |
| "Failed to extract ZIP archive" | Wrong password or corrupted archive. | Provide the correct password or verify archive integrity. |
| "None of the specified files were found" | File names don't match any entries in the archive. | Use List ZIP Contents to verify exact file paths. |

> **Note:** When some files succeed and others fail, the action still returns `status: success` with a `failed_files` array listing the failures. This allows your workflow to continue while still reporting issues.

---

## Tips

- **Use List ZIP Contents first** — Before removing files, use List ZIP Contents to see exact file paths.
- **Organize with Base Folders** — Use the Base Folder field to create organized directory structures inside your archives.
- **Handle partial failures** — Check the `failed_files` array in the output to handle files that couldn't be downloaded.
- **Dynamic file lists** — Pass file URLs from previous workflow steps using dynamic variables like `{HTTPRequest1.file_urls}`.
- **Duplicate filenames** — If multiple files have the same name, FlowMattic automatically appends `-1`, `-2`, etc. to avoid conflicts.

---

## Limitations

- Cannot **create** password-protected archives (extraction of password-protected archives is supported).
- File types extracted from ZIPs must comply with WordPress upload settings.
- Large archives may require more server memory and processing time.
- Each file is downloaded individually from its URL during archive creation.

---

## Summary

| Feature | Details |
|---------|---------|
| **Connection Required** | No (built-in core app) |
| **Available Actions** | 5 (Create, Extract, List Contents, Add Files, Remove Files) |
| **Triggers** | None |
| **Password Support** | Extraction only (not creation) |
| **Media Library** | Automatic upload for created and extracted files |
| **Input Formats** | Comma-separated URLs, JSON arrays |
| **Base Folder** | Optional directory structure inside ZIP |