Integration delivery
Configure supported Slack, Microsoft Teams, and HTTPS webhook destinations, then interpret queued, attempted, accepted, uncertain, and failed receipts.
On this page
Task and prerequisites
Use this guide to configure a supported event destination or investigate a failed handoff. You need authorized workspace integration settings, the destination administrator's approval and a supported destination type.
Review any required webhook or channel credentials inside the protected setup; never send them through public contact forms. Generic integration delivery and action-specific ticketing have different capability boundaries.
Supported delivery model
Configured Slack, Microsoft Teams, and HTTPS webhook destinations receive allowlisted event summaries through tenant-scoped delivery records.
Security and retry state
Webhook delivery rejects unsafe destinations and records bounded customer-safe failures. A queued or attempted delivery is not a confirmed receipt.
Destination-specific limits
Generic event delivery does not imply every action-specific Jira, ticketing, SIEM, or chat workflow is implemented. Check the current integration screen before relying on a destination.
Steps and expected result
Open the relevant integration, confirm its destination and event scope, and inspect the allowed summary before using the supported test or send control. Review the resulting receipt and the destination's current status.
A successful preview sends nothing. A queued or attempted record does not establish receipt, and HTTP acceptance does not prove a person read the message.
Review links still require normal sign-in and current access to the referenced record.
Limitations and troubleshooting
Follow the safe failure category and retry guidance. If the outcome is uncertain or marked no-resend, inspect the destination before trying again because it may already have accepted the request.
A dead letter records failed delivery needing review; it does not resolve the source finding. Jira Service Management Cloud needs its own configured workflow.
Linear, Azure DevOps and SIEM labels are not evidence of identical dispatch support. Ask support with the receipt reference and safe summary, without tokens, payloads or raw external errors.