Keep documentation-driven context structured
A meaningful README change can prompt the metadata your operations need.
Trigger
GitHub Repository README Changed
Triggers when the README file in a specific repository directory changes. Monitors the README in a configurable directory and branch/tag/commit. The payload includes the current README metadata (filename, path, SHA, size, URLs), the previous and current git blob SHAs, and a list of which tracked fields changed.
Action
Create Custom Field
Tool to create a custom field for a specified entity in simla. use when you need to extend orders, customers, corporate customers, or companies with custom metadata fields.
Why this helps
Documentation changes can affect onboarding or delivery without a place to record the new context.
- Creates structure for new documentation context
- Reduces ad hoc notes
- Supports smoother onboarding and delivery
Setup
Build it in a few focused steps.
- 1Connect GitHub and Simla com to Notis once through the portal.
- 2Create an automation instructing Notis to create a Simla com custom field when a specified README change requires new operational metadata.
- 3Select the README changed trigger and choose the channel for run reports.
- 4Make one controlled README update and verify the field definition.
Questions about this workflow
Should every README edit create a field?
No. The instruction should identify only changes that introduce genuinely new metadata needs.
Which Simla entities can use custom fields?
Simla com supports custom fields for orders, customers, corporate customers, and companies.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Simla com. A trigger fires from one place; an action lands in another.
GitHub triggers
Simla com actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Customer
Tool to create a new customer. use after gathering all customer information.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Custom Field
Tool to create a custom field for a specified entity in simla. use when you need to extend orders, customers, corporate customers, or companies with custom metadata fields.
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 Order
Tool to create a new order. use when you have all order details prepared and need to register it in simla via the api.
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.
Create Task
Tool to create a new task. use after gathering task details and assignees.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Edit Customer
Tool to edit an existing customer. use when you need to update customer details by external id.
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.
Edit Custom Field
Tool to edit an existing custom field by entity and code. use when you need to update custom field metadata before usage.
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.
Edit Order
Tool to edit an existing order by external id. use when you need to update order details by external id.
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.
Edit Task
Tool to edit an existing task. use after confirming task id and fields to update. updates only provided fields on the task.
Connect any two apps with Notis in the middle.
GitHub and Simla com, 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 Simla com.