Carry approved profile updates through to GitHub
A completed profile update can supply a supported social link for the connected GitHub user's public profile.
Trigger
Webhook received
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Action
Add social accounts for the authenticated user
Adds one or more social media links (which must be valid, full urls for platforms supported by github) to the authenticated user's public github profile.
Why this helps
A profile update can be approved in a document workflow and still be missed on the public GitHub profile.
- Reduce manual repetition after profile update approval.
- Use a complete URL provided in the request.
- Keep the profile update action traceable in a run report.
Setup
Build it in a few focused steps.
- 1Connect ActiveMerge and GitHub once in the Notis portal.
- 2In Automations, choose New Automation and give it a name.
- 3Tell Notis to add the supported full social profile URL in the approved request to the authenticated GitHub user's public profile.
- 4Choose the webhook trigger and select where run reports should go.
- 5Send one real approved profile update with a supported URL to the webhook and review the run report.
Questions about this workflow
What kind of link can be added?
The URL must be a valid, full URL for a platform supported by GitHub.
Whose profile is updated?
The action updates the public profile of the authenticated GitHub user.
Does the action verify the social account?
The listed action adds social media links. It does not describe a separate verification step.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link ActiveMerge to GitHub. A trigger fires from one place; an action lands in another.
ActiveMerge 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.
ActiveMerge 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.