Keep deployment and campaign status together
When deployment status changes, bring the campaign context back into view automatically.
Trigger
New Deployment Status Created
Triggers when a new deployment status is created for a specific deployment. Fires an event for each newly created deployment status on the monitored deployment. Deployment statuses represent state transitions such as pending, in_progress, success, failure, error, inactive, and queued. The payload includes the status state, creator, environment, description, timestamps, and relevant URLs.
Action
Get Advertising Campaign
Retrieve a specific advertising campaign by its ID using ToneDen's API. Endpoint: GET /advertising/campaigns/{campaignID} Notes: - This endpoint does not require a userID in the path per official docs. - Some accounts may not have advertising access; in such cases, non-2xx responses are still returned here for observability instead of raising, so the caller can inspect the error object.
Why this helps
Founders often know whether code shipped but forget to check whether the campaign connected to that launch is ready or active.
- Surfaces campaign context after deployment updates
- Reduces repeated dashboard checking
- Creates a reliable launch follow-up habit
Setup
Build it in a few focused steps.
- 1Connect GitHub and ToneDen to Notis once through the portal.
- 2Create the automation in the portal or ask Notis for it conversationally.
- 3Use this instruction: When a GitHub deployment status changes, retrieve the related ToneDen campaign and summarize what needs attention.
- 4Pick the deployment status trigger and choose a reporting channel.
- 5Test with one deployment status update and confirm the returned campaign is the intended one.
Questions about this workflow
What if the deployment has no campaign yet?
Tell Notis to report that clearly so you can decide whether to create one.
Is this a campaign edit?
No. This workflow retrieves campaign details and reports them for follow-up.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Toneden. A trigger fires from one place; an action lands in another.
GitHub triggers
Toneden actions
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Create Advertising Campaign
Tool to create a ToneDen advertising campaign on Facebook or Google platforms. Use when you need to launch a new ad campaign with specified budget, targeting, and creatives.
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
Create Attachment
Tool to create an attachment. Use when you need to programmatically create a social unlock or contest attachment after gathering all required parameters.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Create ToneDen Link
Tool to create a ToneDen link. Use when you have the target_type and, if needed, the services array. Supports creation of links for music, podcast, livestream, event, tour, biglink, fundraiser, smartlink, and custom types.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
Delete Advertising Campaign
Deletes a ToneDen advertising campaign by ID using DELETE /advertising/campaigns/{campaignID}.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
Delete ToneDen Link
Deletes a ToneDen link by ID using DELETE /links/{linkID}.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
Delete ToneDen Playbook Campaign
Deletes a ToneDen playbook campaign by ID using DELETE /playbooks/campaigns/{campaignID}.
New Repository Collaborator Added
Triggers when a new collaborator is added to a GitHub repository. Monitors the full list of collaborators on a repository and fires an event for each newly added collaborator. The payload includes the collaborator's GitHub username, account ID, profile URL, avatar URL, permission flags (pull, triage, push, maintain, admin), and assigned role name.
Expand ToneDen Link Template
Tool to expand a ToneDen link template. Use when you need to retrieve the full template link with your tracking pixels and optional service links. Provide a URL to generate platform services for music or podcast content.
Commit Event
Triggered when a new commit is pushed to a repository.
Get Advertising Campaign
Retrieve a specific advertising campaign by its ID using ToneDen's API. Endpoint: GET /advertising/campaigns/{campaignID} Notes: - This endpoint does not require a userID in the path per official docs. - Some accounts may not have advertising access; in such cases, non-2xx responses are still returned here for observability instead of raising, so the caller can inspect the error object.
Connect any two apps with Notis in the middle.
Not just GitHub and Toneden. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business Toneden.