Anonymize Ashby candidates after a recorded privacy decision
Turn a clear privacy request into a completed Ashby action with an audit-friendly report.
Trigger
Transcription Complete Trigger
Triggers when a transcription is complete. Polls Fireflies API for transcripts created or updated since the last poll time. Handles rate limiting gracefully.
Action
Anonymize Candidate
Anonymize a candidate by removing personally identifiable information. Use this when you need to permanently anonymize a candidate's data. This action cannot be reversed and requires all of the candidate's applications to be in the archived or hired state.
Why this helps
Privacy decisions made in meetings can remain unresolved while personal data stays active.
- Reduces privacy follow-up work
- Acts only on explicit requests
- Reports blocked eligibility cases
Setup
Build it in a few focused steps.
- 1Connect Fireflies and Ashby in Notis once.
- 2Create an automation requiring an explicit request and eligible candidate state.
- 3Pick the Fireflies Transcription Complete trigger.
- 4Choose a restricted report channel for outcomes.
- 5Test with one authorized privacy transcript.
Questions about this workflow
Is anonymization reversible?
No, Ashby anonymization permanently removes personally identifiable information, so require explicit authorization.
What if applications are not eligible?
Notis should report the candidate without anonymizing until Ashby's eligibility requirement is met.
When this happens · Trigger
Do this · Action
Supported Triggers and Actions
Notis builds workflows that link Fireflies to Ashby. A trigger fires from one place; an action lands in another.
Fireflies 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 project in Ashby. Projects are sourcing initiatives or recruiting campaigns used to organize and track candidate pipelines. Use this to associate candidates with specific sourcing efforts. Common use cases: - Adding sourced candidates to recruiting campaigns - Organizing candidates by sourcing channel or initiative - Tracking candidates in specific hiring projects Requires candidatesWrite permission. Returns the updated candidate object on success, or error details if the candidate or project is not found.
Webhook trigger
Notis starts this workflow when an external tool or custom backend sends an HTTP request.
Add Candidate Tag
Add a tag to a candidate in Ashby. Use this to categorize and organize candidates with existing tags from the system. This action allows you to apply labels/tags to candidates for filtering, searching, and organizational purposes. Tags must already exist in the system - use LIST_CANDIDATE_TAGS to view available tags or CREATE_CANDIDATE_TAG to create new ones. The response includes the full updated candidate object when successful, showing the newly added tag in the candidate's tags array. If a candidate already has the tag, the operation will still succeed idempotently.
Transcription Complete Trigger
Triggers when a transcription is complete. Polls Fireflies API for transcripts created or updated since the last poll time. Handles rate limiting gracefully.
Add Hiring Team Member
Add an Ashby user to a hiring team at the application, job, or opening level. Use this when you need to assign a team member to participate in the hiring process with a specific role. Requires the organizationWrite permission.
Add User to Interviewer Pool
Add a user to an interviewer pool. Use this to assign interviewers to interview pools for scheduling and coordination. Requires the hiringProcessMetadataWrite permission.
Add Opening Job
Adds a job to an opening (job requisition) in Ashby ATS. An opening represents a position to be filled, while a job defines the role details. This action associates an existing job with an existing opening, allowing multiple jobs to be linked to a single opening. Use this when you need to add job definitions to an opening or when creating multi-role requisitions. Requires the jobsWrite permission. On success, returns the updated opening with the job added to its jobIds array. On failure, returns error details with specific error codes.
Add Opening Location
Tool to add a location to an opening (job requisition). Use when you need to associate a location with an existing opening. Requires the jobsWrite permission.
Anonymize Candidate
Anonymize a candidate by removing personally identifiable information. Use this when you need to permanently anonymize a candidate's data. This action cannot be reversed and requires all of the candidate's applications to be in the archived or hired state.
Approve Offer
Approve an offer or a specific approval step within an offer's approval process. This action supports two modes: - Complete offer approval: Provide only offerId to approve the entire offer - Step-specific approval: Provide offerId, approvalStepId, and userId to approve a specific step When approving a specific step, both approvalStepId and userId are required together. Requires the 'offersWrite' permission.
Connect any two apps with Notis in the middle.
Fireflies 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.