Get task alerts where your team works

Semaphore supports SMTP email, Slack, Microsoft Teams, Telegram, Rocket.Chat, DingTalk and Gotify. Configure shared server channels or named project alerts for the destinations your team watches. Provider credentials can be referenced from the Key Store. Use the channel setup guide and send a test message before relying on delivery for scheduled operations.

Yes. Create named alerts in the project with the destinations and events you need. Task Templates can inherit the project defaults or select a custom set of alerts. This lets teams route different jobs to different channels while keeping the destination configuration reusable across templates. Schedules can inherit the template selection or override it.

Choose failure events for the relevant project alert. Task Templates also provide success and error suppression controls, so routine successful checks do not have to fill the team channel. Waiting-for-confirmation alerts are handled separately. Review both the destination event selection and template settings when deciding which results should produce a message.

Use Send test message for an individual project alert, or Test all to check the configured project destinations. Neither action needs to launch infrastructure automation. After confirming receipt, run a harmless task to check the actual event rules and the link back to its result. Repeat the test when changing credentials or webhook URLs.

Check that the destination is enabled, its credentials are valid, and the selected events include the task result. Review whether the template inherits project defaults, uses a custom alert set, or suppresses that result. For scheduled tasks, also check the schedule override. An empty custom selection can intentionally disable project-alert delivery for that job.

Named project alerts support Go template messages with task context, including a task URL and the trigger type. Use that context to help colleagues identify the job and open the execution record. Keep messages concise and avoid including sensitive values. The alert reports the event; incident ownership and escalation remain part of your team process.

Yes. Scheduled tasks use their configured alert selection, inherited from the Task Template or overridden on the schedule. A failed Ansible patching job, backup check or certificate renewal can bring the result to the team without someone watching the dashboard. Open the linked task to inspect its output and execution details.

Their supported events differ. Email task alerts report failures, while supported chat channels can also report success and waiting-for-confirmation events. Select the events relevant to each project destination and review template suppression settings. A notification is a route to the task evidence, rather than a replacement for inspecting the result or managing an incident.