Workflow Rules are retired
Support ended on 31 December 2025, though existing rules still run. We build on Flow and tell you where call logic is sitting in something that will not be maintained.
Integration · Orum to Salesforce
Orum and Salesforce integration
Orum lets a rep have several conversations in the time one used to take. Salesforce has to record them without anyone typing. We connect the two and build the automation on what Salesforce actually supports now, not on the Workflow Rules your org is probably still carrying. It is a one-time setup by our team, not a monthly middleware subscription.
- From $100, one-time setup
- No monthly fees from us
- Tested on your own calls before go-live
Orum
Salesforce
One call ends in Orum. In Salesforce:
- A list is pushed to OrumFrom the view or campaign you choose
- A real person answersOrum bridges the rep in
- Logged as a call on the recordContact, lead or opportunity
- One-time setup
- From $100
- Monthly fee from us
- $0
- Working days to a written scope
- 2
- Working days to build and test
- 5–10
Got it, thank you.
Check your inbox for a confirmation. We will reply within 2 working days with what we would do and what it would cost.
Building this on automation that has a future
Salesforce stopped supporting Workflow Rules and Process Builder at the end of 2025. Existing ones still run, which is why so many orgs still have them, and it is also why a new integration built to fire them is building on sand. Anything we add here is built with Flow, and where we find call logic sitting in a retired automation we say so rather than layering on top of it.
The rest is arithmetic. A parallel dialer produces far more records than a rep dialing one at a time, and an org on Enterprise allows 500 custom fields per object — 800 on Unlimited — with field history tracking limited to 20 fields per object without Field Audit Trail. Create a field per disposition and you will spend both. And with three major releases a year, an integration that depends on undocumented behaviour is a maintenance bill. We keep the footprint small on purpose.
- SDR teams on SalesforceA view becomes a dial list and the conversations come back as calls.
- Orgs modernising their automationCall logic is built on Flow, not added to retired Workflow Rules.
- Teams with tight field governanceOutcomes written into few fields, not one per disposition.
What we connect between Orum and Salesforce
A typical setup. We adjust each line to how your team uses Orum and Salesforce.
When this happensThis is what you get
A Salesforce view or campaignPushed to the Orum list for the rep who owns it
A call connects to a live personA logged call on the matching contact, lead or opportunity
The call outcomeThe field you choose, with the Flow that should follow it
A voicemail, screener or phone treeLogged as an attempt, not as a conversation
A callback requestA task for the record owner at the agreed time
A bad numberFlagged on the record so it leaves the view and the dial list
Field mapping, event by event
Each Orum event and exactly what it writes in Salesforce. Pick an event to see its fields.
1. Trigger · Orum
When a call ends
Every call made or received in Orum
2. Action · Salesforce
Log the call
In Salesforce, on the contact or lead — Where your team already works
Salesforce field
Mapped from
What happens
Activity date
Call time15 Sep, 4:00 pm
Shown in your time zone
Call time15 Sep, 4:00 pm
Shown in your time zone
Call length
Call length3 min 04 s
Stored the way Salesforce expects
Call length3 min 04 s
Stored the way Salesforce expects
Call outcome
Call outcomeInterested
Matched to your own list of outcomes
Call outcomeInterested
Matched to your own list of outcomes
Recording
Call recordingPlayable audio
Added once the file is ready
Call recordingPlayable audio
Added once the file is ready
Call notes
Call notesAsked for pricing
Saved as note text
Call notesAsked for pricing
Saved as note text
Owner
Rep nameMaria Lopez
Matched to the same person in Salesforce
Rep nameMaria Lopez
Matched to the same person in Salesforce
Contact or lead
Matched by phone number+1 415 555 0142
A new contact or lead is created only if none match
1. Trigger · Orum
When an outcome is set
A rep marks how the call went
2. Action · Salesforce
Update the opportunity
In Salesforce — Moves one record, not all of them
Salesforce field
Mapped from
What happens
Which opportunity
Most recent open opportunityNorthwind — 12 seats
On the matching contact or lead, owned by the rep on the call
Stage
Call outcomeInterested
Looked up in the outcome-to-stage list we agree with you
Call outcomeInterested
Looked up in the outcome-to-stage list we agree with you
1. Trigger · Orum
When a voicemail is left
Nobody picked up in time
2. Action · Salesforce
Create a task
In Salesforce, for the contact or lead owner — A call-back nobody forgets
Salesforce field
Mapped from
What happens
Title
Caller number+1 415 555 0142
“Call back” plus the contact or lead name, or the number if unknown
Caller number+1 415 555 0142
“Call back” plus the contact or lead name, or the number if unknown
Due
Your follow-up windowWithin 1 hour
Set to how fast your team calls back
Assigned to
Contact or lead ownerMaria Lopez
Falls back to the rep who was on the line
Contact or lead ownerMaria Lopez
Falls back to the rep who was on the line
Sample values are made up. The exact fields are agreed with you in your scope.
A one-time setup, not a monthly middleware bill
We are not a middleware. We plan the connection, set it up, test it on your calls and hand it over.
Web Repay integration setup
Middleware subscription
What you pay
One-time setup, from $100 (one-off)
A monthly plan, often priced by tasks or operations
As call volume grows
The same price, no per-task charges
Costs rise with every call that syncs
Who builds and tests it
We do, on your own Orum calls
Your team builds and maintains every step
Where it runs
In your own Orum and Salesforce accounts, documented
Inside the middleware vendor’s platform
When something changes
Additional support as needed, when you request it
Your team fixes the broken steps
Where a small connector layer is the most reliable route, we say so in your written scope, set it up in your own account and choose the option with the lowest running cost.
Where Orum and Salesforce setups usually go wrong
Fields are finite
Enterprise allows 500 custom fields per object and Unlimited 800, and field history tracks only 20 fields per object without Field Audit Trail. We write outcomes into a small set of fields rather than one per disposition.
Attempts are not conversations
Parallel dialing produces many more attempts than calls. Only bridged conversations create a logged call; the rest are recorded quietly so the activity timeline stays readable.
Three releases a year
Salesforce changes three times a year. We keep to supported behaviour and document what the integration depends on, so an upgrade is not an incident.
How we set it up
- 1
Agree what connects
Which views or campaigns feed the dialer, which outcomes are logged and which trigger a Flow, and what the field footprint will be. You get a written scope with a fixed one-time price.
- 2
Access for the setup
A Salesforce user with a profile and permission set covering the objects involved, and admin access to Orum.
- 3
We connect and test
We push a test list, take and reject calls ourselves, and check every logged call, field, task and Flow — in a sandbox first where you have one.
- 4
Handover
A short document of what is connected, including the fields and Flows it touches. It runs in your own accounts, with no monthly fee from us.
Test call passedEvery field in the table checked
LiveWatched for the first week
What it costs
From
$100 one-time setup
Starting price for connecting Orum and Salesforce, built and tested. Larger mappings get a fixed quote in writing before we start.
No monthly fee from us. Additional support is available as needed, whenever you request it.
Free download
The integration health check
10 checks to make sure your website, CRM and dialer really are passing information between them.
From the blog
Further reading
Integrations
How to log every call from your dialer in your CRM
Every call on the right contact, with the outcome, the rep and the recording, and nobody typing notes afterwards. What to connect, how to match callers, and what to test.
CRM
Why your CRM is full of duplicates, and how to stop new ones
Duplicates come in through forms, imports, integrations and manual entry. Here is how to clean up what is there, and close the doors so they do not come back.
Dialers
Why fewer people answer your calls: spam labels and caller ID
When answer rates drop, the cause is often a warning label on your caller ID. How US carriers check and label calls, and what you can do about it.
Questions about Orum and Salesforce
Can Orum dial a Salesforce list view?
Yes. The view or campaign you choose becomes the dial list for the rep who owns it, and conversations are logged back on the matching records.
Will this work with our existing Workflow Rules?
They still run, but Salesforce stopped supporting Workflow Rules and Process Builder at the end of 2025. We build new logic in Flow and flag any call automation still sitting in the retired tools.
Does every dial attempt create a task or a call record?
No. Only bridged conversations are logged as calls. Voicemails, screeners and phone trees are recorded as attempts so the timeline stays usable.
Is there a monthly fee?
No. You pay once for the setup. Unlike Zapier, Make and similar middleware subscriptions, there is no monthly or per-task charge from us. Your Salesforce and Orum plans are unchanged.
Rather talk it through?
Thirty minutes on how your team uses Orum and Salesforce. You leave knowing what we would build and what it would cost.
Call ended03:04 · inbound
Opportunity updatedMeeting booked
Call-back taskAssigned to the contact owner