Hive’s native Salesforce integration connects your CRM to delivery work — so when an opportunity moves, an account updates, or a lead is created, Hive can create projects, create actions, assign owners, and run multi-step Workflows automatically.
Most teams use Workflows with a Salesforce event trigger for this. That is the recommended path for new Salesforce automations because you can combine CRM events with conditions and a full set of Hive steps (including Give Buzz a job).
Quick example
A services team keeps a templated onboarding project in Hive. New deals still close in Salesforce. Instead of a project manager manually copying the template:
They connect Salesforce in Hive Apps
They create a Workflow with trigger Salesforce event
Object: Opportunity · Trigger on: Updated
Condition: Stage equals Closed Won (or your onboarding stage)
Step: Create project from template (and optionally assign owners, add labels, or give Buzz a follow-up job)
When Salesforce updates that opportunity, Hive runs the workflow for them.
Step 1: Connect Salesforce
Open Apps in Hive.
Enable Salesforce.
Connect with one of these options:
Personal Salesforce — connect with your Salesforce login for personal triggers and automations.
Workspace Salesforce (admins) — configure a workspace API / Connected App connection for shared CRM sync, triggers, and Workflows.
Connection tip: Salesforce needs API access enabled, and PushTopic create permission for triggers. Hive’s Salesforce connection screen shows a connection-requirements checklist if something is missing. Salesforce editions with API access (commonly Enterprise, Unlimited, Developer, or Performance) are typically required.
Only one connected Salesforce setup is needed for data to flow. If workspace Salesforce API is active, Workflows use that shared connection; otherwise they use the personal OAuth connection.
Step 2: Create a Salesforce Workflow (recommended)
Use Workflows when you want Salesforce changes to start a repeatable process in Hive — not only create one project or action.
Enable Workflows in Apps (if it is not already on).
Open Workflows and create a new workflow.
Choose trigger Salesforce event (under System events).
Configure the Salesforce side:
Object type — Account, Campaign, Contact, Lead, Opportunity, or compatible custom objects available to your connected Salesforce user
Trigger on — Created, Updated, or both
Conditions (optional) — field rules that must match before the workflow runs (for example Stage equals Closed Won AND Amount is greater than 50000). Nested All / Any groups are supported.
Add one or more Hive steps, such as:
Create project from template
Create new action
Update assignees, status, labels, or custom fields
Give Buzz a job — for enrichment, routing, summaries, or multi-step follow-through
Notifications, email, Slack, or other available workflow operations
Save and enable the workflow.
For a deeper walkthrough of Workflow design patterns (including Salesforce → Hive intake), see Buzz Workflows.
Notes for Salesforce Workflows
Salesforce event is a standalone trigger — it cannot be combined with other triggers in the same workflow.
If workspace Salesforce API is enabled, only workspace admins can create Salesforce event Workflows.
If no conditions are set, the workflow runs on every matching Created / Updated event for that object.
Hive uses the Salesforce field names available in your org; available condition fields depend on your Salesforce configuration.
Step 3: Test
In Salesforce, create or update a record that matches your object, event, and conditions.
Confirm the workflow run in Hive (Workflows run history) and that the expected project, action, or Buzz step completed.
Alternative: Salesforce Triggers in Apps (simple project/action creation)
If you only need Hive to create a project or action when Salesforce criteria are met — and optionally sync selected Salesforce fields as Hive custom fields — you can still use the classic Salesforce Triggers UI:
Open Apps → Salesforce → Open.
Click + Add new trigger.
Configure In Salesforce (what to listen for) and In Hive (create a project or action, optional template, optional field sync).
Save the trigger, then test it from Salesforce.
To edit an existing Apps-page trigger, expand it on the Salesforce Triggers page and use Edit. Changes to Salesforce-side listen criteria may require deleting and recreating the trigger.
For multiple conditions and field sync details on this path, see Multiple conditions in Salesforce triggers.
Note: Projects created by a personal Salesforce trigger may start private to the person who set up the trigger — update sharing as needed. Template-based project creation follows the template’s visibility settings.
Optional: CRM sync
Separately from Workflows and triggers, you can enable Salesforce CRM sync from the Salesforce Apps modal to import accounts, contacts, and opportunities into Hive CRM (personal sync or workspace API sync). That import path is independent of automation triggers.
Common questions
Should we use Workflows or Salesforce Triggers?
Use Workflows + Salesforce event for new automations, multi-step processes, and Buzz-assisted handoffs. Use Salesforce Triggers in Apps when you want a simple create-project / create-action automation with optional field sync.
If the person who created a Salesforce trigger leaves, is it deleted?
No. Existing triggers remain. Prefer workspace Salesforce connections for shared, admin-managed setups.
Are Salesforce triggers and Workflows visible to others?
Yes — workspace members can see Salesforce triggers. Workflow visibility follows your Workflows permissions and workspace settings.
Can Workflows sync Salesforce fields as Hive custom fields the same way Apps triggers do?
Field sync rows are configured on the classic Salesforce Triggers path. In Workflows, use workflow steps (and Buzz, when helpful) to create or update Hive work from Salesforce event context.