Track failed GitHub deployments in Wrike
Convert a deployment failure into a visible recovery action before attention fragments.
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
Modify task
Modifies an existing wrike task by its id, allowing updates to attributes such as title, status, dates, assignees, and custom fields; `prioritybefore` and `priorityafter` are mutually exclusive, and parent folder ids for `addparents`/`removeparents` cannot be the recycle bin.
Why this helps
Deployment failures compete with everything else and can lack a clear owner or next step.
- Creates a recovery cue
- Keeps incident work visible
- Reduces manual escalation
Setup
Build it in a few focused steps.
- 1Connect GitHub and Wrike to Notis once.
- 2Create a new automation through the portal.
- 3Ask Notis to update the related Wrike incident task when a GitHub deployment status is failure or error.
- 4Choose the new deployment-status trigger and run-report channel.
- 5Test with a safe real deployment example.
Questions about this workflow
Can successes be ignored?
Yes - state that only failed or errored deployment statuses need action.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Wrike. A trigger fires from one place; an action lands in another.
GitHub triggers
Wrike 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.
Bulk modify group members
Adds or removes members for multiple wrike groups in a single request; all specified user ids must correspond to existing wrike users.
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 a folder
Creates a new wrike subfolder within the specified `folderid`, optionally as a project if `customitemtypeid` is given; the folder is auto-shared with its creator.
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 a group
Creates a new user group in wrike with a specified title, optionally setting members, parent group, avatar, and custom metadata.
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.
Create invitation
Invites a user to a wrike workspace by email, optionally with name, specifying either `usertypeid` or a combination of `role`/`external`; custom email subject/message available for paid accounts.
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.
Create task in folder
Creates a new task in a specified wrike folder; if setting priority with `prioritybefore` or `priorityafter`, the referenced task must be in the same folder or project.
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 custom field by id
Permanently deletes a custom field by its id; this action is irreversible and requires a valid, existing custom field id.
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.
Delete folder
Permanently deletes the folder specified by `folderid` and all its contents (e.g., tasks, documents, subfolders) from the wrike workspace; this irreversible action is for when the folder is no longer needed and has no active tasks or dependencies that would block deletion.
Commit Event
Triggered when a new commit is pushed to a repository.
Delete group by id
Permanently deletes a group by its `groupid`; this action is irreversible and does not affect user accounts that were members of the group.
Connect any two apps with Notis in the middle.
Not just GitHub and Wrike. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7-day trial of any paid plan, with 20$ of usage included.
No card. Works with personal or business Wrike.