FlowRunner
PricingContact
Theme
Start Free

Hirely

HR

Connect AI agents to Hirely, a German applicant tracking system for recruiting teams and agencies. Agents publish job postings, capture and progress applications, and hire or reject applicants so every candidate moves through the pipeline on time.

Verified 46 actions API key available
Hirely website ↗ Platform Documentation ↗ Capability data verified 2026-08-10
A signed client brief lands in the shared drive with an approved role
Agent reads the role details, location, employment terms, and salary band from the brief
Agent runs List Companies and matches the client to exactly one managed company id
Agent runs Create Job Posting in draft, then Update Job Posting with the details, highlights, and application process
Agent runs Get Job Posting and compares the rendered draft against the brief field by field
Account owner receives the draft preview, the resolved company name, and the career page it will appear on
Owner confirms the target company and approves Publish Job Posting

What This Integration Enables

Hirely is an applicant tracking system built for German recruiting teams and, importantly, for agencies running hiring on behalf of other companies. That second audience shapes the whole API. Every operation takes a Company parameter, and List Companies can return managed client companies alongside your own. An agency account adds customers and recruiting campaigns on top. One API key, several employers, and the company id is what keeps them apart.

The surface is broad. Agents manage company profiles, users, permission roles, locations, and highlights. They define hiring pipelines through application processes. They also run the full job posting lifecycle: create as a draft, update with employment details, salary, remote options, and the assigned process, publish to the public career page, then archive to pull it back. Deletion is available too, though Hirely itself advises against it because archiving preserves the data. On the candidate side they list and read applications, create them from external forms with the option to suppress team notifications and hold the automated process actions, update tags and source, add and remove internal comments, correct the person record behind the applications, and mark an applicant hired or rejected. Recruiting tasks with deadlines and priorities sit alongside, and webhook subscriptions can be created and removed so Hirely posts events to an endpoint you control. This connector itself has no triggers, so flows here start from a schedule, a document arriving, or an event another system raises.

Without FlowRunner

Client postings retyped per system The same role is entered into a brief, a posting, and a tracker with three chances to drift
Company scope held in someone's head An agency key reaches several client accounts and the right one is chosen from memory
Candidate decisions recorded loosely Hires and rejections are marked at some point, with the reasoning in a chat thread

With FlowRunner

Postings assembled from the brief Create Job Posting and Update Job Posting build the draft from the approved source document
Company resolved before the write List Companies pins the target account and the agent refuses an ambiguous match
Decisions written where they belong Hire Applicant and Reject Applicant run after sign-off, with the reason logged by Add Comment

Use Case Scenarios

Brief to Live Posting for an Agency Client

An agency receives a signed brief for a warehouse supervisor role at a client company. The agent reads the brief, runs List Companies to resolve the client to a single company id, and runs List Locations to find the work site. It creates the posting in draft with Create Job Posting, fills in the title, employment details, salary, and remote options with Update Job Posting, attaches the relevant selling points from List Highlights, and assigns the pipeline with the process id from List Application Processes. It then runs Get Job Posting and diffs the draft against the brief. The account owner sees a preview and the resolved client name before anything goes public. Publish Job Posting runs only after that confirmation.

External Application Form Into the Pipeline

Applications arrive through a careers microsite that is not Hirely. The agent receives each submission, runs List Job Postings to map the selected role to a posting id, and runs Create Application with the applicant's first name, surname, email, phone, cover letter, and source. For bulk imports it can suppress team notifications and prevent the first automated process actions from firing, so a backfill of two hundred historical applicants does not send two hundred acknowledgement emails. It then runs Add Comment to record where the application came from and what the agent checked, and Create Task with a deadline so a recruiter owns the first response.

Pipeline Hygiene and Team Access Review

On a weekly schedule the agent runs List Applications per company and finds candidates sitting in the same phase past the agreed response window. It assembles a digest per recruiter with the applicant, the posting, the phase, and how long they have waited, and posts it to Slack with a Create Task per stalled candidate. In the same pass it runs List Users and List Permission Roles across the managed companies and flags accounts that still hold access to a client the agency no longer works with, staging Remove User calls for the operations lead to confirm. Neither the response chase nor the access review depends on someone remembering to run it.

Human-in-Loop Highlight

Publish Job Posting is the moment a draft becomes a public web page under an employer's brand, and on an agency key that employer may not be your own company. Reversal is partial at best: Archive Job Posting removes the posting from the career page, but it does not un-send the applications that arrived, un-index the page, or un-tell a client that their salary band was published with the wrong number. So the agent builds the posting, verifies it with Get Job Posting, and then stops. It routes to the account owner with the specifics that actually carry risk: "Ready to publish [title] to the career page of [company name], resolved from List Companies as company id [id]. Salary [band], location [site], application process [name]. This goes live on their public page. Approve, correct a field, or reassign the company?" Draft assembly, field validation, and duplicate checks run unattended. Putting a client's name on a live advert gets a human-in-the-loop confirmation, and Delete Job Posting is never run by the agent at all, since Hirely recommends archiving instead.

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

46 actions

Companies and Access

7
  • List Companies Lists every company (account) the API key can access, which for agencies can include managed client companies. Each item includes the company ID, display name, official name, contact details, public links, and logo image URLs. Run this first to pin the Company parameter used by every other operation.
  • Get Company Retrieves a single company by its ID, including its official name, public contact details, career page links, logo image URLs, and custom scripts.
  • Update Company Updates a company's profile fields such as display name, official name, public email and phone, and website, imprint, and data protection URLs. Only the fields you provide are changed.
  • List Users Lists all users who have access to the given company, including their names, email addresses, and assigned permission roles. Used for periodic access reviews across managed clients.
  • Invite User Invites a user to the company by email, optionally assigning a permission role by its ID. When no role is given the company default is assigned. The invited person receives an email invitation.
  • Remove User Removes a user from the company so they can no longer access it. The user's account is not deleted, only their membership in this company.
  • List Permission Roles Lists all permission roles defined for the company. Use a role's ID when inviting a user to control the access that user receives.

Locations and Highlights

4
  • List Locations Lists all locations (work sites) configured for the company, each with its address. Use a location ID when creating or updating a job posting.
  • Get Location Retrieves a single company location by its ID, including its full address.
  • List Highlights Lists all highlights (selling points) defined for the company, each with an icon, title, and description. Highlights can be attached to job postings to showcase benefits.
  • Create Highlight Creates a company highlight that can be shown on job postings. Provide a Font Awesome icon identifier, a title, and a description.

Application Processes

5
  • List Application Processes Lists all application processes (hiring pipelines) defined for the company. A process defines the phases a candidate moves through. Use a process ID when creating or updating job postings.
  • Get Application Process Retrieves a single application process by its ID, including its name, description, and phases.
  • Create Application Process Creates a new application process for the company with a name and an optional description.
  • Update Application Process Updates an existing application process. Only the fields you provide are changed.
  • Delete Application Process Permanently deletes an application process from the company. Destructive, so route it for confirmation rather than running it inside an unattended cleanup.

Job Postings

7
  • List Job Postings Lists job postings (job offers) for the company, including status, location, application counts, and public links. For agencies the list can optionally be restricted to specific managed companies.
  • Get Job Posting Retrieves a single job posting by its ID, including status, location, application form configuration, highlights, statistics, and public links. Used to validate a draft before it is published.
  • Create Job Posting Creates a new job posting in draft status from a name and a location. The posting is not public until it is published.
  • Update Job Posting Updates an existing job posting: title, location, employment details, salary, remote options, and the assigned application process. Only the fields you provide are changed.
  • Publish Job Posting Publishes a job posting so it becomes accessible over the internet on the company career page. Routed for sign-off, because it puts a live advert under a named employer's brand.
  • Archive Job Posting Archives a public job posting to remove it from the career page while keeping its data. Hirely recommends archiving over deletion.
  • Delete Job Posting Permanently deletes a job posting. Hirely recommends archiving instead so the posting's data is preserved.

Applications

7
  • List Applications Lists applications (candidates) for the company, including the applicant, the job posting they applied to, the current phase, and status. Used to find candidates stalled past a response window.
  • Get Application Retrieves a single application by its ID, including the applicant's person data, the job posting, cover letter, documents, and status.
  • Create Application Creates a new application for a job posting from the applicant's first name, surname, and email, with optional phone, salutation, cover letter, and source. Team notifications and the first automated process actions can both be suppressed, which is what makes a safe bulk import possible.
  • Update Application Updates an existing application's cover letter, tags, and source. Only the fields you provide are changed.
  • Hire Applicant Marks an application as hired, moving the candidate to the hired state. Run after a human decision, with the reason recorded by Add Comment.
  • Reject Applicant Marks an application as rejected, moving the candidate to the rejected state. Run after a human decision, with the reason recorded by Add Comment.
  • Delete Application Permanently deletes an application together with all of its associated documents.

Comments and People

4
  • List Comments Lists all comments on an application. Comments are internal notes visible to your team.
  • Add Comment Adds an internal comment to an application, visible to your team, supporting up to 10000 characters without HTML tags. Used to record what an agent checked and which person approved a decision.
  • Delete Comment Deletes a comment from an application.
  • Update Person Updates a person's contact data such as salutation, name, email, and phone. A person is the individual behind one or more applications, so a correction here follows them across every application they hold.

Tasks

5
  • List Tasks Lists all of your tasks in the company, including title, deadline, priority, and completion state.
  • Get Task Retrieves the details of a single task by its ID.
  • Create Task Creates a new task with a title and optional description, deadline, and priority. Deadlines use the format YYYY-MM-DD HH:MM:SS.
  • Update Task Updates an existing task's title, description, deadline, and priority, or marks it completed by setting a completion timestamp. Only the fields you provide are changed.
  • Delete Task Permanently deletes a task from the company.

Webhooks

3
  • List Webhooks Lists all webhook subscriptions for the company, including each webhook's target URL and the events it listens for.
  • Create Webhook Creates a webhook subscription that sends a POST request to a URL you control whenever one of the selected events occurs, such as an application being created or a job posting being published.
  • Delete Webhook Deletes a webhook subscription so it no longer receives events.

Agency

4
  • List Customers Lists all customers managed by an agency. Available only for accounts registered as agencies.
  • Create Customer Creates a new customer company managed by your agency. All address fields are required, and the customer can optionally be assigned to a customer group. Agency accounts only.
  • List Campaigns Lists all recruiting campaigns for the agency. Agency accounts only.
  • Create Campaign Creates a new recruiting campaign for a customer managed by the agency, from a title and the customer's company ID, with an optional description and start date. Agency accounts only.

Frequently Asked Questions

What can FlowRunner do with Hirely?

FlowRunner agents can run List Companies, Get Company, and Update Company in Hirely, plus 43 more actions.

Does connecting Hirely to FlowRunner require OAuth?

No. Hirely connects to FlowRunner with an API key, no OAuth flow required.

Can Hirely trigger a FlowRunner workflow automatically?

Hirely doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with Hirely

$100 in credits. No card required. Connect in minutes.