Heavier CRM, usually with an existing integration team to coordinate with.
52 workflows in the community library involve Salesforce, and we can build any of them on your own instance. The 40 most used are listed below; the rest are searchable in the library browser.
Counted from the library, not guessed. Each one is a workflow we can build.
Ranked by how many people have actually used them.
| Workflow | Systems joined | |
|---|---|---|
| Salesforce Workflow Automation | Salesforce | open |
| Google Sheets to Salesforce Workflow | Google Sheets, Salesforce | open |
| Microsoft Excel to Salesforce Workflow | Microsoft Excel, Salesforce | open |
| Salesforce Workflow Automation | Salesforce | open |
| Salesforce Workflow Automation | Salesforce, Gong | open |
| Salesforce Workflow Automation | Salesforce | open |
| Salesforce Workflow Automation | Salesforce | open |
| HubSpot to Salesforce Workflow | HubSpot, Salesforce | open |
| Salesforce to Microsoft Outlook Workflow | Salesforce, Microsoft Outlook | open |
| Salesforce Workflow with an AI Step | Salesforce, AI | open |
| Google Sheets to Salesforce Workflow | Google Sheets, Salesforce, AI | open |
| Slack to Salesforce Workflow | Slack, Salesforce, Aws S3 | open |
| Salesforce Workflow Automation | Salesforce | open |
| Email to SMS Workflow | Email, SMS, Salesforce, AI | open |
| Salesforce Workflow with an AI Step | Salesforce, Send In Blue, AI | open |
| Google Drive to Salesforce Workflow | Google Drive, Salesforce, Microsoft One Drive, AI | open |
| Salesforce Workflow with an AI Step | Salesforce, AI | open |
| Email to Slack Workflow | Email, Slack, Salesforce, AI | open |
| Pipedrive to Postgres Workflow | Pipedrive, Postgres, Slack, Trello | open |
| Salesforce to Gmail Workflow | Salesforce, Gmail, AI | open |
| Salesforce to Email Workflow | Salesforce, Email, AI | open |
| Salesforce Workflow Automation | Salesforce | open |
| Google Sheets to Slack Workflow | Google Sheets, Slack, Salesforce, AI | open |
| Google Sheets to Slack Workflow | Google Sheets, Slack, Salesforce, AI | open |
| Google Sheets to Slack Workflow | Google Sheets, Slack, Salesforce, AI | open |
| Slack to Salesforce Workflow | Slack, Salesforce, AI | open |
| Google Sheets to Slack Workflow | Google Sheets, Slack, Salesforce, AI | open |
| Salesforce Workflow Automation | Salesforce | open |
| Slack to Salesforce Workflow | Slack, Salesforce, AI | open |
| Salesforce to Gmail Workflow | Salesforce, Gmail, AI | open |
| Slack to Salesforce Workflow | Slack, Salesforce, Gmail, Microsoft Outlook | open |
| Google Sheets to Salesforce Workflow | Google Sheets, Salesforce, Gmail, AI | open |
| Slack to Google Drive Workflow | Slack, Google Drive, Salesforce, Google Docs | open |
| Google Sheets to Salesforce Workflow | Google Sheets, Salesforce, Gmail, AI | open |
| Google Sheets to Slack Workflow | Google Sheets, Slack, Google Drive, Salesforce | open |
| Postgres to Salesforce Workflow | Postgres, Salesforce | open |
| Google Sheets to Telegram Workflow | Google Sheets, Telegram, Facebook, Salesforce | open |
| Postgres to Slack Workflow | Postgres, Slack, Salesforce, Gmail | open |
| Google Sheets to Slack Workflow | Google Sheets, Slack, Salesforce, Gmail | open |
| Google Sheets to Slack Workflow | Google Sheets, Slack, Salesforce, Gmail | open |
Titles are ours, derived from the systems each workflow joins. The source template is linked so you can check it yourself.
The template is the sketch. This is the part that makes it dependable.
A workflow engine holds the sequence, the retries and the credentials, so the logic lives in one visible place instead of scattered across four tools.
Workflow tools make it easy to build something nobody can maintain. We version every workflow, document the field mapping, and keep credentials out of the canvas.
Built on: A workflow engine on your own instance, connectors to your existing tools, and queued retries so a transient failure never loses a record.
Including the one about whether you are locked into anything.
Every one in the community library, which is 52 for Salesforce right now, plus anything we write from scratch. The library is a starting point, not a limit: what you pay for is the version that is hardened, monitored and fitted to your business.
Between $700 and $2,500 for a single workflow on an instance that already exists, plus a day or two to stand the instance up if it does not. Running it is from $290 a month.
You do not, but it is what we recommend, and it runs on your own instance so you own the automation outright. Its licence expressly permits us to build and support workflows for you. We do not resell it as a product.
Then the library template is a sketch and we build against your actual API surface. That is the same price band; what changes is how much of the mapping we do by hand.
Describe the job in your own words and we will name the workflow, the price and the timeline.