Coralogix currently provides 2 triggers that can start a workflow and 10 actions a workflow can run. Use those building blocks to move information into the same workspace as the people, records, and next steps it affects.
New Alert Event
Triggers when Coralogix sends an alert-event webhook payload to this flow.
New Incident
Triggers when a new incident appears in Coralogix. Polls on a schedule — ideal for paging on-call, creating Jira tickets, or posting to Slack.
Send Logs
Send a single log to Coralogix Log Ingestion API.
List Incidents
Retrieve a filtered list of Coralogix incidents.
Acknowledge Incidents
Acknowledge one or more Coralogix incidents by incident ID.
Resolve Incidents
Mark one or more Coralogix incidents as resolved.
Close Incidents
Close one or more Coralogix incidents (e.g. false positives or noise). Use Resolve for incidents that were actually fixed.
Assign Incidents
Assign one or more Coralogix incidents to a specific user.
Get Incident By ID
Retrieve a Coralogix incident by its incident ID.
Get Incident Events
Get related events for a specific incident.
Enable / Disable Alert
Enable or disable a Coralogix alert definition. Use this to mute alerts during maintenance windows.
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 Coralogix event, then create or update the appropriate CRM, project, or custom record with the source context preserved.
Starts with
New Alert Event
Finishes with
Create or update a Coherence record
Use a change in Coherence to run a supported Coralogix 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
Send Logs
Combine Coralogix with another integration and Coherence records to move information into the same workspace as the people, records, and next steps it affects.
Starts with
New Alert Event
Finishes with
Send Logs, then preserve the outcome in Coherence
The exact authentication fields depend on Coralogix. The workflow structure stays straightforward:
Authorize the Coralogix 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 Coralogix or provide a complementary trigger or action.
Coralogix currently provides 2 triggers that can start a workflow and 10 actions a workflow can run. Use those building blocks to move information into the same workspace as the people, records, and next steps it affects.
Coralogix currently lists 2 triggers and 10 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 Coralogix 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.
