BMC Helix ↔ Salesforce

BMC Helix to Salesforce Sync

Fully bidirectional synchronisation between BMC Helix ITSM incidents and Salesforce Service Cloud cases so IT and customer support teams always work from the same live record.

$89/month
0 min
manual entry
Real-time
on trigger
Pre-built
no code
Salesforce
?

When a customer raises a case in Salesforce Service Cloud, your IT team in BMC Helix ITSM has no visibility unless someone manually creates a matching incident and keeps it updated. In the other direction, when an IT incident is resolved, the Salesforce agent handling the customer case is often the last to know. This Integration Pack connects Salesforce Service Cloud and BMC Helix ITSM so cases and incidents stay in sync automatically. A new Salesforce case triggers a matching Helix incident with priority, description and contact details mapped across. Status changes, attachments and notes flow bidirectionally from that point - so customer-facing agents and IT engineers always see the same current state without manual handoff.

How it works

Watch the agent run, end to end

intellipaas · agent run
TRIGGER A new case is submitted in Salesforce Service Cloud with a subject, description and priority, a matching incident is generated in BMC Helix ITSM immediately with the same details.
01
An attachment is added to the Salesforce case and syncs to the corresponding Helix incident record automatically.
02
The status is changed in Salesforce from new to in progress, the Helix incident updates to reflect the change within seconds.
03
The incident status is updated in Helix to resolved, the linked Salesforce case closes automatically.
04
All status changes, attachments and updates are logged in both platforms with a full timestamped record.
Use case highlights

Why deploy this use case

Automatic incident creation

Every new Salesforce Service Cloud case automatically generates a matching BMC Helix ITSM incident with subject, priority and contact details - no manual ticket creation.

Bidirectional status sync

Status changes made in either Salesforce or Helix ITSM propagate to the other platform in real time so both teams always see the current state.

Attachment synchronisation

File attachments added to the Salesforce case are automatically synced to the linked Helix incident so IT engineers have every piece of supporting evidence.

Comment and note sharing

Work notes and comments flow bidirectionally so customer-facing agents and IT engineers share the full incident conversation without switching platforms.

Instant closure notification

Resolving the Helix incident automatically updates the linked Salesforce case so support agents know the moment IT closes the issue.

Full audit trail

Every case-incident pair is fully logged in both platforms with a timestamped trail of status changes, comments and attachments for audit and compliance teams.

See it in action

Bidirectional Incident and Case Sync Between Salesforce Service Cloud and BMC Helix ITSM

See how IntelliPaaS connects Salesforce Service Cloud and BMC Helix ITSM to sync cases and incidents bidirectionally, with status changes and attachments mirrored in real time across both platforms.

/connectors/salesforce
All Salesforce integrations
FAQ

Questions teams ask

How quickly can we get the BMC Helix to Salesforce Sync Integration Pack running?

Most teams are live the same day. Connect your Salesforce account, confirm the field mapping and the agent starts running against your own data. There is no infrastructure to provision and nothing to deploy.

Do we need to write any code?

No. The Integration Pack ships with the trigger, the agent logic and the actions already configured. Everything is adjusted from the IntelliPaaS dashboard, so your operations team can own it without waiting on engineering.

How often does data sync?

The agent runs on every qualifying event in Salesforce, so records land in the target system within moments rather than waiting for an overnight batch. You can also put the Integration Pack on a schedule or trigger a run by hand when that suits your process better.

What happens if a record fails to sync?

Failed runs are retried automatically, and anything still unresolved is held in a review queue with the full error trace attached, so nothing is dropped silently. Your team is alerted and can replay the record once the cause is cleared.

Can we customise the field mapping?

Yes. Every field the Integration Pack maps is editable, and you can layer on your own conditions, filters and transformations without leaving the Integration Pack.

Ready to take control of your integrations?

See how teams like yours are eliminating risk, accelerating time to value and simplifying complexity.