Keep deployment outcomes visible where follow-up happens
See whether a customer relevant deployment succeeded or needs attention without checking every run.
Trigger
New Deployment Status Created
Triggers when a new deployment status is created for a specific deployment. Fires an event for each newly created deployment status on the monitored deployment. Deployment statuses represent state transitions such as pending, in_progress, success, failure, error, inactive, and queued. The payload includes the status state, creator, environment, description, timestamps, and relevant URLs.
Action
Create Note
This tool creates a new note on a given record in attio. the note can be attached to any record type (like person, company, or deal) and includes a title and content. it requires parameters such as parent object, parent record id, title, and content, with an optional created at timestamp.
Why this helps
Deployment state changes can affect a promised update, but the relationship owner may not see them promptly.
- Bring deployment outcomes into relationship context.
- Make failures and successes easier to spot during follow-up.
- Keep a source reference for technical investigation.
Setup
Build it in a few focused steps.
- 1Connect GitHub and Attio once in the Notis portal.
- 2Create an automation in Automations, New Automation, or tell Notis from any channel.
- 3In one instruction, ask Notis to record the deployment status and source link on the relevant Attio record, highlighting failures for follow-up.
- 4Pick New Deployment Status Created as the trigger and choose where run reports go.
- 5Test with one real status event and review the resulting note.
Questions about this workflow
What states may appear?
Deployment statuses can represent pending, in progress, success, failure, error, inactive, and queued transitions.
Does it watch every deployment?
The trigger is for a specific deployment. Choose the deployment whose statuses should create notes.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link GitHub to Attio. A trigger fires from one place; an action lands in another.
GitHub triggers
Attio actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Create Note
This tool creates a new note on a given record in attio. the note can be attached to any record type (like person, company, or deal) and includes a title and content. it requires parameters such as parent object, parent record id, title, and content, with an optional created at timestamp.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Create Record
This tool creates a new record in attio for a specified object type (people, companies, deals, users, workspaces, etc.). it requires the object type and a values dictionary containing the attributes for the new record.
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.
Delete Note
This tool allows users to delete a specific note in attio by its id. it is implemented via delete https://api.attio.com/v2/notes/{note id} and handles note deletion by validating the provided note id. it complements attio create note functionality, providing complete note management capabilities within the attio platform.
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 Record
This tool allows you to delete a record from attio permanently. the deletion is irreversible, and the data will eventually be removed from the system.
New Branch Created
Triggers when a new branch is created in a GitHub repository. Detects newly created branches. Deleted branches do not fire events.
Find Record
This tool allows users to find a record in attio by either its unique id or by searching using unique attributes. it provides two methods: one for directly retrieving a record by its id with the get /v2/objects/{object}/records/{record id} endpoint, and another for searching by attributes using the post /v2/objects/{object}/records/query endpoint.
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.
Get Object Details
This tool retrieves detailed information about a specific object type in attio, including all its attributes and their properties. this is useful for understanding what fields are available when creating or updating records of this type.
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 Lists
This tool retrieves all lists available in the attio workspace. the lists are returned sorted as they appear in the sidebar. this tool is essential for managing and navigating lists, and is a prerequisite for many list-related operations. it requires the list configuration:read permission scope.
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 Notes
This tool lists all notes associated with a specific record in attio. notes are returned in reverse chronological order (newest first).
Connect any two apps with Notis in the middle.
GitHub and Attio, 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 Attio.