Skip to content
Documentation
Contact
← Back to documentation
Technical Reference

Coralogix

Coralogix integration for Flows360 workflows.

CategoryOther
Authenticationcustom
Version0.2.0
Published scopes0 published scopes
Last updatedSeptember 19, 2026

Overview

Connect Coralogix with Flows360

Coralogix integration for Flows360 workflows.

Use the Coralogix connector to include its declared actions and events in Flows360 workflows without duplicating the integration logic inside each consuming system. This pinned connector version currently exposes 10 actions and 2 triggers.

Available actions

  • Send Logs
  • List Incidents
  • Acknowledge Incidents
  • Resolve Incidents
  • Close Incidents
  • Assign Incidents
  • Get Incident By ID
  • Get Incident Events
  • Plus 2 additional declared actions.

Available triggers

  • New Alert Event
  • New Incident

The capability list above is generated from the exact reviewed connector package so the public description stays aligned with the version Flows360 operates.

Technical guide

Technical reference

Package identity

  • Connector: Coralogix
  • Package: @activepieces/piece-coralogix@0.2.0
  • Exact artifact digest: sha256:058f781405b6e11ace0563b3d91c40309c9b46ff348f754c46911bc4cfbfda5b
  • Runtime: Activepieces-compatible deterministic worker
  • Source: the exact reviewed Activepieces source

Authentication

CUSTOM AUTH. Connection values are tenant-specific and remain in the consuming Studio instance; CDK stores definitions and field metadata, not customer credential values.

Action contracts

  • Send Logs (sendLogs), Send a single log to Coralogix Log Ingestion API. Classification: read.
  • List Incidents (listIncidents), Retrieve a filtered list of Coralogix incidents. Classification: read.
  • Acknowledge Incidents (acknowledgeIncidents), Acknowledge one or more Coralogix incidents by incident ID. Classification: read.
  • Resolve Incidents (resolveIncidents), Mark one or more Coralogix incidents as resolved. Classification: read.
  • Close Incidents (closeIncidents), Close one or more Coralogix incidents (e.g. false positives or noise). Use Resolve for incidents that were actually fixed. Classification: read.
  • Assign Incidents (assignIncidents), Assign one or more Coralogix incidents to a specific user. Classification: read.
  • Get Incident By ID (getIncidentById), Retrieve a Coralogix incident by its incident ID. Classification: read.
  • Get Incident Events (getIncidentEvents), Get related events for a specific incident. Classification: read.
  • Enable / Disable Alert (setAlertActive), Enable or disable a Coralogix alert definition. Use this to mute alerts during maintenance windows. Classification: read.
  • Custom API Call (custom_api_call), Make a custom API call to a specific endpoint Classification: read.

Trigger contracts

  • New Alert Event, webhook.
  • New Incident, polling.

Verification

Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Capability summary

Authenticationcustom
Supported objects12
Supported actionsNot published
Triggers2

Authentication

Authentication method: custom

Authentication profiles

connection · custom
  • Personal/Team API Key Required · protected credential
  • Send-Your-Data API Key Optional · protected credential
  • Ingestion Region Domain Required

Supported objects

ObjectReadWriteNotes
Send Logs Yes No Send a single log to Coralogix Log Ingestion API.
List Incidents Yes No Retrieve a filtered list of Coralogix incidents.
Acknowledge Incidents Yes No Acknowledge one or more Coralogix incidents by incident ID.
Resolve Incidents Yes No Mark one or more Coralogix incidents as resolved.
Close Incidents Yes No Close one or more Coralogix incidents (e.g. false positives or noise). Use Resolve for incidents that were actually fixed.
Assign Incidents Yes No Assign one or more Coralogix incidents to a specific user.
Get Incident By ID Yes No Retrieve a Coralogix incident by its incident ID.
Get Incident Events Yes No Get related events for a specific incident.
Enable / Disable Alert Yes No Enable or disable a Coralogix alert definition. Use this to mute alerts during maintenance windows.
Custom API Call Yes No Make a custom API call to a specific endpoint
New Alert Event Yes No webhook trigger declared by the pinned package.
New Incident Yes No polling trigger declared by the pinned package.

Triggers

New Alert Event · Webhook

Triggers when Coralogix sends an alert-event webhook payload to this flow.

Inputs

  • setupInstructions · string
New Incident · Poll

Triggers when a new incident appears in Coralogix. Polls on a schedule u2014 ideal for paging on-call, creating Jira tickets, or posting to Slack.

Inputs

  • severity · array

Setup

Setup

  1. Add the Coralogix connector to the workflow in the target Flows360 Studio instance.
  2. Create or select the tenant-specific connection required by the connector. Connection secrets remain in the Studio connection boundary and are not copied into CDK documentation.
  3. Provide the connection fields declared by the pinned package:
  • Personal/Team API Key (personalOrTeamApiKey), required; stored as a sensitive connection value.
  • Send-Your-Data API Key (sendYourDataApiKey), optional; stored as a sensitive connection value.
  • Ingestion Region Domain (coralogixDomain), required.
  1. Select the required action or trigger and complete its declared input fields. Required and optional inputs are defined by the exact package schema.
  2. Test the workflow in the appropriate environment before enabling production scheduling or event delivery.

Limitations

Limitations and operational notes

  • This content describes @activepieces/piece-coralogix@0.2.0; provider behaviour can change independently and should be revalidated when the provider or connector version changes.
  • Only the 10 actions and 2 triggers declared by this pinned package are represented here.
  • Tenant credentials and connection values are not stored in the public connector record.
  • Provider-side permissions, account entitlements, quotas and rate limits remain subject to the connected provider account and are not inferred when the package does not declare them.
  • Deterministic execution evidence is recorded for the pinned artifact, including 1 exercised action entrypoint and 0 exercised trigger entrypoints.

Troubleshooting

Why canu2019t the connector authenticate?

Check the tenant connection in Studio and confirm every required Coralogix connection field is present. Re-authorise OAuth-based connections if the provider token or consent has expired. Do not place credential values in CDK content or logs.

Why is an action or trigger unavailable?

Confirm that the workflow is using @activepieces/piece-coralogix@0.2.0 and compare the requested capability with the declared action and trigger list for this version. A capability that is not declared by the pinned package should not be presented as supported.

What should I check after a provider-side change?

Revalidate authentication, required fields, action/trigger behaviour and provider documentation before publishing refreshed connector content or moving a new package version into production.

github.com