Connect Addresszen to DeployHQ
When something happens in Addresszen, Notis takes the next step in DeployHQ. Describe what you want in plain English, or start from one of the examples below.
When this happens · Trigger
Do this · Action
Ways Notis can move work from Addresszen to DeployHQ
Inventory DeployHQ projects for an Addresszen delivery
Receive an Addresszen address validation payload and return the DeployHQ projects relevant to the delivery operation.
Check the DeployHQ project behind a validated address
Use an Addresszen webhook payload with an explicit DeployHQ project identifier to retrieve that project's details.
Review deployment history for an Addresszen delivery
Retrieve paginated DeployHQ deployment history when an Addresszen webhook includes a project identifier and delivery reference.
Check repository context for a validated delivery project
Retrieve DeployHQ repository details from an Addresszen webhook that supplies the exact project identifier.
Check available DeployHQ branches for an Addresszen request
List repository branches for a specified DeployHQ project using explicit project details from an Addresszen webhook.
Check the latest revision for an Addresszen delivery project
Retrieve the latest remote revision for the exact DeployHQ project and branch named in an Addresszen webhook.
Review a DeployHQ commit for an Addresszen request
Retrieve commit details when the Addresszen webhook supplies the exact project and revision reference.
Review recent commits and tags for a delivery project
Retrieve recent commit and tag context for a DeployHQ branch named in an Addresszen webhook.
Inventory DeployHQ server groups for an Addresszen operation
List server groups for the exact DeployHQ project named by an Addresszen webhook payload.
Supported Triggers and Actions
Notis builds workflows that link Addresszen to DeployHQ. A trigger fires from one place; an action lands in another.
Addresszen triggers
DeployHQ actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Delete Command
Deletes an SSH command from a project’s configuration.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Delete Project
Permanently removes a project.
Delete Build Cache File
Deletes a build cache file from a project.
Delete Excluded File Rule
Deletes an excluded file rule from a project’s deployment configuration.
Delete Server Group
Deletes a server group from a project’s deployment configuration.
Delete Template
Permanently removes a template.
Get Projects
Lists all projects in your account.
Get Project
Retrieves details about a project.
Four ways to start an automation.
A trigger is the event that kicks a workflow off. Notis supports four kinds: an event in a connected app, an inbound webhook, a recurring schedule, and soon, your own database.
Integration triggers
Fire when something happens inside a connected app. New Notion page, Stripe charge, Linear issue: any of 1,000+ apps can start a workflow.
Webhook triggers
A unique URL per workflow. Anything that can send an HTTP POST can start an automation, including no-code tools that speak webhooks.
Recurring triggers
Cron-style schedules run a workflow on the clock. Daily standups, hourly syncs, business-hours-only digests: the workhorse of Notis.
Database triggers
Watch a row, query, or threshold in your own database and fire the moment the data changes. Row inserted, value crosses a limit, query starts matching.
Classic automation breaks. AI adapts.
Same triggers and actions, smarter middle. AI handles the fuzziness that breaks traditional Zapier-style workflows the moment a field gets renamed.
Describe it. Notis builds it.
Skip the visual builder. Tell Notis what you want, in plain English. It writes the workflow, you review and deploy.
You · in the Notis Builder
NEW“When a row gets added to the Q4 OKRs Notion database and the status is Blocked, send a Telegram message to the owner with a summary of what's blocking, and ping me if there's no reply within 24 hours.”
Notis built this automation:
Watch every run.
Notis Desktop is Mission Control for your AI automations. See every run, replay, edit, or rewind. Set approval gates so Notis pauses before destructive actions.
- Full run history with inputs, outputs and traces
- Replay any run with edited inputs
- Approval inbox, confirm via chat in one tap
- Audit logs for compliance teams
Automations
Inbox
Migrate background jobs to a durable queue You can cancel it through Stripe
3 daysNotis v3 release update This one’s v3: Notis Manager (desktop app with …
8 daysAdd multi-tenant RBAC User initiates a voice call
13 daysDraft pricing v (tiers, limits, overages) and sanity-check margins
2 weeksVerify analytics events for new features That’s a really interesting automat…
1 monthEverything in the box.
Whatever starts the workflow, the platform underneath is the same: a thinking brain, full visibility, and you in control.
AI in the middle
Every step can include an LLM call: summarise, classify, extract, rewrite.
Full observability
Every run, every step, every input, all replay-able from Mission Control.
Human in the loop
Pause for approval. Notis pings you in chat with one-tap approve.
Self-healing
When an API changes shape, Notis adapts the parser. Less midnight fire-fighting.
More ways to connect Addresszen and DeployHQ
Connect any two apps with Notis in the middle.
Addresszen and DeployHQ, 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 DeployHQ.