Create Salesforce Task
Create a Salesforce task from explicit task input.
Salesforce provider contract for accounts, leads, contacts, opportunities, notes, tasks, and pipeline reads.
Connection facts
These details come from the current StackOS provider manifest and action catalog. They describe the available connection—not a promise that every workflow will use every action.
Action catalog
Actions listed for this integration. Individual descriptions note availability limits. A workflow still decides which actions belong in the job and where approval is required.
5 matching actions
Create a Salesforce task from explicit task input.
Query bounded Salesforce Opportunity records through allowlisted query templates.
Upsert a Salesforce Account using an approved external ID field and safe refs.
Upsert a Salesforce Contact using an approved external ID field and safe refs.
Upsert a Salesforce Lead using an approved external ID field and safe refs.
Direct answer
People continue using Salesforce as their tool. StackOS adds it to a visible workflow, keeps the work in order, and passes only the approved action to the integration when that stage is ready.
Common questions
The current catalog includes 5 Salesforce actions across CRM Operations, Lead Management, Pipeline Management. The exact actions used depend on the workflow and approval rules.
No. Salesforce remains the tool that performs its part of the job. StackOS organizes the workflow, keeps status and dependencies visible, and calls the tool only when the plan reaches the right approved action.