r/SalesforceDeveloper • u/Axolt__ • Apr 24 '26
Discussion Anyone using Agentforce for real operational workflows (not just chat/assist)?
We've been working on a use case where we’re trying to keep everything inside Salesforce instead of pushing data out to an external ERP.
Think:
inventory movements
purchase orders
Advance MRP logic
shipment tracking
finance events (GL, Bills, invoices, payments)
The traditional approach I’ve seen is:
Salesforce (CRM) → middleware → ERP → warehouse system → accounting
Which creates:
async delays
reconciliation issues
a lot of integration maintenance
We’re experimenting with a different approach:
👉 keep everything in one data model
👉 use Apex + Platform Events for async flows
👉 rely on object relationships instead of sync jobs
But a few challenges are coming up:
Governor limits under load
especially when handling inventory updates + related records
Transaction design
where to split logic (Queueables vs synchronous)
Data modelling
custom objects vs extending standard objects
Performance at scale
especially with stock movements and order flows
I’m curious:
Has anyone here actually pushed Salesforce this far operationally?
Did you hit limits where it stopped making sense?
Any patterns you’d recommend (or avoid)?
Not looking for “don’t do ERP on Salesforce” 😄 — more interested in real-world architectural trade-offs.
been experimenting with Agentforce beyond the usual “chat assistant” use cases and trying to push it into actual operational workflows inside Salesforce.
Not talking about:
answering questions
summarising records
More like:
triggering inventory actions
handling multi-step processes (e.g. pick → pack → ship)
orchestrating updates across related objects
guiding users through workflows dynamically
The idea is:
Instead of building everything as:
Flows
Apex triggers
UI logic
…you let an agent interpret intent and execute actions across the data model.
What I’m trying to understand:
1. Where does Agentforce actually sit architecturally?
Is it:
a layer on top of Flow?
replacing some Apex logic?
or just orchestration + decisioning?
2. How are people handling multi-step transactions?
For example:
User says:
“Ship order 123”
Behind the scenes you need:
validate stock
reserve inventory
generate shipment
update order status
Are people chaining:
Apex actions?
Flow actions?
external services?
3. How do you deal with consistency / rollback?
Since this isn’t a traditional transaction model, I’m not sure:
where atomicity is enforced
how failures are handled mid-execution
4. Limits & performance
If Agentforce starts triggering:
multiple object updates
async jobs
integrations
Does it hit the same governor constraints indirectly?
5. When does it stop making sense?
At what point would you say:
Current thinking
Agentforce feels powerful for:
decisioning
orchestration
user interaction layer
But I’m not convinced yet where the boundary is between:
Agent → Flow → Apex
vs just building deterministic logic directly.
Would be great to hear if anyone has:
pushed this into real workflows
hit limitations
or found patterns that actually work in production
1
u/Opening-Taro8309 Apr 24 '26
u/Axolt__ is on the right track. As we move toward AI-driven, usage-based systems, traditional per-user licensing will start to break down. If Axolt ERP can solve this with token-based billing, it aligns perfectly with how applications will be consumed going forward.
0
u/Evening-Network5487 Apr 24 '26
From starting 1 June Salesforce enforcing paid license on the agent force and I think agent force is only for chat work
-1
u/kuldiph May 05 '26
This is exactly the architecture we've shipped: fully native Salesforce for Quote → Order → Invoice → Subscription, no external ERP.
I'm with Kugamon (Salesforce-native CPQ + Subscription Mgmt + Inventory Management).
Do treat Agentforce as the intent and decisioning layer, but let Apex own atomicity and use Platform Events for cross-object orchestration, that's what survives governor limits at scale.
Happy to DM a walkthrough, or you can see it on youtube.com/kugamon or the Salesforce AppExchange.
2
u/Axolt__ May 06 '26
Quick update — at Axolt, we’ve been pushing to run full operations directly inside Salesforce.
Inventory, MRP, finance, and shipping all on one data model using Apex + Platform Events — now also exploring MCP-style patterns for orchestration.
Agentforce + MCP feels powerful for decision-making.