Connect ActiveTrail to Ashby
When something happens in ActiveTrail, Notis takes the next step in Ashby. 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 ActiveTrail to Ashby
Create Ashby candidates from recruiting campaign responses
Use an ActiveTrail response or contact payload to create an Ashby candidate when it contains enough information to identify them.
Tag candidates who respond with recruiting interest
Apply an existing Ashby tag to a candidate when a webhook request includes an ActiveTrail response indicating recruiting interest.
Record recruiting reply context on an Ashby candidate
Add a candidate note with relevant ActiveTrail reply context supplied in a webhook request.
Create Ashby applications from qualified recruiting replies
Create an Ashby application when a webhook request supplies a qualifying reply, candidate identity, and target job details.
Group campaign-sourced candidates in an Ashby project
Associate a candidate with an existing Ashby sourcing project using candidate and project details supplied in a webhook request.
Attribute campaign replies to their recruiting source
Update an Ashby application's source attribution using source details included in a webhook request.
Advance an application after a confirmed recruiting reply
Move an identified Ashby application to a specified stage when a request confirms the conditions you define.
Assign a recruiter to a campaign candidate's application
Add an Ashby user to the hiring team for an identified application, job, or opening based on request details.
Create a reusable Ashby tag for a recruiting campaign
Create a new Ashby candidate tag when a request identifies a useful campaign category that does not already exist.
Supported Triggers and Actions
Notis builds workflows that link ActiveTrail to Ashby. A trigger fires from one place; an action lands in another.
ActiveTrail triggers
Ashby actions
Recurring trigger
Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.
Add Candidate to Project
Add a candidate to a recruiting project.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Candidate Tag
Add an existing tag to a candidate’s profile.
Add Hiring Team Member
Assign a team member to a hiring team.
Add User to Interviewer Pool
Add a user to a pool of interviewers.
Add Opening Job
Link an existing job to a job requisition.
Add Opening Location
Associate a location with an existing job requisition.
Anonymize Candidate
Irreversibly anonymizes a candidate’s personal data; all applications must be archived or hired.
Approve Offer
Approve an offer or a specific step in its approval process.
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 ActiveTrail and Ashby
Connect any two apps with Notis in the middle.
ActiveTrail and Ashby, 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 Ashby.