Edwin AI Freshservice Integration
Last updated – 14 September, 2026
Use the LogicMonitor Edwin AI Freshservice Integration to send, update, and correlate IT service tickets within your Freshservice environment. The integration supports bi-directional ITSM workflows, enabling Edwin AI to automatically create or update tickets based on alerts, incidents, and correlation logic, while also accepting inbound ticket updates when supported.
This integration supports outbound ticket actions using the ConnectWise REST API and includes field mapping, authentication requirements, and customizable ticket operations. Configure a Freshservice webhook, then configure actions and rules in Edwin AI to create automated responses, alert enrichment, and cross-platform incident correlation in real time.
This integration supports structured JSON payloads using the Edwin Common Event Format (CEF) to enrich event data.
Requirements for Configuring Edwin AI Freshservice Integration
To configure the Edwin AI Freshservice Integration, you need the following:
- A user with permissions to create webhooks in Freshservice
- A Freshservice API key
For more information, see Where do I find my API key? from Freshservice - An Edwin AI Client ID and Client Secret
For more information, see Edwin AI API Credentials Management.
Configuring Edwin AI Freshservice Webhook
- Create a Webhook in Freshservice.
For more information, see Using Webhooks with the Workflow Automator from Freshservice. - Include the following details in the webhook:
- client_id—Edwin API client ID
- client_secret—Edwin API client secret
- auth token URL (POST)—
https://${orgId}.dexda.ai/auth/token - endpoint URL (POST)—
https://${orgId}.dexda.ai/integration/Freshservice
Configuring Freshservice Integration Credentials in Edwin AI
- In LogicMonitor, navigate to Edwin AI.
- Select Settings > Integrations.
- Select Configure for Freshservice.
- In the Name field, enter a name the Freshservice integration.
- In the Description field, enter a short summary of the integration.
- Enter the following connection details from Freshservice:
- URL
- API Key
- Select Save.
Edwin AI includes Freshservice API credentials as part of outgoing payloads. Verify and manage integrations by selecting your configured integrations from the Integrations settings.
Configuring a Create Freshservice Alert Action
- Create a new Edwin AI Action.
For more information, see Creating and Editing Action in Edwin AI. - From the Source dropdown menu, select “FreshserviceTicket.”
- From the Add Action dropdown menu, select “Create Freshservice Ticket.”
- In the Mapped Fields section, add mapped fields to specify what information to include in the payload to Freshservice.
You can use the following supported fields:
| Freshservice Field | Data Type | Notes |
| id | string | Present in response, generated by Freshservice |
| subject | string | Required in request body |
| description | string | Required in request body |
| status | integer | 2=Open, 3=Pending, 4=Resolved, 5=Closed |
| priority | integer | 1=Low, 2=Medium, 3=High, 4=Urgent |
| impact | integer | 1=Low, 2=Medium, 3=High |
| urgency | integer | 1=Low, 2=Medium, 3=High |
| source | integer | Specifies the channel. For example, 1=Email. |
| url | string | Present in response, constructed by backend |
| string | Required in request body (if requester_id is not set). User entity must have been created first in Freshservice instance. | |
| resolution_notes | string | Mandatory when trying to resolve or close a ticket. |
| group_id | integer | Group entity must have been created first in Freshservice instance. |
| wourkspace_id | integer | Workspace entity must have been created first in Freshservice instance. |
| requester_id | integer | Required in request body (if email is not set). User entity must have been created first in Freshservice instance. |
| publicnote | string | Internal custom field to add a conversation through the Update path. |
- Select Submit.
Edwin AI creates a new ticket in Freshservice with details from the Mapped Fields whenever Edwin AI generates a new alert.
Note: You can use these steps to create an Edwin AI action that updates existing Freshservice tickets when a corresponding Edwin AI alert changes status.


