Create your own Slack and Ashby integration

Choose a trigger
Choose an action

When Slack: New message posted happens, do Ashby: Create application.

Popular Slack and Ashby workflows

When this happens in one app, do this in the other. Try it on Hub to connect both apps and run the pair.

Most popular

Post stage changes to #talent-pipeline

When a candidate reaches onsite in Ashby, post name, role, and recruiter to #talent-pipeline.

Ashby + SlackTry it →

Celebrate offers in #hiring-wins

When an Ashby offer is created, announce role, level, and start target in #hiring-wins.

Ashby + SlackTry it →

File Ashby referrals from :referral: reactions

When someone reacts with :referral: on a resume share, create an Ashby application with referrer noted.

Slack + AshbyTry it →

DM interviewers when Ashby schedules panels

When an interview is scheduled, post time, loop, and Ashby link to the interviewers Slack DM.

Ashby + SlackTry it →

Summarize new applicants each morning

When applications submit overnight, search Slack for open reqs and post a digest to #recruiting-ops.

Ashby + SlackTry it →

Welcome new hires in #general

When a candidate is marked hired, post a welcome message with team and start date.

Ashby + SlackTry it →

Agent

Use Corsair's MCP with your agent

Corsair connected

The agent searches both apps before it answers.

Where is the senior backend candidate we interviewed last week?

Slack and Ashby details

Slack and Ashby FAQ

Yes. Corsair is built with a REST API. This means you can build agents, knowledge bases, interfaces, and workflows.

Yes. Connect Slack and Ashby once, then post stage and offer updates to channels, schedule reminders, and create applications from referral reactions.

Pipeline alerts, offer announcements, referral intake from reactions, interview scheduling pings, applicant digests, and hire announcements.

Yes. Slack message, reaction, channel, and file events plus Ashby application, stage, interview, offer, and hire webhooks are typed for recruiting workflows.