The deepest Salesforce integration for revenue, marketing, and service teams.
Salesforce
The deepest Salesforce integration for revenue, marketing, and service teams.
Flows360 gives operators an end-to-end view of Salesforce alongside the rest of their stack — sync the objects that matter, run the actions you need, and trigger workflows on real-time events without writing glue code.
Common use cases
- Run cross-CRM deduplication and routing
- Reconstruct revenue attribution across Salesforce and marketing
- Surface usage and product data on the Account record
Sync scenarios
- Sync Salesforce accounts and opportunities into your data warehouse
- Push enriched leads from your CDP back into Salesforce
- Mirror cases between Salesforce Service Cloud and Zendesk
Objects supported
- Contact
- Lead
- Account
- Opportunity
- Case
- Campaign
- Task
- Event
- Pricebook
- Quote
Actions
- create_record
- update_record
- search_records
- list_records
- lead_created
- deal_won
- convert_lead
- merge_records
- add_member_to_campaign
- record_updated
- record_deleted
- new_case_created
- task_reminder_due
Frequently asked questions
Which Salesforce editions are supported?
Enterprise and above; Professional works when API access is enabled.
Does this respect Salesforce Shield?
Yes — encrypted fields stay encrypted in transit and at rest.
- Auth method: OAuth 2.0
- Required scopes: 2
- Supported objects: 3
- Supported actions: 4
Overview
The Flows360 connector for Salesforce lets you build reliable, bidirectional integrations between Salesforce and the other tools your teams rely on every day. Move records, trigger downstream workflows, and keep data consistent across CRMs, ERPs, data warehouses, support desks, and internal apps — without writing or maintaining glue code.
Use this connector to eliminate manual data entry, reduce swivel-chair work between systems, and give every team a complete, real-time view of customers, operations, and pipeline. Flows360 handles authentication, pagination, retries, rate-limit backoff, and schema drift so your integrations stay healthy as Salesforce evolves.
Setup steps
1. Sign in to Salesforce
Log in to your Salesforce account with an administrator user that can create or manage API credentials.
2. Create credentials for Flows360
In the Salesforce admin area, create a new API key, service account, or OAuth application dedicated to Flows360. Grant it the minimum scopes required to read and write the objects you plan to sync.
3. Copy the credentials
Copy the generated client ID, client secret, API token, or service account key. Treat these values as secrets — they grant access to your Salesforce data.
4. Connect from Flows360
In Flows360, open Connectors → Salesforce → Connect. Paste the credentials into the matching fields and (for OAuth) complete the authorization redirect.
5. Test the connection
Run the built-in test in Flows360. A successful test confirms credentials, network access, and the required scopes. You can now use Salesforce as a source or destination in any flow.
Required scopes
readwrite
Supported objects
- Record
- User
- Activity
Supported actions
- list_records — Retrieve records from Salesforce with optional filters.
- create_record — Create a new record in Salesforce.
- update_record — Update an existing record in Salesforce by its ID.
- record_changed — Trigger a flow when a record in Salesforce is created or updated.
Use cases
- Customer 360
- Marketing Automation
- Revenue Operations
- CRM to ERP Sync
Limitations
- Throughput is bounded by the Salesforce API's published rate limits; Flows360 automatically retries with exponential backoff.
- Computed, derived, or read-only fields in Salesforce cannot be written to from Flows360.
- Real-time triggers depend on Salesforce supporting webhooks; otherwise Flows360 falls back to polling on the schedule you configure.
- Large historical backfills should be run during off-peak windows to avoid hitting daily API quotas.