Overview

Glossary of key terminology to know when working with the HrFlow.ai Platform

Connectors Marketplace

Connectors are one of the main HrFlow.ai's core product offering: you can collect Talent data from your websites, mobile apps, and servers with one API, then pull in contextual data from cloud apps like your CRM, SSO, HRMS, LMS, and internal databases to build a unified picture of your Talent data.

Connector

Description

Source

Board

Destination

HCM

Human Capital Management

✔️

✔️

✔️

HRIS

Human Resources Information Systems

✔️

✔️

✔️

ATS

Applicant Tracking System

✔️

✔️

✔️

HR Tech

Human Resources Technology

✔️

✔️

✔️

HR CRM

Customer Relationship Management used for HR

✔️

✔️

✔️

HR ERP

Enterprise Resource Planning used for HR

✔️

✔️

✔️

Databases

Electronic and Cloud data storage

✔️

✔️

✔️

Mailbox

Gmail, Office, Imap, SMTP, Redirection, Email Clients

✔️

✔️

Cloud Apps

Online Hosted Applications

✔️

✔️

✔️

Local Apps

Locally Hosted Applications or Server

✔️

✔️

✔️

BI Platforms

Analytics, Business Intelligence Dashboards

✔️

Marketing tools

Email and SMS Push Notification Tools

✔️

✔️

✔️

Productivity

Project Management and Time Management Tool

✔️

✔️

✔️

🚧

Inbound Data Segmentation

We highly recommend creating a Source of profiles and a Board of jobs for each unique channel of data (each site, app, or server), though this isn’t required.

Sources

Sources are a family of Connectors that simplifies profiles, resumes, and CV data collection from any website, database, or tool.

Boards

Boards are a family of Connectors that simplifies job offers data collection from any website, database, or tool.

Destinations

Destinations are a family of Connectors that simplifies sending profiles and job offers data to any website, database, or tool.

API Clients

We’ve developed API clients for the most common programming languages and platforms. These clients are advanced wrappers on top of our REST API itself and have been built in order to help you integrate our service within your apps. For example, you might choose to use our PHP client for your indexing logic, while your front-end relies on our JavaScript client. All our clients are open-source and available on Github.

Workflows

Allows to collect and transform any stream of first-party data via webhooks (Workflow CATCH) or CronJob (Workflow PULL) into HrFlow.ai . With just ten lines of Python code, you can build any integration —no additional infrastructure required. Scale from point-to-point integration to complex workflows, using conditional logic and processing billions of tasks in just milliseconds.

📘

Main use cases of Workflows

Automations with custom Business logic, Syncing profiles and jobs between apps automatically.

Item

An item is the profile or job data you're providing into the platform. Items are indexed so that they can be used for Searching, Scoring, and Reasoning. You can also add your own tags and metadata to Items to use for Searching or when training your own Scoring Algorithm.

Indexing

Indexing collects and stores your Items in a Connector to facilitate fast and accurate information retrieval.
Indexing happens automatically every time you add new Items to a Connector.

🚧

Indexing can be a prerequisite

Indexing is mandatory for storage and enables Searching, Scoring, Reasoning, and algorithm training

📘

Resume Indexing after Parsing

When you Parse a resume or upload it to a Source, it is automatically indexed by default unless you change the default parameter to false.


Did this page help you?