Salesforce
Long-tail Salesforce CRM connector
Salesforce CRM is the long-tail variant of the Salesforce connector for teams that have a separate Salesforce instance configured differently from the main one already wired up. Seven triggers cover Lead and Opportunity lifecycle events; ten actions cover the core Create / Update / Get / List endpoints across Lead, Account, Contact, and Opportunity. The integration shares Salesforce's OAuth model (a connected app installed in your org). For most teams, the main Salesforce connector is the right choice; pick this variant when you need a second, isolated Salesforce connection (multi-org setups, sandbox vs production, or M&A scenarios where two CRMs coexist). All the same caveats apply: field-level security is respected, SOQL queries go via HTTP action, and Marketing Cloud is a separate connector.
Workflows start when Salesforce does.
7 real-time triggers, each backed by a webhook subscription. Events arrive within seconds and you don't have to set up polling.
Fires when a new account is created. For "new B2B account → enrich firmographic data, sync to other tools" workflows.
Fires when a new support case is created. For "high-priority case → page on-call, post to support channel" workflows.
Fires when a new contact is added. The base hook for "auto-enrich → sync to marketing automation → fan out welcome" cross-system onboarding.
Fires when a new lead is added (before conversion to Contact/Account/Opportunity). For lead-enrichment and qualification workflows that act before conversion.
Fires on any lead field change including status transitions. For "lead became MQL → notify BDR" specific-transition workflows.
Fires on new opportunity creation. The pipeline-growth hook for revenue forecasting workflows and AE notification automation.
Fires on any opportunity change. For "stage moved to Closed Won" specifically, filter the payload before downstream side-effects.
Do anything Salesforce can do, from a workflow.
Every action accepts dynamic inputs from upstream nodes, whether that's an AI output, a form field, or a search result.
| Action | What it does |
|---|---|
| Create Salesforce Lead | Creates a lead with name, email, company, status, source. For "marketing form submission → push to Salesforce" lead-capture workflows. |
| Create Salesforce Opportunity | Creates an opportunity tied to an account with amount, stage, close date, owner. For "qualified lead → create opportunity in the right pipeline" workflows. |
| Create Salesforce Record (Any Object) | Generic create for any SObject (Contact, Lead, Custom Object, etc.). For workflows that need to create custom-object records not covered by typed actions. |
| Create Salesforce Task | Creates a follow-up task linked to any SObject (lead, contact, opportunity). For "deal stagnant → create follow-up task" hygiene automation. |
| Delete Salesforce Record | Generic delete for any SObject. Irreversible at the API level (though Salesforce keeps in Recycle Bin for 15 days). For GDPR compliance or cleanup workflows. |
| Get Salesforce Record | Generic get by SObject and ID. Returns the record with selected fields. The standard lookup before update workflows. |
| List Salesforce Records | Paginated records of a specific SObject with filters. For "all opportunities in this pipeline" or "leads created since timestamp" sync workflows. |
| Salesforce SOQL Query | Runs a SOQL (Salesforce Object Query Language) statement. The power-user escape hatch for complex multi-object queries with relationships, aggregations, and filters that typed actions don't express. |
| Salesforce SOSL Search | Runs a SOSL (Salesforce Object Search Language) cross-object search. For "find all records mentioning this term across leads, contacts, accounts" workflows. |
| Update Salesforce Record | Generic update for any SObject. Partial update — only passed fields change. For "external system changed → reflect in Salesforce" sync patterns. |
Pre-built Salesforce workflows.
Clone any recipe and customize it in one click. Every recipe is fully editable.
Three things worth knowing.
Tiny Command counts a run the moment a trigger fires. Filtering early means only matching events spend your usage budget.
Connect Salesforce once and every workflow on your account can use its triggers and actions. You don't have to re-auth per workflow.
Every Salesforce field shows up in the visual picker for downstream nodes. The raw payload is there for power users, optional for everyone else.
Questions about the Salesforce integration.
If we missed yours, ping support. We usually reply within an hour.
How do I connect Salesforce to Tiny Command?
What Salesforce triggers does Tiny Command support?
What Salesforce actions can I run from a workflow?
Is the Salesforce integration real-time?
Do I need to write code to use Salesforce with Tiny Command?
How much does the Salesforce integration cost?
More crm & sales apps people connect.
Same category as Salesforce, ordered by how often teams pair them. Hover the carousel to pause.
Do more with Salesforce.
Wire it to Slack, Notion, HubSpot, Stripe, or any of the other 438 apps in our catalog. Setup takes roughly two minutes. Free to try, no credit card.
