By connecting the action builder to external systems, such as Confluence, admins can integrate Zendesk with external systems in automated workflows, improving collaboration and maintaining a seamless experience across multiple platforms.
The following example action flow automatically creates an incident report in Confluence
when a Zendesk ticket is determined to be an incident. Automating these actions ensures
immediate visibility for engineering, consistent documentation of incidents, and clean
handoffs between teams working together to resolve the incident.
- Add an action flow trigger with the following details:
- Click Add trigger.
- In the step sidebar, under Zendesk, click Tickets.
- Click Properties and select Ticket type changed.
- Click Add condition.
- Under Variable, select Ticket type changed and Type.
- Set the Operator to Is.
- Under Value, enter Incident.
- Add a step to look up ticket details:
- In the action builder, beneath the action flow trigger, click the Add
step icon (
). - In the step sidebar, under Zendesk actions, click Look up ticket.
- Under Ticket ID, click into the field and then click Select a variable instead.
- In the variable menu, select Ticket assignment changed as the step that output the variable you want to use, and then select Ticket ID.
- In the action builder, beneath the action flow trigger, click the Add
step icon (
- Add a step to look up user details about the ticket assignee:
- In the action builder, click the Add step icon (
). - In the step sidebar, under Zendesk actions, click Look up user.
- Under User ID type, select Zendesk user ID.
- For User ID, click Add variable.
- In the variable menu, select Look up ticket as the step that outputs the variable you want to use, and then select Requester ID.
- In the action builder, click the Add step icon (
- Add a step to lookup details about the ticket requester's organization:
- In the action builder, click the Add step icon (
). - In the step sidebar, under Zendesk actions, click Look up organization.
- Under Organization ID type, select Zendesk organization ID.
- For Organization ID, click Add variable.
- In the variable menu, select Look up user as the step that outputs the variable you want to use, and then select Organization ID.
- In the action builder, click the Add step icon (
- Add a step that creates a Confluence page based on the information you collected
for the ticket, requester, and organization:
- In the action builder, click the Add step icon (
). - In the step sidebar, under External actions, click Confluence and then select Create page.
- Under Space, select the appropriate space from the connected account in which to create the page.
- Under Title, enter Incident report: and then click add variable.
- In the variable menu, select Look up ticket as the step that outputs the variable you want to use, and then select Ticket ID.
- Under Content, enter the templated content you want to capture
for all incidents. Include relevant ticket and user information as
variables from the Look up ticket, Look up user, and Look up
organization steps, respectively, to streamline the incident resolution.
In the following example, all variables are
italicized:
An incident was identified via the following Zendesk ticket: Ticket ID. **Incident owner** The following team member is serving as the incident owner: Ticket Assignee. They should be included in all decisions. **Summary** - Incident: Ticket Description - Status: Ticket Status ID - Reported by: Requester Name (Requester ID) - Reporter's Organization: Requester's Organization Name (Organization ID) - Reported at: Ticket Created at
- In the action builder, click the Add step icon (
- Click Save.
- Click Test to test the action flow.
- Click the options menu (
) and select Activate to begin using the
action flow to automatically create incident reports in Confluence.