IT service management software for ticketing, asset management, and IT operations.
Freshservice currently provides 4 triggers that can start a workflow and 5 actions a workflow can run. Use those building blocks to connect support activity to the full account history and the next internal action.
New Ticket
Triggers when a new ticket is created in Freshservice.
Updated Ticket
Triggers when an existing ticket is updated in Freshservice.
New Requester
Triggers when a new requester (user) is created in Freshservice.
Updated Requester
Triggers when an existing requester is updated in Freshservice.
Create Ticket
Creates a new ticket in Freshservice.
Add Note to Ticket
Adds a private or public note to an existing ticket.
Create Requester
Creates a new requester (end user) in Freshservice.
Request Ticket Approval
Requests approval for a ticket from a specified agent.
Custom API Call
Make a custom API call to a specific endpoint
These recipes are generated from the triggers, actions, and categories currently available for this piece. Use them as starting points, then choose the exact fields, conditions, and records your workflow should update.
Start from a supported Freshservice event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Ticket
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Freshservice action, so the next step follows the record instead of relying on someone to copy it.
Starts with
A Coherence record or workflow changes
Finishes with
Create Ticket
Combine Freshservice with another integration and Coherence records to connect support activity to the full account history and the next internal action.
Starts with
New Ticket
Finishes with
Create Ticket, then preserve the outcome in Coherence
The exact authentication fields depend on Freshservice. The workflow structure stays straightforward:
Authorize the Freshservice account and permissions the workflow needs.
Select one of the current triggers or actions listed above and map its fields.
Run a small test, inspect the result in both systems, and only then enable the workflow.
Explore apps that share a category with Freshservice or provide a complementary trigger or action.
Freshservice currently provides 4 triggers that can start a workflow and 5 actions a workflow can run. Use those building blocks to connect support activity to the full account history and the next internal action.
Freshservice currently lists 4 triggers and 5 actions in the integration catalog. The supported list is refreshed from the pieces available in Coherence, so review the capability names on this page before building a workflow.
Yes. A workflow can combine supported Freshservice triggers or actions with Coherence records and other available integrations. The exact flow depends on the authentication, permissions, triggers, and actions exposed by each connected app.
The listed triggers and actions are designed for visual workflows. If the pre-built integration does not expose a capability you need, HTTP and webhook steps can cover APIs that your team is authorized to use.
Start automating in minutes. No credit card required.
