# Glossary

## C

**Connector:** A Connector links an external API with FlowMate and defines the available authentication, triggers, and actions. It is the technical foundation for building integrations.

**Credential:** A credential stores the authentication information a user provides to allow FlowMate to access an external system.

## E

**Execution:** An execution is a single step performed within a Flow (such as a trigger or action call) and does **not** include internal FlowMate control components like Logic Gateways.

## F

**Flow:** A Flow is a customer-specific instance of a Template that executes a defined workflow using configured triggers, actions, and mappings.

## G

**Groups:** User groups can be used to control which of your users can see a particular template when it is published.

## I

**Integration Center:** The Integration Center is the customer-facing web component where users activate, configure, and monitor their integrations.

**Instance:** An instance refers to a concrete, active version of a Template (a Flow) created and configured by a customer.

## M

**Mapping**: Mapping defines how data from the trigger is transformed and sent to the action.

## O

**Options:** FlowMate offers several advanced options that help you control how data is fetched, split, synchronized, and passed between flow steps.

## P

**Platform**: The Platform is where teams build, manage, and maintain Connectors, Templates, and all integration logic in FlowMate.

**Polling**: Polling is a trigger mechanism that retrieves data from an external API at regular intervals.

## S

**Snapshot:** A snapshot stores state information (e.g., the last processed timestamp) so a Flow can continue from where it left off.

## T

**Template:** A Template is the reusable blueprint of an integration that defines triggers, actions, and mappings; customers create Flows from it.

## U

**User:** A user is an end customer or team member who interacts with FlowMate, either through the Platform or the Integration Center.

## W

**Workflow:** A workflow represents the logical sequence of steps (trigger, logic, actions) that a Flow executes.

**Webhook:** A webhook is an event-based trigger where external systems send real-time updates to FlowMate.

**Webhook Connector:** A Webhook Connector receives incoming webhook events via virtual endpoints and passes them into the Flow for processing.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://flowmate.gitbook.io/flowmate-documentation/glossary/glossary.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.