Connect Salesforce or HubSpot, route records with an Agent Identifier, and build CRM workflows in Julian.
Connect Salesforce or HubSpot once, subscribe records to the correct agent with an Agent Identifier, build CRM
behavior in Workflow Builder, and inspect each execution in Run History. Everything on this page works the same way
for either CRM.
Your CRM also needs setup on its own side — a user, permissions, and object access. Complete that before the
Connect step below: Salesforce, or the HubSpot setup
guide for HubSpot’s private app.
Open Integrations in Julian. Before a CRM is connected, Salesforce and HubSpot each display a Connect button.To connect Salesforce:1. Start the connection. Select Connect beside Salesforce.2. Enter your Salesforce subdomain. Enter the part before .my.salesforce.com, then select Next.3. Authorize Salesforce. Complete the Salesforce authorization flow.4. Finish the installation. Return to Integrations and open Salesforce to configure the integration.After authorization, Salesforce displays Integration Not Installed until you map at least one Agent Identifier
field or enable write permission for at least one CRM object.Complete the Agent Identifier and write-permission setup in the next section. Once the installation configuration is
saved, Salesforce appears as connected on the Integrations page.A green status and a Connected button confirm the completed installation. The connection is shared across the
organization rather than created separately for each agent.
Use an Agent Identifier when CRM field changes should start a sequence for a specific Julian agent.
Open the connected CRM from Integrations.
Under Schedule, choose the CRM field that stores the Agent Identifier for each supported object.
Use the matching Agent Identifier value on the agent’s pre-sequence workflow.
Under Push, enable the CRM objects that Julian may write to.
The Agent Identifier belongs to subscription routing. Ordinary Search CRM and Write to CRM nodes do not
require it. Within an organization, one Agent Identifier value routes to one workflow for each CRM provider and
record type.
Use Search CRM to look up one record by Record ID or field filters, choose the fields to return, and use found,
recordId, and record.<field> in later nodes.This pre-sequence example starts when the mapped CRM field changes, fetches contact details, checks the result, and
enrolls only records with the required fields.The Search CRM node below reads a Salesforce Lead by the Record ID from the workflow trigger and returns Phone and
Status.
Use Write to CRM to create a record, update an existing record by Record ID, or log a supported activity. In a
post-call workflow, a call activity can also include the recording.This post-call example searches for the Lead after analysis completes. When the Lead is found, it updates the CRM
record and logs the call activity with its recording. A missing record follows the safe no-op branch.The Update CRM Record node below uses the Record ID returned by Search CRM and maps the call summary to the Salesforce
Lead Description field.
Open Workflows → Run History to confirm that a workflow ran and review its overall status, version, trigger, start
time, finish time, and duration.The latest entry above is a completed Version 3 test run of the updated post-call workflow. No individual node is
selected, so the page shows the run-level summary.
Test runs execute real workflow actions. Use designated test data and safe branches when a workflow can update CRM
records, send notifications, call APIs, or schedule sequences.
