Core concepts
The Floqer object model on one page. Five minutes here and the rest of the documentation reads without friction.
Note
Prefer watching? Floqer 101 on University covers the same ground as guided video lessons.
1. The platform at a glance
Floqer is a data and automation platform for GTM operations. Two modules do the heavy lifting:
- Sources bring leads in: list builders, scrapes, signal trackers, and uploads.
- Workflows do everything after that: clean, qualify, enrich, and automate, then send the result wherever it needs to go.
Around them sit the surfaces you and your team work from:
| Surface | Who works there | What happens there |
|---|---|---|
| The Floqer app | Builders | Create and run workflows and campaigns. |
| Shortcuts | Reps | Workflows packaged as one-click buttons. |
| The Chrome extension | Reps | Run shortcuts on LinkedIn and Sales Navigator. |
| Campaigns | Outbound operators | The cold email engine, fed by workflows. |
| MCP | AI assistants | Read and drive your workspace programmatically. |
2. The object model
Everything in Floqer is one of eleven objects. The build objects chain together: inputs feed actions, actions write to the table, the output node marks the result, and the endpoint sends it onward.
| Object | What it is |
|---|---|
| Workspace | Your organization's Floqer account. Workflows, sources, tables, shortcuts, campaigns, credits, and connections all live in it. |
| Workflow | An automation built from actions. Creating a workflow creates its main sheet automatically; you can work on it in the Floq view (the step canvas) or the Data view (the table of rows). |
| Action | One step in a workflow. An action sources, enriches, qualifies, transforms, or exports data. Actions are the unit that costs credits; see Actions. |
| Input | A typed field the workflow expects before it runs, for example a Person LinkedIn URL of type url. Inputs can be filled in the app, ingested from the page by the extension, or set programmatically over MCP. |
| Table | The rows a workflow reads and writes. Every run lands its results here, one column per field. |
| Output node | The point in a workflow that marks which fields are surfaced as the result, for example a verified work email and phone number. |
| Endpoint | Where the workflow continues after the output node, for example creating or updating a CRM contact, pushing to a sequence, or posting to Slack. |
| Credit | The usage unit. A credit is spent when an action looks up new information; moving, formatting, and exporting data is free. See Credits and pricing. |
| Source | Anything that brings leads or signals into the workspace: list builders, URL scrapes, job posting monitors, website visitor tracking, and more. |
| Shortcut | A workflow packaged as a one-click button, published to your team. Formerly called Apps. See Shortcuts. |
| Campaign | One email sequence paired with a set of leads, sending from your team's own mailboxes. See Campaigns. |
3. The core motion
Almost every Floqer build follows the same sequence, called SeqE (Sequential Engineering):
- Source: find companies and people, from built-in tools or your existing lists.
- Enrich: gather the data you need: emails, phone numbers, firmographics, talking points.
- Qualify: filter to the people who actually match your ICP instead of blasting volume.
- Export: push to your CRM, outreach tools, a campaign, or a CSV.
When planning a bigger build, the Mosaic Method helps: outline the goal, set placeholders for the steps you know you need, then fill in logic that matches prospects to your ICP criteria.
4. Where to go next
- Building workflows: create, configure, test, and ship one.
- Running workflows: run modes, credits during runs, and results.
- Actions: the catalog of building blocks and what they cost.