Route BlueFox Email requests to GitHub issue owners
Send a request to your Notis webhook and let Notis assign the referenced GitHub issue to the named owner.
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
Issue ownership gets lost when requests arrive by email and you have to switch tools to assign them.
- Assign the issue from the request context
- Reduce manual handoffs between email and GitHub
- Keep requests moving without a second triage pass
Setup
Build it in a few focused steps.
- 1Connect BlueFox Email and GitHub once in Notis.
- 2Create an automation in any Notis channel or in Automations, New Automation.
- 3Describe that Notis should assign the referenced GitHub issue to the requested owner.
- 4Choose a webhook trigger and where run reports should go.
- 5Test with one real request payload and issue.
Questions about this workflow
Does BlueFox Email provide a trigger for this automation?
No. Start it with a Notis webhook and send the request context to that webhook.
What should the request include?
Provide enough context to identify the GitHub repository and issue, plus the intended assignee. The payload must supply these details.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link BlueFox Email to GitHub. A trigger fires from one place; an action lands in another.
BlueFox Email 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.
BlueFox Email 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.