Role-Based Access, Agentic File Uploads and CSV Exports

Role-Based Access controls what each person can do in your organization. You can give someone access to Sources and Shortcuts without giving them access to workflows, while keeping billing and user management with admins. Floqer has three roles: Admin, Member, and Operator.

Choose a role based on what the teammate needs to do.

• Admin: access to everything, including billing, managing users, and all other administrative settings.
• Member: build and run workflows, create and run Shortcuts, and work with Sources and Connections. Billing and user management remain with Admins.
• Operator: create Sources and run the Shortcuts your team has prepared.

Assign roles in Floqer or through your SSO provider.

• Manage roles in Floqer. Open 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 Operator, then confirm with Change to [role].

• Set up roles with SSO. If your organization uses SSO, configure the SCIM role mappings in your identity provider so users receive the right access in Floqer.
  • Admin: org_lead
  • Member: org_member
  • Operator: org_operator
• Use your role during agentic building. Select the organization you want to work in before connecting your agent to Floqer.
  • The connection uses the organization currently active for your user.
  • Your agent takes on the permissions of your role in that organization, so it has the same access you do there.

• 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.
• Slack access: requires Floqer Agent enabled for your organization and a connected channel. Contact the Floqer team for access.

Running a Shortcut on a CSV meant opening the Floqer platform to start the run and collect the results. Floqer Agent and agentic builders can now handle both, so you can use your existing Shortcuts without switching back to the platform for each step.

• Run a Shortcut on your list. Upload a CSV and map its columns to the Shortcut's inputs. Your agent runs the list as a batch, without passing each row individually.
• Follow the results. Check the batch's run statuses and results as rows complete.
• Export the results. Collect the batch in one CSV with input fields, output values, and run status, ready to review or share. Exports run in the background; download the file when it is ready.
• See Export Shortcut Runs.

• Previously, you had to open the Floqer platform to export workflow results as CSV. Floqer Agent and agentic builders can now export all rows, selected rows, or rows matching your filters, so you can collect your results without leaving the conversation.
• Follow the export's progress, then download the CSV when it is ready to review or share.
• See Export Sheet.

• Floqer Agent and agentic builders can now turn workflow Auto-run on or off before importing existing data. Turn it off to review the list before spending credits on enrichment, then choose which rows to run. You can also update the workflow's cache settings.
• Existing integrations: the run field on Sync Source to Workflow is deprecated and ignored. Set the destination sheet's auto_run to false before syncing if you want to import rows without running actions. This applies to the initial import and later incoming rows.
• See Update Sheet.

• Environment variables previously worked only in the Floqer platform. Floqer Agent and agentic builders can now find available variables and set action inputs to references such as {{env.<key>}}, so you can reuse a vendor key or service URL without pasting it into every action.
• Agents can see which variables are available without reading their values. Create variables and edit their values in the Floqer platform.
• See List Environment Variables.

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 check Lemlist separately to see whether they were already being contacted. Your workflow can now check this for you, helping 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. It returns the campaigns they belong to, whether any are active, and their email deliverability status, so you can decide whether to continue outreach or skip the lead.
• An email that is not in Lemlist returns Found In Lemlist = false, so the rest of the workflow can keep running.
• Requires a connected Lemlist workspace on the Email Pro plan. Other plans return Lemlist's plan-requirement error.

• Sales Nav: Find Employees at Company will return total employee count alongside employee records, so you can size an account without paying for a separate count-only run.
• Number of Employees will show the company total; Employees Returned will show 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.