Put campaign follow-up issues in the right hands
Send Notis the issue and assignee details with a campaign follow-up request, and let it update the GitHub issue.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add assignees to an issue
Adds or removes assignees for a github issue; changes are silently ignored if the authenticated user lacks push access to the repository.
Why this helps
When a campaign surfaces work for the product team, ownership can be unclear and follow-up can stall.
- Give supplied follow-up work a clear owner.
- Keep the campaign reference alongside the issue context in the automation prompt.
- Reduce the chance that a campaign-related task sits unassigned.
Setup
Build it in a few focused steps.
- 1Connect ActiveTrail and GitHub once in the Notis portal.
- 2Create an automation in Automations, New Automation, and name it for campaign follow-up.
- 3In one instruction, tell Notis to add the supplied assignees to the supplied GitHub issue and include the campaign reference in its reasoning.
- 4Pick the webhook trigger and choose where run reports should go.
- 5Test with one real issue and confirm the requested assignees have access.
Questions about this workflow
What does the webhook need to provide?
Include the repository, issue number, and GitHub usernames to assign. The automation cannot infer missing issue or ownership details.
What if the authenticated user lacks permission?
GitHub may silently ignore assignee changes when the authenticated user lacks push access to the repository.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link ActiveTrail to GitHub. A trigger fires from one place; an action lands in another.
ActiveTrail triggers
GitHub actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
List repositories starred by the authenticated user
Deprecated: lists repositories starred by the authenticated user, including star creation timestamps; use 'list repositories starred by the authenticated user' instead.
List stargazers
Deprecated: lists users who have starred a repository; use `list stargazers` instead.
Star a repository for the authenticated user
Deprecated: stars a repository for the authenticated user; use `star a repository for the authenticated user` instead.
Add email for auth user
Adds one or more email addresses (which will be initially unverified) to the authenticated user's github account; use this to associate new emails, noting an email verified for another account will error, while an existing email for the current user is accepted.
Add app access restrictions
Replaces github app access restrictions for an existing protected branch; requires a json array of app slugs in the request body, where apps must be installed and have 'contents' write permissions.
Add a repository collaborator
Adds a github user as a repository collaborator, or updates their permission if already a collaborator; `permission` applies to organization-owned repositories (personal ones default to 'push' and ignore this field), and an invitation may be created or permissions updated directly.
Add a repository to an app installation
Adds a repository to a github app installation, granting the app access; requires authenticated user to have admin rights for the repository and access to the installation.
Connect any two apps with Notis in the middle.
ActiveTrail and GitHub, or any other 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 GitHub.