--- title: "RecruSpace Integration" description: "Connect AI agents to RecruSpace, an AI recruitment sourcing and screening platform. Agents submit applications, create and tag candidates, and organize talent pools so sourcing pipelines fill up and stay organized." url: https://flowrunner.ai/integrations/recruspace date_modified: 2026-08-12T15:40:33-07:00 --- # RecruSpace [HR](https://flowrunner.ai/integrations/category/hr) Connect AI agents to RecruSpace, an AI recruitment sourcing and screening platform. Agents submit applications, create and tag candidates, and organize talent pools so sourcing pipelines fill up and stay organized. [Verified](https://flowrunner.ai/integrations/verified "What does verified mean?") · 17 actions · API key · available [RecruSpace website](https://recruspace.com/) · [Platform Documentation](https://docs.recruspace.com) · Capability data verified 2026-08-10 1. A candidate replies to a sourcing message saying they want to be put forward for a role 2. Agent pulls the attached CV and runs Upload File to get a document ID 3. Agent runs Search Candidate By Email to see whether this person already exists in RecruSpace 4. Agent runs List Job Post Questions and confirms it has an answer for every required question 5. Recruiter receives the assembled application, including the terms of use acceptance the submission requires 6. Recruiter confirms the candidate genuinely consented before Apply To Job Post submits on their behalf ## What This Integration Enables Most recruiting APIs let a machine act as the recruiter. RecruSpace lets it act as the applicant too, and that is the thing worth understanding before you build on it. Apply To Job Post submits a full application on behalf of a person: their email, their name, an uploaded CV, arrays of education and work experience entries, answers to the job post's custom questions, and an explicit acceptance of the terms of use. That is a materially different kind of write from creating a record in a database, and it deserves a different kind of care. The rest of the surface supports that pattern well. Agents list and read job posts with filters on status, employment type, workplace type, location, and creator, and read the application questions configured for a post, each with a stable question key, the expected answer type, any choice options, and whether it is required. On the candidate side they search by partial email match, retrieve a full candidate including CV and photo links with presigned URLs, education, work experience, tags, and the platform's own AI screening score and suitability, create candidates from an already uploaded CV, and enrich them with notes and tags. Talent pools are first class: create, list, update, delete, and page through the candidates inside one. Upload File handles the document side by fetching a publicly reachable URL and forwarding it as a multipart upload. A few operational facts are worth designing around. Uploads accept PDF, TXT, DOCX, DOC, PNG, JPEG, and JPG up to 5 MB. The API is rate limited at 100 requests per minute per key and returns HTTP 429 beyond that, so bulk imports should be paced. Creating a candidate with a duplicate email returns an error that names the existing candidate ID, which is a useful signal rather than a failure. And API access requires a RecruSpace plan that includes it; without one, requests return HTTP 423. ### Without FlowRunner **Sourced candidates re-entered by hand**: The same CV is typed into a form after it was already read once **Screening notes scattered**: Feedback on a candidate lives in an email thread rather than on their profile **Talent pools decay quietly**: Candidates who were not right for one role are never grouped for the next one ### With FlowRunner **CVs move once**: Upload File and Create Candidate turn an attachment into a profile with a linked document **Notes and tags live on the candidate**: Add Note To Candidate and Add Tag To Candidate write screening context where the next recruiter will look **Pools are maintained by the flow**: Create Talent Pool and List Talent Pool Candidates keep future prospects organized without a cleanup project ## Use Case Scenarios ### Sourced Candidate Into a Talent Pool An agency sends a batch of CVs for a role that is not open yet. The agent downloads each file from [Google Drive](https://flowrunner.ai/integrations/google-drive-api), runs Upload File to get a document ID, and runs Search Candidate By Email to check for an existing record. New people get Create Candidate with the CV document ID, attached to a named talent pool rather than a job post, with the source platform set so attribution survives. Existing people get Add Note To Candidate recording the new submission and Add Tag To Candidate marking the specialism. When the role opens, List Talent Pool Candidates returns the pool with screening scores already attached. ### Screening Feedback Captured From Email A hiring manager replies to a candidate summary by email with their read on the person. The agent picks up the reply from [Gmail](https://flowrunner.ai/integrations/gmail-service), extracts the candidate's email address from the thread, runs Search Candidate By Email to resolve the candidate ID, and runs Add Note To Candidate with the manager's assessment and the platform label identifying where it came from. It adds a stage tag with Add Tag To Candidate so the pipeline view reflects the decision. Feedback that would otherwise stay in one inbox becomes part of the candidate's record within minutes of being written. ### Live Hiring Report Recruiting leadership wants a current view of open roles without logging in. On a schedule the agent runs List Job Posts with a status filter, runs Get Job Post for each to pull the seniority, salary range, and workplace type, and runs List Company Offices and List Company Users to resolve locations and owners into readable names. It writes the whole set to a sheet in [Google Sheets](https://flowrunner.ai/integrations/google-sheets), one row per post, with applicant counts and the responsible recruiter. The report is rebuilt from the source every morning rather than maintained by hand. ## Human-in-Loop Highlight Apply To Job Post requires the acceptance of terms of use as a parameter. An agent can set that value. It should not be the one deciding to. Submitting an application creates a formal record that a named person applied for a named job, with their contact details, employment history, and consent attached, and it is the candidate's reputation and inbox on the other end of it, not the company's. Nothing in the API can verify that the person actually asked to be put forward. So the agent assembles everything, the uploaded CV document ID, the education and work experience arrays, and an answer for each required item returned by List Job Post Questions, then stops and routes to the recruiter: "Ready to submit \[candidate name\] to \[job post title\]. This submission asserts their acceptance of the terms of use. Evidence of consent on file: \[their reply, dated\]. Confirm they agreed to be put forward, or send them the application link instead." The recruiter answers for the candidate's consent. Everything on the recruiter's own side of the relationship, uploads, pool management, notes, tags, and reporting, runs without a [human-in-the-loop](https://flowrunner.ai/concepts/human-in-the-loop) pause, because those are the company's records to change. Agent processes routinely Detects exception requiring judgment Clear match Continues automatically Ambiguous Routes to human via preferred channel Human decides Agent resumes with decision ## Agent Capabilities 17 actions ### Job Posts 4 - **List Job Posts** Lists job posts for the authenticated company with filtering, search, sorting, and pagination. Filter by status, employment type, workplace type, locations, or creator, and search by job title. Returns a paginated envelope with count, next, previous, and results. Each job post carries a hash identifier used by the other job post operations. - **Get Job Post** Retrieves the full details of a single job post by its hash identifier, including title, description, status, locations, workplace type, employment type, seniority, salary range, and the creating company user. - **List Job Post Questions** Lists the application questions configured for a job post. Each question includes a stable question key, the displayed text, the expected answer type, any choice options, and whether an answer is required. Read this before building an application so no required question is missed. - **Apply To Job Post** Submits a candidate application to a job post on behalf of an applicant. Requires the candidate email, first and last name, an uploaded CV document ID, acceptance of terms of use, and arrays of education and work experience entries, with optional answers to the job post questions. Routed for sign-off, because it asserts a real person's consent. ### Candidates 5 - **Search Candidate By Email** Searches for candidates by email address using partial matching, returning matching candidates with their ID and email. Used as the deduplication check before creating a record and as the lookup that resolves an email thread to a candidate. - **Get Candidate** Retrieves full details for a single candidate by ID, including contact information, CV and photo document links with presigned URLs, education, work experience, links, tags, AI screening score, and suitability. - **Create Candidate** Creates a candidate record from an already uploaded CV document. Requires the candidate email, first and last name, and a CV document ID from Upload File. Optionally attaches the candidate to a job post or a talent pool and sets the source platform. A duplicate email returns an error naming the existing candidate ID. - **Add Note To Candidate** Adds a text note to a candidate's profile, used for screening feedback, interview impressions, or internal reminders. Optionally sets the platform label identifying where the note came from. - **Add Tag To Candidate** Adds a tag to a candidate's profile to categorize and filter them, for example by skill, seniority, or hiring stage. Returns the created tag. ### Talent Pools 5 - **List Talent Pools** Lists all talent pools for the company, including the pool name, candidate count, creator, department, and assignees. Use a returned pool ID with the other pool operations. - **Create Talent Pool** Creates a new talent pool, a named group for organizing candidates for current or future roles. Returns the created pool with its ID. - **Update Talent Pool** Updates an existing talent pool's name, sample flag, department, and assignees. Omitted fields are left unchanged. - **Delete Talent Pool** Permanently deletes a talent pool. The candidates themselves are not deleted, only the pool grouping, but the grouping is not recoverable, so this is routed for confirmation rather than run in a cleanup pass. - **List Talent Pool Candidates** Lists the candidates inside a talent pool with pagination, returning a paginated envelope with count, next, previous, and results. Each candidate includes contact details, AI screening score, tags, and CV and photo document links. ### Company 2 - **List Company Offices** Lists all office locations configured for the authenticated company, including name, address, country, city, and which office is the default. Used to map job post locations to readable names in reporting. - **List Company Users** Lists all users belonging to the authenticated company, including their profile, permission level, role, invite status, and last login. Use the returned user IDs to filter job posts by creator or to identify the responsible recruiter. ### Files 1 - **Upload File** Uploads a file to RecruSpace from a publicly reachable URL, such as a FlowRunner file URL. Accepts PDF, TXT, DOCX, DOC, PNG, JPEG, and JPG up to 5 MB. Returns the created document with its ID and a presigned URL. Use the returned ID as the CV document ID in Create Candidate or Apply To Job Post. ## Frequently Asked Questions ### What can FlowRunner do with RecruSpace? FlowRunner agents can run List Job Posts, Get Job Post, and List Job Post Questions in RecruSpace, plus 14 more actions. ### Does connecting RecruSpace to FlowRunner require OAuth? No. RecruSpace connects to FlowRunner with an API key, no OAuth flow required. ### Can RecruSpace trigger a FlowRunner workflow automatically? RecruSpace doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger. **Work at RecruSpace?** This integration exposes RecruSpace to AI agents on every FlowRunner plan, including through MCP, at no cost to you. [See what FlowRunner offers integration partners](https://flowrunner.ai/integrations/partners), including how to keep this page current. --- Markdown version of https://flowrunner.ai/integrations/recruspace. Site index: https://flowrunner.ai/llms.txt