Assign GitHub issues from Chatwork requests
Keep urgent requests moving by sending a Chatwork webhook that gives the matching GitHub issue an 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
A request buried in chat can sit unowned while everyone assumes someone else will handle it.
- Makes ownership visible
- Reduces follow-up messages
- Preserves focus time
Setup
Build it in a few focused steps.
- 1Connect Chatwork and GitHub to Notis once in the portal.
- 2Open Automations and choose New Automation.
- 3Write one instruction telling Notis to assign the requested GitHub issue from each incoming Chatwork webhook.
- 4Choose Incoming webhook as the trigger and a channel for run reports.
- 5Send one real request to test the automation.
Questions about this workflow
Do I need to map Chatwork fields to GitHub?
No. Describe the assignment outcome in plain language and Notis handles the details.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Chatwork to GitHub. A trigger fires from one place; an action lands in another.
Chatwork triggers
GitHub actions
Accept a repository invitation
Accepts a pending repository invitation that has been issued to the authenticated user.
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.
Not just Chatwork and GitHub. Any combination from 1,000+ integrations.
When this happens · Trigger
Do this · Action
Save your first hour today.
7 days free trial with 20$ free usage included.
No card. Works with personal or business GitHub.