pushinator_skill

Overview

This skill provides concise curl-based examples and guidance for sending push notifications with Pushinator. It focuses on practical steps: preparing a JSON payload, setting the Authorization header with your API token, and posting to the notifications endpoint. Use it to integrate quick alerts into scripts, CI/CD pipelines, or manual workflows.

How this skill works

The skill shows how to build a minimal JSON payload containing channel_id and content, then call the Pushinator API endpoint https://api.pushinator.com/api/v2/notifications/send with the Authorization: Bearer ${PUSHINATOR_API_KEY} and Content-Type: application/json headers. It demonstrates writing the payload to a file and sending it via curl, and explains expected HTTP success and error codes. It also highlights environment variable handling when using pipes in shells.

When to use it

• Send immediate alerts to mobile devices from scripts or automation
• Notify teams about deployments, build results, or incidents
• Integrate lightweight notifications into CI/CD pipelines
• Get completion or error alerts for long-running jobs
• Broadcast short updates to a topic-based channel

Best practices

• Store your API token in an environment variable (PUSHINATOR_API_KEY) and never hard-code it
• Keep messages concise and actionable to fit push display limits
• Use separate channels for different notification types to avoid noise
• Respect your plan’s rate limits and monitor monthly usage
• Wrap curl commands in bash -c '...' when piping to avoid environment variable loss in some runners

Example use cases

• Notify QA and ops when a deployment finishes with a short summary
• Send CI build failure alerts including a link to logs
• Trigger a personal mobile alert when a scheduled backup or data job completes
• Broadcast on-call rotation reminders or incident triage prompts to a channel