Case channels
Create in a service desk the address another system uses to open cases, and the URL where Elion ITSM notifies it of replies.
A case channel is the door through which another system (your product's support form, your website, a chatbot) creates cases in a service desk. Each channel has:
a URL to create cases, which identifies your company and the desk;
an inbound secret, which your system uses to sign what it sends;
optionally, an outbound URL (webhook) in your system, where Elion ITSM notifies you when the team replies, changes the status or resolves, and an outbound secret so your system can verify those notifications.
A desk can have up to 10 channels, one per system that connects.
Before you start
You must be the desk's Lead, or have Administer in Desks, groups, rules, categories, services and organization.
The desk must be a service desk (MDA, ESM or CSM).
If you are going to receive notifications, have your system's URL that will receive them ready. It must be
https://and reachable from the internet.
Create a channel
Open the desk and go to Settings.
Open the Case channels tab.
Click New channel and fill in:
Field
What to enter
Name
To recognize it, for example "My product's support form".
Outbound URL (webhook, optional)
Your system's URL that receives the notifications. If you leave it empty, the requester receives the normal Elion ITSM emails.
Events
Which notifications to send: Team reply, Status change, Resolved, Closed and Satisfaction survey.
Case defaults
Type, Group, Category, Service, Impact and Urgency that cases get if the request does not specify them.
Who can open cases
Create the requester if they don't exist, Registered requesters only or Only emails from these domains (with Allowed domains).
Save. A window appears with the URL to create cases (POST), the Inbound secret and, if you entered an outbound URL, the Outbound secret.
Copy them with the Copy buttons and give them to the development team through a secure channel. Click Done, I've copied them.
The URL and secrets are shown only once. If you lose them, rotate the secret: new ones are generated.
Manage a channel
In the list you see, per channel, whether it is active, which domain it sends notifications to, when it received the last case, when it sent the last notification and the last error. The actions are:
Action | What it does |
|---|---|
Edit | Changes the name, outbound URL, events, defaults and who can open cases. If you set an outbound URL for the first time, its secret is shown. |
Pause / Enable | When paused, the URL rejects new cases and no notifications are sent. |
Test outbound | Sends a test notification ( |
Rotate inbound secret | Generates a new URL and a new secret. The previous URL stops working immediately; the previous secret stays valid for 24 hours. |
Rotate outbound secret | Generates a new secret. For 24 hours, notifications carry both signatures, the new one and the previous one. |
View deliveries | Shows the last 50 notifications sent with their status: queued, retrying, delivered, failed or skipped. |
Delete | Removes the channel. Its URL stops working. Cases already created stay in the desk. |
What happens to the cases
They enter the channel's desk like any ticket, with the source API, and follow the desk's assignment rules, SLA and notifications.
The requester is looked up by email. If they do not exist and the channel allows it, they are created as a requester, without a password.
If the case includes the requester's company, it is linked to the account with that RUT or name, and the account is created if it does not exist.
If the channel has an outbound URL, Elion ITSM does not send emails to the requester: your system notifies them. The case's watchers do receive email.