Skip to content
← Back to documentation
Technical Reference

Salesforce

Connect Salesforce with Flows360 to automate CRM workflows and data movement.

CategoryCRM
Authenticationcustom
Version0.8.0
Published scopes0 published scopes
Last updatedSeptember 23, 2026

Overview

Connect Salesforce with Flows360

Connect Salesforce with Flows360 to automate CRM workflows and data movement.

Use the Salesforce connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 27 actions and 9 triggers.

Available actions

  • Add Contact to Campaign
  • Add File to Record
  • Add Lead to Campaign
  • Create Attachment (Legacy)
  • Create Case
  • Create Contact
  • Create Lead
  • Create Note
  • Plus 19 additional declared actions.

Available triggers

  • New Case Attachment
  • New Contact
  • New Field History Event
  • New Lead
  • New or Updated Record
  • New Outbound Message
  • Plus 3 additional declared triggers.

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Salesforce
  • Package: @activepieces/piece-salesforce@0.8.0
  • Exact artifact digest: sha256:6af1a5efda13dffffa3b57d04b6f2488ae656d6811c831161a85b81cc617f569
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

OAUTH2. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Add Contact to Campaign (add_contact_to_campaign), Add a contact to a campaign. Classification: read.
  • Add File to Record (add_file_to_record), Uploads a file and attaches it to an existing record. Classification: read.
  • Add Lead to Campaign (add_lead_to_campaign), Adds an existing lead to an existing campaign. Classification: read.
  • Create Attachment (Legacy) (create_attachment), Creates a legacy Attachment record. Salesforce recommends using "Add File to Record" for modern apps. Classification: read.
  • Create Case (create_case), Creates a Case, which represents a customer issue or problem. Classification: read.
  • Create Contact (create_contact), Creates a new contact record. Classification: read.
  • Create Lead (create_lead), Creates a new lead. Classification: read.
  • Create Note (create_note), Creates a note and attaches it to a record. Classification: read.
  • Create Opportunity (create_opportunity), Creates a new opportunity. Classification: read.
  • Create Record (create_record), Create a record of a given object. Classification: read.
  • Create Task (create_task), Creates a new task. Classification: read.
  • Delete Opportunity (delete_opportunity), Deletes an opportunity. Classification: read.
  • Delete Record (delete_record), Deletes an existing record in an object. Classification: read.
  • Export Report (export_report), Export a Salesforce report as an Excel file. Classification: read.
  • Find Child Records (find_child_records), Finds child records related to a parent record. Classification: read.
  • Find Record (find_record), Finds a record by a field value. Classification: read.
  • Find Records by Query (Advanced) (find_records_by_query), Finds records in an object using a SOQL WHERE clause. Classification: read.
  • Get Record Attachments (get_record_attachments), Get all attachments (both classic and modern Files) for a record. Classification: read.
  • Run Query (Advanced) (run_query), Run a salesforce query Classification: read.
  • Run Report (run_report), Execute a Salesforce analytics report and return the results as easy-to-use rows. Classification: read.
  • Send Email (send_email), Sends an email to a Contact or Lead by creating an EmailMessage record. Classification: read.
  • Update Contact (update_contact), Update an existing contact. Classification: read.
  • Update Lead (update_lead), Update an existing lead. Classification: read.
  • Update Record (update_record), Updates an existing record. Classification: read.
  • Batch Upsert (Advanced) (upsert_by_external_id), Batch upsert a record by external id Classification: read.
  • Bulk Upsert (Advanced) (upsert_by_external_id_bulk), Bulk upsert a record by external id Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Case Attachment, polling.
  • New Contact, polling.
  • New Field History Event, polling.
  • New Lead, polling.
  • New or Updated Record, polling.
  • New Outbound Message, webhook.
  • New Record, polling.
  • New or Updated File, polling.
  • New Case in Queue, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objectsNot published
Supported actionsNot published
Triggers9

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Access token Required · protected credential
  • Salesforce Domain Required

Triggers

New Case Attachment · Poll

Fires when a new Attachment or File is added to any Case record.

New Contact · Poll

Fires when a new Contact record is created in Salesforce.

New Field History Event · Poll

Fires when a tracked field is updated on a specified object.

Inputs

  • object · string
New Lead · Poll

Fires when a new Lead record is created in Salesforce.

New or Updated Record · Poll

Triggers when there is new or updated record

Inputs

  • object · string
  • conditions · string
New Outbound Message · Webhook

Fires when a new outbound message is received from Salesforce.

New Record · Poll

Triggers when there is new record

Inputs

  • object · string
  • conditions · string
New or Updated File · Poll

Fires when a file (ContentDocument) is created or updated. Does not fire for classic Attachments or Notes.

New Case in Queue · Poll

Triggers when a new Case record is assigned to a specified queue.

Inputs

  • caseQueueId · string

Setup

Setup

  1. Add the Salesforce connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Salesforce Domain (environment), required.

OAuth scopes

  • refresh_token
  • full
  • api
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-salesforce@0.8.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 27 actions and 9 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Salesforce connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-salesforce@0.8.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.