Connect Affinda to Ashby
When something happens in Affinda, 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 Affinda to Ashby
Create an Ashby candidate from a parsed resume
Turn a resume processed by Affinda into a candidate record in Ashby, using the extracted details and avoiding duplicate profiles where possible.
Add a resume summary to an Ashby candidate
Use Affinda's resume extraction to prepare a concise note on an existing Ashby candidate, with relevant experience and qualifications easy to scan.
Tag Ashby candidates by extracted resume skills
Apply an existing Ashby candidate tag when Affinda extracts a clearly relevant skill from a resume.
Add parsed resume candidates to an Ashby sourcing project
Organize a candidate from an Affinda processed resume into the relevant existing Ashby sourcing project.
Create an Ashby application from an eligible resume
For a resume with a clear candidate and job match, create an Ashby application so the person enters the appropriate hiring pipeline.
Submit an Ashby referral from processed candidate details
Turn candidate details extracted from a resume into an Ashby referral when the required referral information is available from the request or provided context.
Correct application source using supplied recruiting context
When a resume arrives with clear source context, update the Ashby application's source attribution to reflect it.
Create only clearly new candidates from parsed resumes
Review Affinda resume details against available Ashby candidate information and create a candidate only when the record appears clearly new.
Record a resume review decision on the candidate profile
Create an Ashby candidate note that records a recruiter supplied review decision alongside relevant details extracted from a resume.
Supported Triggers and Actions
Notis builds workflows that link Affinda to Ashby. A trigger fires from one place; an action lands in another.
Affinda 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 Affinda and Ashby
Connect any two apps with Notis in the middle.
Affinda 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.