FR
EN
ES
IT
DE
PT-BROne automation engine.
All your data.
In HOP, automations, also known as workflows, are not siloed by function. They apply to all your entities, standard and custom.
Talk to a certified integratorOne engine for the whole platform
In HOP, automation does not stop at module boundaries. The engine applies to all your entities. Contacts, deals, tickets, invoices, among others. And your custom entities too, without any restriction.
No matter who changes the data
the engine reacts the same way.
One mechanism, no special cases.
Triggers for every situation
Field change
Any change to any field, on any entity, can trigger an automation.
Scheduling
An automation can run at regular intervals. Example: overdue invoice reminders can run every night.
API call
Your external systems launch an automation directly.
Business processing
A business rule triggers an automation.
The trigger opens the door. The condition decides.
Each automation can carry entry conditions. Example: a deal status changes. The automation only runs if the new status is "signed". The sales rep is then notified.
For the "field change" trigger, every initiator is taken into account: a logged-in user, an API, a business rule, another automation. The initiator type can itself be used as a condition. Example: an in-app notification is only sent if the initiator is a logged-in user.
What an automation can do in HOP
Once triggered, an automation chains the actions of your choice.
Act on data
Update fields, increment a value, change a status, add or remove a tag.
Create linked items
A task, a note, a deal. Any item linked to the entity concerned.
Communicate
In-app notification, Slack message, email or SMS.
Talk to your systems
The automation calls an external service.
Orchestrate
Internal conditions, pauses, chaining, stopping an automation.
Launch an AI task
Any AI task in HOP can be run by an automation.
AI and automations work both ways
An automation can launch an AI task. And when an AI task writes a result to a field, that change can trigger an automation.
Automations in action
The signed deal
A deal status changes.
The new status is "signed".
An automation notifies the sales rep in the app.
Invoice reminders
Every night, an automation checks overdue invoices.
A reminder is sent.
Three reminders at most, then the automation stops.
The urgent message
The AI detects an urgent incoming message and updates the urgency field.
This change triggers an automation.
A ticket is created, the team is alerted on Slack.
Cart abandonment
A cart is abandoned.
The automation sends a discount coupon, then waits three days.
If the cart converts, it stops. Otherwise, it offers free shipping.
In HOP, automation is not a black box
Every operation performed by an automation is logged, exactly like one performed by a user or an API.
Who directly triggered
Each run records the initiator that directly triggered the automation.
Who started the chain
When automations chain together, you can always trace back to the source.
Your automated processes remain auditable end to end.
Designed with your integrator
Your automations are designed by your certified integrator. They know your processes and evolve them with your organization. You describe your business, they set it in motion.
Automate what slows you down
Discover what the HOP automation engine can do for your organization.
Talk to a certified integrator