Skip to content
Notis

Turn a reviewed Salesforce record into candidate intake

Capture candidate details from a Salesforce record type your team already uses for intentional recruiting intake.

Trigger

Record Updated (Generic SObject)

Triggers when monitored fields change on any Salesforce SObject. You specify the SObject type and which field values should be returned in the payload. The trigger uses SystemModstamp to detect changes regardless of which specific field changed.

Action

Create Candidate

Create a new candidate in the system. Use this to add candidates with their contact information and social profiles before applying them to jobs.

Why this helps

Candidate details may be recorded in a custom Salesforce object that recruiting does not regularly check.

  • Use an existing Salesforce intake process to start a recruiting profile.
  • Reduce repetitive data entry for clearly qualified people.
  • Keep the automation grounded in fields returned by the monitored record.

Setup

Build it in a few focused steps.

  • 1Connect Salesforce and Ashby once in the Notis portal.
  • 2Create an automation in Automations, New Automation, and name it for the chosen intake record.
  • 3Tell Notis which Salesforce record type and returned fields indicate an opted-in candidate, and to skip records without those details.
  • 4Pick Record Updated (Generic SObject) and select the relevant SObject type and returned fields in the trigger setup.
  • 5Choose where run reports should go, then test with one real intake record and review the candidate.

Questions about this workflow

Can this monitor any Salesforce object?

The generic trigger supports a specified SObject type and returned fields. Base the instruction on the fields made available by that trigger.

Should every matching record become a candidate?

Only when it clearly represents candidate intake and includes the required identity and consent context. Have Notis skip unclear records.

When this happens · Trigger

Do this · Action

Supported Triggers and Actions

Notis builds workflows that link Salesforce to Ashby. A trigger fires from one place; an action lands in another.

Salesforce triggers

Ashby actions

Recurring trigger

Notis starts this workflow on a schedule, such as daily, weekly, or during business hours.

TriggerScheduled

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.

ActionInstant

Webhook trigger

Notis starts this workflow when an external tool or custom backend sends an HTTP request.

TriggerInstant

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.

ActionInstant

Account Created or Updated

Triggers when an Account is created or updated in Salesforce. Uses LastModifiedDate high-watermark to capture both creations and updates.

TriggerPolling

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.

ActionInstant

Contact Updated

Triggers when an existing Salesforce Contact record is modified. Emits changed fields alongside relevant timestamps.

TriggerPolling

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.

ActionInstant

Record Updated (Generic SObject)

Triggers when monitored fields change on any Salesforce SObject. You specify the SObject type and which field values should be returned in the payload. The trigger uses SystemModstamp to detect changes regardless of which specific field changed.

TriggerPolling

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.

ActionInstant

New Contact Trigger

Triggers when a new Contact is Created in Salesforce.

TriggerPolling

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.

ActionInstant

New Lead Trigger

Triggers when a new Lead is created in Salesforce.

TriggerPolling

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.

ActionInstant

New or Updated Opportunity

Triggers when a Salesforce Opportunity is created or updated.

TriggerPolling

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.

ActionInstant

Connect any two apps with Notis in the middle.

Salesforce 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.