Send support handoffs to the right GitHub issue owner
Carry the engineering follow-up from a customer conversation into the issue that needs attention.
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
Support details and engineering ownership can get separated when customer conversations move between Agile CRM and GitHub.
- Turn a support handoff into an issue assignment.
- Keep the requested issue and assignee together in the incoming request.
- Surface a run report if the assignment is ignored or fails.
Setup
Build it in a few focused steps.
- 1Connect Agile CRM and GitHub once in the Notis portal.
- 2Create an automation in the portal or tell Notis in plain language.
- 3Describe in one instruction how to add the supplied GitHub username to the supplied issue when a support handoff is ready.
- 4Choose the notis_webhook trigger and where run reports should go.
- 5Test with one real handoff and an issue the authenticated GitHub user can update.
Questions about this workflow
Does the workflow create a GitHub issue?
No. The available action adds an assignee to an existing issue, so include its repository and issue details in the incoming request.
Can this assign someone without repository access?
GitHub may silently ignore changes if the authenticated user lacks push access. Check the run report and repository permissions if assignment does not take effect.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Agile CRM to GitHub. A trigger fires from one place; an action lands in another.
Agile CRM 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.
Agile CRM 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.