It runs inside the ATS you already pay for
Figlime isn't a new system of record. It reads candidates from your ATS and writes the filled scorecard back onto the same profile — then connects to the rest of your stack: query your pipeline from your AI assistant over MCP, and surface results in Slack. No new tool for your team to learn, nothing to export.
Greenhouse, end to end
The full round trip happens on the candidate's Greenhouse profile — no tab-switching, no manual data entry.
Reads your pipeline
When a candidate reaches your screening stage, Figlime picks them up automatically — no list to upload, no CSV to maintain.
Screens against your scorecard
Figlime uses the rubric mapped to the role and runs the conversation, scoring each criterion with evidence.
Writes the result back
The transcript, filled scorecard, and an advance/hold recommendation land on the candidate's Greenhouse profile, ready for a human to action.
What's live and what's next
The screening engine is ATS-agnostic — each new integration is a connector, and we ship them by demand.
Connect the rest of your stack
Figlime meets your team where they already work — in their AI assistant and in Slack.
AI assistants · MCP
Figlime exposes your pipeline over MCP (the Model Context Protocol), so you can connect Claude or any MCP-compatible assistant and ask about your candidates in plain language. Answers come straight from your scorecards, and access follows the permissions you already have.
Slack
Connect your Slack workspace to bring screening into the channel your team already lives in — so the shortlist surfaces where people actually see it, not in another tab they have to remember to check.
Integration questions, answered
Which ATS does Figlime support today?
Greenhouse is live now — Figlime reads candidates from your pipeline and writes the transcript and filled scorecard back onto the candidate's profile. Lever, Ashby, and Workday are in active development.
Can I connect my AI assistant to Figlime?
Yes. Figlime exposes your pipeline over MCP (the Model Context Protocol), so you can connect Claude or any MCP-compatible assistant and ask about your candidates in plain language — "who are my strongest candidates and why?" Answers come straight from your scorecards, and access follows your existing permissions.
Does Figlime work with Slack?
Yes. Connect your Slack workspace to bring screening into the channel your team already works in, so the shortlist surfaces where people actually see it instead of in another tab.
Do we need to change our workflow?
No. Figlime works inside your existing ATS. Your team keeps reviewing candidates in Greenhouse exactly as they do now — the scorecard is just already filled in when they get there.
Can we get an integration that isn't listed yet?
Tell us which ATS you use. We prioritise integrations by demand, and the underlying screening engine is ATS-agnostic — the work is the connector, not the product.
Stop skimming. Start talking to the right people.
See Figlime run your own scorecard on a real pipeline — and watch the shortlist land in Greenhouse. One short call is all it takes.