Salesforce

Connect your Salesforce CRM to Floqer to import records into lists, look up and enrich records mid-workflow, and write results back — all over a secure OAuth 2.0 connection.

Two ways to connect

MethodBest forHow it authenticates
Salesforce loginGetting started quickly — connect as yourself in a few clicksOAuth 2.0 authorization flow: you sign in to Salesforce and approve access
API-only integration userOrgs that want a dedicated, tightly scoped connection not tied to a person — see Set up an integration userOAuth 2.0 client credentials: server-to-server, no interactive login

Both production and sandbox orgs are supported. Either way, Floqer's access is always bounded by the object and field permissions of the connecting Salesforce user — see Permissions and scope control. Requirements — supported editions, user licenses, and permissions — are covered in the FAQs.

Connect with your Salesforce login

This method signs in through Floqer's own connected app, which Floqer maintains. The Salesforce organization does not need to create an app of its own.

Careful

Not a Salesforce admin? An admin must first install the Floqer app in Salesforce. Until then, only admins can connect.

  1. Log in to app.floqer.com and go to Connections → Salesforce.
  2. When connecting a Salesforce sandbox, check Use Sandbox Environment.
  3. Select Connect to Salesforce. Floqer redirects to the Salesforce login page.
  4. Sign in with Salesforce credentials and complete any verification the organization requires (single sign-on, multi-factor authentication, or a security token).
  5. On the Salesforce authorization screen, review the four OAuth scopes Floqer requests and select Allow. Salesforce redirects back to Floqer.
  6. Under Your Connections, confirm Salesforce shows as connected.
  7. Open the connection to finish setting it up:
    • Optionally toggle Enable for Org to share this connection with everyone in the organization.
    • Optionally toggle Set as Default to make this the default Salesforce connection.
    • Select Save Changes.

Install the Floqer app for users

A Salesforce admin completes these steps once per Salesforce organization. The admin must have authorized Floqer at least once (steps 1 to 5 above) so that the app appears in Setup.

  1. Go to Setup → Connected Apps OAuth Usage.
  2. Find Floqer and select Install.
  3. Go to Setup → Manage Connected Apps → Floqer → Edit Policies.
  4. Under Permitted Users, choose one option:
    • All users may self-authorize: any user with API access can connect.
    • Admin approved users are pre-authorized: only users with an approved profile or permission set can connect. This applies to admins too, so approve every user who should connect, including users who already connected. After saving, add those profiles or permission sets under Manage Profiles or Manage Permission Sets on the app page.
  5. Under Refresh Token Policy, select Refresh token is valid until revoked, so the connection does not expire after authorization.
  6. Select Save.

Connect as an API-only integration user

This method uses the consumer key and secret from an External Client App that a Salesforce admin creates in Set up an integration user.

  1. Log in to app.floqer.com and go to Connections → Salesforce.
  2. Select Integration User.
  3. When connecting a Salesforce sandbox, check Use Sandbox Environment.
  4. Enter the credentials from the External Client App:
    • Client ID: the consumer key
    • Client Secret: the consumer secret
    • Instance URL: the organization's My Domain address, found under Setup → My Domain, including https://, for example https://yourorg.my.salesforce.com
  5. Optionally toggle Enable for Org to share this connection with everyone in the organization.
  6. Select Connect to Salesforce.

Floqer authenticates server to server as the integration user, with no password and no interactive login.

Set up an integration user

For a connection that is not tied to a person, a Salesforce admin can create a dedicated API-only user and External Client App, and connect Floqer through the OAuth 2.0 client credentials flow:

  • A hard permission boundary. Floqer operates as this user and can never exceed its profile and permission sets. Exposing only the objects and fields in scope makes the boundary enforceable, rather than a configuration convention — see Permissions and scope control.
  • No interactive login. The user is API-only — it cannot log in to the Salesforce UI at all — and the client credentials flow authenticates server-to-server without anyone signing in.
  • Not tied to a person. The connection runs as a dedicated user on the Salesforce Integration license rather than as one of your team members.

The setup has three parts: create the API-only user (steps 1 to 3), then create the External Client App that Floqer authenticates through (steps 4 to 6), and finally connect in Floqer (step 7). The admin must be logged in to Salesforce as a System Administrator.

Step 1 — Create the user

  1. Go to Setup → Users → Users → New User.

  2. Fill in the user details:

    FieldValue
    First / last namee.g. Floqer Integration
    EmailA real or alias email you control, e.g. sfdc-floqer@yourcompany.com
    UsernameMust be globally unique, e.g. floqer-integration@yourcompany.com.prod
    User LicenseSalesforce Integration
    ProfileSalesforce API Only System Integrations
  3. Click Save. Salesforce will display a notice that this is an API-only account that cannot log in via the UI — that's expected.

Careful

The profile must be exactly Salesforce API Only System Integrations. Selecting the wrong profile here is the most common setup mistake.

Step 2 — Assign the permission set license

Before the user can do anything useful, it needs the Salesforce API Integration permission set license:

  1. Open the user record: Setup → Users → Users → [your new user].
  2. Under Permission Set License Assignments, click Edit Assignments.
  3. Enable Salesforce API Integration and click Save.

Step 3 — Create and assign a permission set

The API-only profile has zero object permissions by default, so a custom permission set is what actually grants Floqer access to the objects it will read and write:

Create the permission set

  1. Go to Setup → Users → Permission Sets → New.
  2. Enter a Label, for example Floqer Integration Access. The API Name fills in automatically.
  3. Under License, select Salesforce API Integration.
  4. Select Save. Salesforce opens the permission set's overview page.

Grant object and field access

Repeat these steps for each object Floqer will read or write, for example Accounts, Contacts, and Leads.

  1. On the permission set's overview page, select Object Settings.
  2. Select the object, then select Edit.
  3. Under Object Permissions, check Read. For objects that workflows write to, also check Create and Edit.
  4. Under Field Permissions, check Read Access for each field Floqer reads, and Edit Access for each field Floqer writes.
  5. Select Save, then return to Object Settings for the next object.

Assign the permission set to the integration user

  1. On the permission set's overview page, select Manage Assignments → Add Assignment.
  2. Check the Floqer Integration user and select Next.
  3. Select Assign, then Done.

Note

This permission set is the integration's scope. Floqer can only ever read and write what it grants — anything outside it is inaccessible regardless of how a workflow is configured.

Step 4 — Create an External Client App

Salesforce has replaced connected apps with External Client Apps, and new Salesforce organizations can no longer create connected apps by default.

  1. Go to Setup, search for External Client App Manager, and select New External Client App.
  2. Under Basic Information:
    • External Client App Name: Floqer Integration
    • Contact Email: the admin's email address
    • Distribution State: Local
  3. Under API (Enable OAuth Settings):
    • Check Enable OAuth.
    • Callback URL: https://login.salesforce.com/services/oauth2/callback
    • Add the OAuth Scopes: Manage user data via APIs (api) and Perform requests at any time (refresh_token, offline_access).
    • Under Flow Enablement, check Enable Client Credentials Flow.
  4. Select Create. The app can take up to 10 minutes to activate.

Step 5 — Set the "Run As" user

This step ties the integration user to the app for the client credentials flow.

  1. Open the app in External Client App Manager and go to the Policies tab.
  2. Select Edit.
  3. Under OAuth Policies, check Enable Client Credentials Flow and set Run As (Username) to the Floqer Integration user.
  4. Under Permitted Users, select Admin approved users are pre-authorized.
  5. Under App Policies, go to Select Permission Sets and move Floqer Integration Access (from Step 3) into the selected list.
  6. Select Save.

Step 6 — Get the consumer key and secret

  1. On the app's Settings tab, expand OAuth Settings and select Consumer Key and Secret. Salesforce may ask for a verification code.
  2. Copy the Consumer Key (client identifier) and Consumer Secret (client secret), and store them securely.

Step 7 — Connect in Floqer

  1. In Salesforce, go to Setup → My Domain and copy the Current My Domain URL. This is the instance URL. It must start with https://, for example https://yourorg.my.salesforce.com. Salesforce displays the address without https://, so add it before pasting.
  2. In Floqer, go to Connections → Salesforce and select Integration User.
  3. Enter the Consumer Key as the Client ID, the Consumer Secret as the Client Secret, and the My Domain URL as the Instance URL. Check Use Sandbox Environment only for a sandbox organization.
  4. Optionally toggle Enable for Org to share this connection with everyone in the organization.
  5. Select Connect to Salesforce.

If Floqer shows Failed to parse URL, the instance URL is missing https://. If the connection fails for another reason, wait up to 10 minutes for the app to activate and try again. Also confirm that Enable Client Credentials Flow is checked and Run As is set to the integration user in Step 5.

Salesforce Actions

The integration is two-way, with five actions, each configured per workflow:

ActionSalesforce API call
Import records into a Floqer listPOST /jobs/query (Bulk API 2.0 query job), then GET /jobs/query/{id} to poll and GET /jobs/query/{id}/results to download pages, then DELETE /jobs/query/{id} once the import completes; GET /query for the preview, the record count, and a scheduled refresh small enough for one page
Look up records mid-workflowGET /query (SOQL)
Create a recordPOST /sobjects/{Object}
Update a recordPATCH /sobjects/{Object}/{Id}
Upsert by external IDPATCH /sobjects/{Object}/{ExternalIdField}/{value}

Reads and writes are configured independently, so you can run the integration read-only, write-only, or both — and a read-only setup is enforceable by granting the connecting user read-only access.

Floqer's writes are limited to create, update, and upsert. It never deletes Salesforce records.

Alongside these, read-only metadata calls (/sobjects, /describe, /listviews) populate the setup UI so you can pick objects and fields from your live org.

Security and access

Note

Security at a glance: Floqer connects over OAuth 2.0, so your Salesforce password is never shared with Floqer. Access tokens refresh automatically, access is bounded by the connecting user's object and field permissions, and you can revoke it at any time.

OAuth scopes

For the login method, Floqer's connected app requests four scopes:

ScopeSalesforce labelWhy Floqer needs it
apiManage user data via APIsThe working scope: read records via SOQL, including Bulk API 2.0 query jobs, and create, update, and upsert records through the REST API.
refresh_token, offline_accessPerform requests at any timeLets scheduled syncs and workflow runs execute without a user re-authenticating each time.
id, profile, emailAccess the identity URL serviceRead at connect time only, to identify which org and user the connection belongs to and to resolve your org's domain for API calls.
openidAccess unique user identifiersProvides the stable user identifier that ties the connection to a specific Salesforce user.

Revoking access

Floqer's access can be revoked at any time:

  • Login method, in Salesforce: go to Setup → Connected Apps OAuth Usage and revoke the Floqer app.
  • Integration user, in Salesforce: delete the External Client App in External Client App Manager. This stops every integration that uses it.
  • In Floqer: disconnect the connection under Connections → Salesforce.

Permissions and scope control

Floqer operates entirely as the Salesforce user who authorizes the connection and inherits that user's permissions. That user needs:

  • API Enabled (via profile or permission set)
  • Read access on any object and field you want to import
  • Create and Edit access on any object and field you want to write to

Nothing more: Floqer does not require System Administrator, Modify All Data, View All Data, or any Delete permission. Field-Level Security, sharing rules, and record-level access all apply normally.

The api scope grants no more than the authorizing user can already see and do, so that user's permissions are where scope is genuinely controlled. Access can be limited at two layers:

  • Configuration layer. Floqer queries only the fields you select and writes only the fields you map. Unselected fields are never requested and never stored.
  • Permission layer — the enforceable one. Connect with a dedicated integration user whose profile and permission sets expose only the objects and fields in scope — for example, read on Account.Name, Account.Website, and Contact.Email, and edit on the specific enrichment target fields. Anything outside that permission set is inaccessible to Floqer regardless of how a workflow is configured. See Set up an integration user.

Careful

The OAuth credential inherits the authorizing user's full reach. If a System Administrator authorizes the connection, the credential is capable of reading records Floqer will never actually query. This is inherent to Salesforce's OAuth model rather than specific to Floqer — and it's exactly why we recommend a scoped integration user, which collapses the gap between what Floqer accesses and what it could access.

FAQs

Which Salesforce editions are supported?

Your Salesforce organization must be on an edition that includes API access:

EditionAPI access
EnterpriseIncluded
UnlimitedIncluded
PerformanceIncluded
DeveloperIncluded (for testing and development)
ProfessionalNot included by default — requires the API Access add-on. Once purchased, the integration works normally.

Which user licenses include API access?

Your Salesforce user needs a license that includes API access. All of these qualify:

LicenseNotes
SalesforceFull CRM access to all standard and custom objects — the most common license for CRM users
Salesforce Platform (formerly Force.com)Custom objects and a limited set of standard objects — good for custom app users
Salesforce Platform PlusEnhanced platform license with broader standard-object access

What permissions does my Salesforce user need?

Every connecting user needs these two permissions:

  • API Enabled — required to make any API calls.
  • View Setup and Configuration — required to read the object and field metadata that populates Floqer's setup screens.

Beyond that, what you need depends on what your workflows do:

  • Read-only workflows (imports and lookups) — read permission on the objects you'll query (Contacts, Accounts, Leads, Opportunities, and any custom objects), or the broader View All Data.
  • Write operations (create, update, upsert) — create and edit permission on the objects and fields you'll write to, or the broader Modify All Data.

Note

Object-specific permissions are enough. Floqer never requires System Administrator, View All Data, or Modify All Data — granting access to just the objects and fields your workflows touch is the recommended setup.

Note

API Enabled is not enough on its own for the login method. A user who is not an admin also needs a Salesforce admin to install the Floqer app and allow the user under its policies. See Install the Floqer app for users.

To check your permissions:

  1. Go to Setup → Users → Users and click your name.
  2. Review your Profile and Permission Set Assignments.
  3. Confirm API Enabled and View Setup and Configuration are on, plus read (and, for writes, edit) access on the objects your workflows will use.

How is the integration built?

Floqer calls the Salesforce REST and Bulk API 2.0 endpoints (/services/data/v61.0/) directly, server-to-server over HTTPS, authenticated with OAuth 2.0 through Floqer's connected app (login method) or the organization's own External Client App (integration user).

  • No code is deployed to the organization. The integration is not an AppExchange package. No Apex, Lightning components, flows, custom objects, or metadata are deployed. Installing the Floqer app only adds the app's access policies, which the admin controls.
  • No middleware. No iPaaS, ETL vendor, or integration broker sits in the path. Traffic goes directly between Floqer's infrastructure and your Salesforce instance.
  • Floqer initiates every connection. No Salesforce-initiated traffic occurs in either direction.

On the Salesforce side, the only artifacts depend on the connection method:

  • Login method: the app authorization and, when installed, the Floqer app's policies. Both are visible and revocable at any time under Setup → Connected Apps OAuth Usage.
  • Integration user: the API-only user, its permission set, and the External Client App that the admin creates. All three stay under the admin's control in Setup.
  • Both methods: each import creates a Bulk API 2.0 query job in your org, visible under Setup → Bulk Data Load Jobs while it runs. Floqer deletes the job and its result set when the import completes, fails, or is paused; if that delete does not go through, Salesforce removes them itself after 7 days. Floqer only downloads the results; it does not export them anywhere else.

How does data get from Salesforce into Floqer?

  1. Floqer fetches your org's objects and fields so they appear as options in the setup screen. You pick the object and fields to import, plus any filters or a Salesforce List View.
  2. On each run, on demand or on schedule, Floqer submits one Bulk API 2.0 query job for the selected fields and filters only, then downloads the results in pages once Salesforce has prepared them. The preview and the record count use the synchronous query endpoint, and so does a scheduled refresh whose changed records fit one page (up to 2,000 rows), which then costs a single API request and creates no job. For large imports, Bulk API query jobs use far fewer API requests than paging through the query endpoint, which keeps them well inside your org's daily API allowance. A small import costs a few more requests than a single query page would.
  3. Returned records are normalized, stored in Floqer's managed cloud datastores keyed by the Salesforce record Id, and loaded into your list or workflow table.
  4. Workflow steps then operate on those rows — enrichment lookups, transformations, AI-generated fields.

How does data get from Floqer back into Salesforce?

  1. A workflow row reaches a Salesforce create, update, or upsert step.
  2. Floqer builds the payload from the fields you mapped in that step.
  3. The REST call is sent over HTTPS to your org.
  4. Salesforce's response — record ID, insert-vs-update outcome, record URL, or an error — is written back onto the workflow row so you can see the result.

When does Floqer sync, and how often?

Floqer initiates all traffic, either on demand when you run an import or workflow, or on a schedule you configure (default weekly). Scheduled syncs are incremental — they query only records created or modified since the last run — and can be paused or removed at any time.

Which of those records reach connected workflows is set by New Records Only, described under Does editing a Salesforce record run my workflow again?.

Does editing a Salesforce record run my workflow again?

It depends on the New Records Only setting. It appears under Import Existing Records when an Active source is created, and is on by default. Sources created before the setting was introduced have it off.

  • On: a scheduled sync adds a record to connected workflows only if it is not already in the source's list, whatever its creation date. Records from the initial import are already in the list, so editing them updates the list but adds no workflow row and does not run the workflow again. A newly created record, an older record that an edit brings into the source's filters, or, when existing records were not imported, an older record on its first edit is added once. A record stays in the list after it stops matching the filters, so it is not added again when it matches later. Deleting a row from the source's list lets that record come in again the next time it is edited.
  • Off: every matching record created or edited since the last sync is added, one new row per sync that finds the record changed. The row runs when the source's sync is set to Push and Run All and the play/pause Auto-run switch in the workflow's Data view toolbar is on.
  • Workflows that update the records this source pulls: leave the setting on. Such an update is an edit, so with the setting off each updated record is added again on the next sync, and runs again under the same conditions.
  • Changing it: use the New records only switch on the source's page, shown while the source is active or paused.

Which objects and fields does Floqer read and write?

There is no fixed list. Floqer defines no schema of its own and requires no specific object or field: you select the objects and exact fields at configuration time, from your own org. The only field Floqer requires is the record Id. In practice:

  • Read — the objects and fields selected for import or lookup, typically Lead, Contact, and Account.
  • Write — only the fields explicitly mapped in a workflow's create, update, or upsert step, typically enrichment output written to a defined set of target fields.

Floqer reads no field you haven't selected and writes no field you haven't mapped. There is no background crawling, no full-org sync, and no process that reads objects outside a configured import or workflow step. A Bulk API query job covers only the object, fields, and filters you configured for that import, and Floqer never creates a job you did not ask for.

What data does Floqer store?

CategoryTypical itemsDirection
CRM record identifiersRecord Id, external ID field values, owner, created and modified datesRead
Business contact dataName, job title, business email, business phone, LinkedIn URLRead and write
Company / firmographic dataAccount name, domain, website, industry, employee count, revenue, locationRead and write
Custom fieldsAny __c field you select or mapRead and write
Enrichment and AI-generated outputEnriched firmographic or contact attributes, scores, classifications, generated textWrite
Integration credentialsOAuth access and refresh tokens, org instance URL, and the connecting user's identity (user ID, name, email, org ID)Held by Floqer
Operational dataJob status, timestamps, API responses and error messagesHeld by Floqer

What can Floqer see regardless of configuration?

Two things:

  • Your schema. To populate the setup screens, Floqer reads the list of objects in your org and the field names and types of any object you open in the configuration UI, including custom objects and fields. This is metadata only — names and types, never record contents.
  • The User object, minimally. Floqer reads Id and Name from the User object in two places: to display record-owner names alongside looked-up records, and to populate owner selection lists in the setup UI. No other User fields are read, and Floqer never writes to the User object. Beyond that, Floqer stores the name, email, user ID, and organization ID of the Salesforce user who authorized the connection, returned by Salesforce at connect time.

How long is data from Salesforce retained?

Records imported from Salesforce are retained for the duration of your engagement, for functional reasons: so workflows can operate on them, results remain available for review and export, and re-running or auditing a workflow produces consistent output. Data is stored in Floqer's managed cloud infrastructure and scoped to your organization. Each import's query job and result set live in your Salesforce org only until the import ends, when Floqer deletes them; a job whose delete does not go through is removed by Salesforce after 7 days. That copy never leaves your org except through Floqer's download.

Is our data used for anything beyond serving us?

No:

  • Not used to build or resell a data pool. Floqer does not aggregate, sell, license, or otherwise commercialize customer records. Your data is not offered to other customers and does not form part of any Floqer-owned dataset or product.
  • Not used to train models. Floqer does not train, fine-tune, or evaluate any model on customer data.
  • Not used for benchmarking, analytics, or product development against your records.

How do we delete our data?

  • You can delete individual lists, workflows, and connections yourself at any time from within the product.
  • For full deletion, send a written request to privacy@floqer.com. Deletion covers records ingested from your systems, workflow data derived from them, uploaded files, and the credentials of connected integrations. It is completed within 30 days of the request, and Floqer provides written confirmation once done.

Have a question that isn't answered here? Contact Floqer support at hello@floqer.com.