Create Follow-Up Jobs from Closed Pull Requests
Closing the code change should open the next practical step.
Trigger
Pull Request Event
Triggered when a pull request is opened, closed, or synchronized.
Action
ServiceM8 Create Job
Tool to create a new job in servicem8. use when you have all job details and need to push a record into servicem8. example: "create a quote job for 123 main st with po #1234."
Why this helps
A completed pull request can require real-world follow-up that is easy to leave undocumented.
- Converts completed code work into visible follow-up
- Prevents release tasks from relying on memory
- Creates a consistent post-delivery handoff
Setup
Build it in a few focused steps.
- 1Connect GitHub and ServiceM8 to Notis once through the portal.
- 2Create the automation in the portal or ask Notis in plain language.
- 3Tell Notis to create a ServiceM8 job when a qualifying pull request closes and explain the follow-up outcome needed.
- 4Choose the pull request event trigger and select a reporting channel.
- 5Test with one closed pull request.
Questions about this workflow
Can it distinguish merged from simply closed?
Yes. State that only merged pull requests should create the job.
What kind of follow-up can it represent?
Use it for rollout checks, installation, customer communication, or other operational work.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Servicem8. A trigger fires from one place; an action lands in another.
GitHub triggers
Servicem8 actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
ServiceM8 Create Job Note
Tool to create a new job note in servicem8. use when you need to attach additional information to a specific job after obtaining its uuid.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
ServiceM8 Create Job Payment
Tool to create a new job payment in servicem8. use when you have collected payment details and need to record payment against a job. example: "create a 100.00 cash payment for job 123e4567-e89b-12d3-a456-426614174000 at 2023-01-01 13:00:00."
New Workflow Artifact Created
Triggers when a new workflow artifact is created in a GitHub repository. Monitors for newly created GitHub Actions workflow artifacts. Optionally filters by artifact name to restrict monitoring to specific artifacts.
Create a new Job
Tool to create a new job in servicem8. use when you have gathered all job details and need to push a record. example: "create a quote job for 123 main st with po #1234."
Branch Changed
Triggers when a GitHub branch changes. Monitors a specific branch for: - New commits pushed (head commit SHA changes) - Protection status toggled (branch becomes protected or unprotected) - Protection settings changed, including: required status checks and their enforcement level, admin enforcement, required pull request reviews (dismiss stale reviews, code owner reviews, approving review count, last push approval), required linear history, force push allowance, deletion allowance, conversation resolution, branch locking, and fork syncing.
Delete Job Note
Tool to delete a specific job note. use when you need to archive a note by its uuid.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
ServiceM8 Delete Job Payment
Tool to delete (archive) a specific job payment by its uuid. use when you need to archive a payment record.
Check Run Status / Conclusion Changed
Triggers when a specific GitHub check run changes its status or conclusion. Monitors a single check run for changes to: status (queued, in_progress, completed, etc.), conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required), started_at, and completed_at.
List All Assets
Tool to list all servicem8 assets. use when you need a comprehensive asset registry, including custom fields, for inventory or reporting.
Check Suite Status / Conclusion Changed
Triggers when a GitHub check suite changes its status or conclusion for a given ref. Monitors all check suites associated with a git reference (branch, tag, or commit SHA) for changes to status (queued, in_progress, completed, etc.) and conclusion (success, failure, neutral, cancelled, skipped, timed_out, action_required, startup_failure, stale). Optionally filters by GitHub App ID.
List All Clients
Tool to list all servicem8 clients. use when you need a complete set of customer records for integrations or reporting.
New Code Scanning Alert Created
Triggers when a new code scanning alert is created in a repository. Fires an event for each newly created code scanning alert detected in the configured repository. Alerts can be filtered by Git reference, scanning tool, state, and severity. The payload includes the alert number, rule details, tool information, state, severity, and the location of the most recent instance.
List All Document Templates
Tool to list document templates. use when you need to retrieve available template uuids and names before generating job documents.
Connect any two apps with Notis in the middle.
GitHub and Servicem8, 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 Servicem8.