Keep AgencyZoom prospect follow-ups visible in GitHub
Give promising prospects a clear next step by turning follow-up needs from AgencyZoom into issues your team can track.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add labels to an issue
Adds labels (provided in the request body) to a repository issue; labels that do not already exist are created.
Why this helps
Prospect follow-ups get buried across conversations, making it easy for a busy team to lose track of who needs attention.
- Capture follow-up work where the team already tracks tasks.
- Include relevant AgencyZoom client or prospect context in the issue.
- Make the next sales touch easier to spot and assign.
Setup
Build it in a few focused steps.
- 1Connect AgencyZoom and GitHub once in the Notis portal.
- 2Create an automation from Automations, New Automation, and give it a name.
- 3Tell Notis to create a GitHub issue summarizing the AgencyZoom prospect context and the follow-up needed.
- 4Choose a webhook trigger, select where run reports should go, and test with one real example.
Questions about this workflow
Does AgencyZoom start this workflow with a built-in event?
No. AgencyZoom has no listed trigger events, so an HTTP request to a Notis webhook starts the automation.
What should I include in the instruction?
Describe which prospect follow-up should become an issue and ask Notis to include the useful context and the next action. Labels can be added if they already exist or GitHub can create them.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Agencyzoom to GitHub. A trigger fires from one place; an action lands in another.
Agencyzoom 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.
Agencyzoom 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.