How do I connect Ashby?

Sign up for Conductor Deck, then add a Ashby step to a workflow on the visual canvas. The builder walks you through the connection it needs — an account authorization or the required keys — right inside the step. No separate setup or code.

Yes — Conductor Deck has a free tier you can build and run workflows on, with no credit card required. Paid plans raise the monthly run limits and add advanced features when you need them.

What's the difference between a trigger and an action?

A trigger is the event that starts a workflow — for example, a Stream Deck button press or an incoming event from a connected app. An action is a step the workflow performs once it runs. A workflow is one trigger followed by one or more actions.

Ashby + Stream Deck

hr-talent-&-recruitment · 28 triggers · 125 actions

Ashby delivers an applicant tracking system for modern teams, offering features like job postings, candidate management, and data-driven hiring insights to streamline the recruitment process Add Ashby to your Stream Deck workflows with guided setup for the connection details it needs.

Build an Ashby workflow — free See how it works

No code
Free tier
Key press or app-event trigger
Pairs with OBS & Elgato tools
OAuth & keys handled in-builder

Popular ways to use Ashby

Add Ashby to a workflow and pair it with a Stream Deck button to run it in one press — handy for hr-talent-&-recruitment tasks. Combine it with OBS, your Elgato tools, or any other app you connect to build a routine that fits how you work.

Browse all templates

Triggers & actions

Events that start your workflow automatically.

Application Signature Request Updated

Triggers when an e-signature request attached to an application — an NDA, a consent form — is sent, cancelled, completed or deleted. Signature requests on offer letters are a separate trigger, because Ashby gives the two different fields.

Application Submitted

Triggers when a candidate submits an application, or a recruiter adds one by hand. Does not fire for bulk imports or integration syncs, and does not fire when an existing application later changes.

Application Updated

Triggers when anything on an existing application changes — its fields, custom fields, archive state, or the job it is transferred to. Also fires alongside a hire and alongside a stage change, so enabling those triggers too gives two deliveries per action.

Candidate Deleted

Triggers when a candidate record is deleted from Ashby. Distinct from a merge, where the candidate's history is folded into another record rather than lost.

Candidate Emails Changed

Triggers when a candidate's recent email messages may have changed. Carries no message content — use the watermark in the payload to refetch them; Ashby marks this webhook beta and may not enable it for every organisation.

Candidate Hired

Triggers when a candidate is marked hired in Ashby, including hires on confidential jobs. Pushing that hire to an HRIS is a separate, later trigger.

Candidate Merged

Triggers when two candidate records are merged into one. Like a deletion this is the only way to observe it, but unlike a deletion the candidate's history survives on the record named here.

Candidate Moved To Interview Stage

Triggers when an application moves into a different interview stage, in either direction. Ashby also emits an application-updated event for the same move, and emits this one itself when a candidate is hired.

About Ashby

Ashby delivers an applicant tracking system for modern teams, offering features like job postings, candidate management, and data-driven hiring insights to streamline the recruitment process

hr-talent-&-recruitment

How to connect

Sign up for free

Create your Conductor Deck account: no credit card required.

Connect Ashby

Follow the setup prompts for Ashby. Conductor Deck handles the app authorization or required connection details inside the workflow builder.

Build a workflow

Add an Ashby action to your visual workflow canvas. Configure the options you need, then connect it to other steps.

Run it from a key, or let events fire it

Sync your workflow to a Stream Deck button, or skip the button: Ashby triggers can start it automatically when events happen.

Frequently asked questions

How do I connect Ashby?: Sign up for Conductor Deck, then add a Ashby step to a workflow on the visual canvas. The builder walks you through the connection it needs — an account authorization or the required keys — right inside the step. No separate setup or code.
Is it free?: Yes — Conductor Deck has a free tier you can build and run workflows on, with no credit card required. Paid plans raise the monthly run limits and add advanced features when you need them.
What's the difference between a trigger and an action?: A trigger is the event that starts a workflow — for example, a Stream Deck button press or an incoming event from a connected app. An action is a step the workflow performs once it runs. A workflow is one trigger followed by one or more actions.

Automate Ashby with your Stream Deck

Get started free View pricing

Similar integrations