New User Role for Sales Reps, File Uploads and CSV Exports via MCP and APIs

Role-based access controls what each person can do in your organization. So far, we had two roles:

• Admin: access to every feature, including viewing and editing every member's workflows, billing, managing users, and all other administrative settings.
• Member: access to every feature, but can't view or edit workflows from other members unless they're shared with them. No billing, and can't add users either.

Often, RevOps want to make a simple Shortcut that needs to be used by tens of users across a sales team. Until today, everyone could build a workflow, even when most people only needed to run it for their use case. This role lets RevOps limit access and keep things simple for the end user of the application they have built.

We're introducing a new role for users who don't want to enter the complexity of workflows, for example sales reps. We call this new role User.

• User: can run Shortcuts. This works in Floqer, and also from MCP, APIs, Flo in Slack or any agentic platform. They can also build lists and pull leads from CRMs. No access to workflows.

Here's how you can assign it. There are 2 ways to do it.

Option 1: For organizations without SSO

You can manage roles in Floqer from Settings → Members.

• Invite a teammate. Click Invite member and choose their role when sending the invitation.
• Change an existing role. Use the role control beside the teammate to open Change role. Select Admin, Member, or User, then confirm with Change to user.

Option 2: For organizations with SSO (Okta, Descope, etc)

If your organization signs in with SSO, roles are assigned in your identity provider, not in Floqer. Floqer reads the role from the groups a person belongs to there. Map your groups to these roles:

• Admin: org_lead
• Member: org_member
• User: org_user

If a person belongs to more than one of these groups, Floqer takes the role with the least privileges.

Note

If you connect an agent over MCP or the API, it gets the same permissions as your role in the organization you're currently in.

Most enrichments start as a lead list or a CSV of unclean data. To use one with Floqer Agent or Flo in Slack, you had to import it in the Floqer platform first and then come back.

• Drop a CSV or XLSX into Floqer Agent and describe what you want to do with the list. Your agent can use the file to build a workflow, so you can start with your own data without copying rows into the conversation.

• From Slack: attach a CSV or XLSX in a connected channel and tag @flo to import it into a workflow. Reactions confirm receipt, and the reply tags you when ready so you do not have to keep checking.

Note

Slack access requires Floqer Agent enabled for your organization and a connected channel. Contact the Floqer team for access.

Shortcuts can now be run from MCP, APIs, Flo in Slack or any agentic platform. Your existing Shortcuts work as they are, with no need to switch back to the platform.

• Run a Shortcut on your list. Upload a CSV and map its columns to the Shortcut's inputs. The list runs as one batch, so you do not pass each row individually.
• Read the status of your batch run. See which rows are done and what came back, while the batch is still running.
• Export the results. Get the whole batch in one CSV with the inputs, outputs and run status of every row. Exports run in the background, and you download the file when it is ready.

See Export Shortcut Runs in the API reference.

Workflow results can now be exported as a CSV from MCP, APIs, Flo in Slack or any agentic platform, without leaving the conversation.

• Choose what to export. All rows, selected rows, or the rows matching your filters.
• Download when ready. Exports run in the background. Follow the progress, then download the CSV to review or share.

See Export Sheet in the API reference.

You can now turn a workflow's Auto-run on or off from MCP or APIs before importing existing data, and update its cache settings.

Turn Auto-run off to review the list before spending credits on enrichment, then choose which rows to run.

Note

The run field on Sync Source to Workflow is deprecated and ignored. If you want to import rows without running actions, set the destination sheet's auto_run to false before syncing. This applies to the initial import and to rows that arrive later.

See Update Sheet in the API reference.

Environment variables only worked in the Floqer platform. Now you can use them from MCP, APIs or any agentic platform too.

• Find the variables you can use. Agents can see which variables exist without reading their values. Creating variables and editing their values stays in the Floqer platform.
• Reference them in actions. Set an action input to a reference such as {{env.<key>}}, so you reuse a vendor key or service URL without pasting it into every action.

See List Environment Variables in the API reference.

FullEnrich brings together 20+ data sources, checking providers in sequence to find contact details. It also verifies work emails before returning them. We added it to Find Work Email so you can find emails a single provider may miss, without connecting each of those providers separately or moving your lists out of Floqer.

• Connect your account. Add FullEnrich to Find Work Email and select Add API Key to save your FullEnrich key.
• Use it in your waterfall. Choose where FullEnrich runs in the provider order. It returns the work email and verification status; when no email is found, the waterfall moves to the next provider. You can configure it in the Floqer platform or during agentic building.
• Use your FullEnrich credits. Enrichment is charged to your FullEnrich account, with no Floqer provider-credit charge. A connected FullEnrich account is required; this integration covers work emails.

Before adding a lead to a campaign, you had to manually check Lemlist to see whether they were already being contacted. Your workflow can now check this for you, so you avoid duplicate outreach or putting the same lead into overlapping campaigns.

Add Lemlist: Get Lead Data to your workflow and provide the lead's email.

• What it returns. The campaigns the lead belongs to, whether any are active, and their email deliverability status, so you can decide whether to continue outreach or skip the lead.
• Leads not in Lemlist. The action returns Found In Lemlist = false, so the rest of the workflow can keep running.

Note

Requires a connected Lemlist workspace on the Email Pro plan. Other plans return Lemlist's plan-requirement error.

To know how big a company is, you had to run a separate count-only search and pay for it, even when you were already pulling its employees. Sales Nav: Find Employees at Company now returns the total employee count with the employee records, so one run tells you both.

• Number of Employees shows the company total.
• Employees Returned shows how many employee records the run returned.
• Number of Pages still controls how many pages you retrieve, at 25 credits per page.

Row status counts load faster when you open a workflow, including large workflow tables. See how many rows are running, completed, or failed so you can follow the workflow's progress.