Integration

flex Open API integration

flex (flex.team) is a Korean HR platform, and its Open API is read-only. Read the organization (departments, department heads, job roles, ranks, titles, levels and groups, holidays, custom property definitions), employees (employee numbers, profiles, departments and titles, leaves of absence, daily changes, cost centers, business places), working time (schedules, clock events, time-off uses, annual leave balances) and payroll postings (journal entries for salary and severance pay). Answers carry employees' personal data; only records with a code set in flex (employee number, department or job code) appear, work and leave can only be changed in flex's own apps, and the API serves 1 request per second. Employee bank accounts and family details are not exposed, and resident registration numbers are removed from profiles. Authentication is OAuth2 client credentials: a flex admin issues a Client ID and Client Secret in flex's Open API settings (Client Credential method, on a plan that includes the Open API) and picks the information the credential may read; LiveContext requests the short-lived access token itself.

Connect flex Open API How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in flex Open API.Built from the 22 flex Open API tools below, on the connection you add once.

What you can do with flex Open API

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Work schedule, 4 operations

get_live_work_schedules_by_dateGet live work schedules by dateGETAgents: ask firstReturns the work schedules of 1 to 20 employees for one date, including work and breaks still in progress (a work block with no blockTo is ongoing), with each block's source. Personal data.
get_live_work_schedules_by_periodGet live work schedules by periodGETAgents: ask firstReturns the work schedules of 1 to 20 employees for a period of up to 31 days, including work and breaks still in progress (a work block with no blockTo is ongoing). Personal data.
get_work_schedules_by_dateGet work schedules by dateGETAgents: ask firstReturns the work schedules of 1 to 20 employees for one date (YYYY-MM-DD): work blocks and time-off blocks with times and minutes. Work still in progress is not included (see get_live_work_schedules_by_date). Personal data.
get_work_schedules_by_periodGet work schedules by periodGETAgents: ask firstReturns the work schedules of 1 to 20 employees for a period of up to 31 days: per day, work blocks and time-off blocks with times and minutes. Work still in progress is not included. Personal data.

Payroll posting, 2 operations

get_payroll_postingGet payroll postingGETAgents: ask firstReturns one payroll posting by postingId (from list_payroll_postings): its summary and its journal lines with posting key, debit or credit, account code, amount, cost center and payment fields.
list_payroll_postingsList payroll postingsGETAgents: ask firstLists the payroll postings (salary and severance pay journal entries) of a month (YYYY-MM): posting ID, title, posting and document dates, type. The credential needs the payroll posting scope.

Time off, 2 operations

get_time_off_uses_by_dateGet time off uses by dateGETAgents: ask firstReturns the time off (leave type, dates, and times for a partial day) that 1 to 20 employees take on one date (YYYY-MM-DD). Personal data.
get_time_off_uses_by_periodGet time off uses by periodGETAgents: ask firstReturns the time off (leave type, dates, and times for a partial day) of 1 to 20 employees for a period of up to 31 days. Personal data.

Annual leave, 1 operation

get_annual_time_offGet annual time offGETAgents: ask firstReturns the annual leave of 1 to 20 employees: grants with their valid date range, uses, adjustments, and the remaining balance in minutes and days. Personal data.

Business place, 1 operation

get_user_business_placesGet user business placesGETAgents: ask firstReturns the business place (name, code and local income tax withholding code) of 1 to 20 employees.

Clock event, 1 operation

get_clock_events_by_periodGet clock events by periodGETAgents: ask firstReturns the clock events (start, switch, stop, break start and stop) of 1 to 20 employees for a period of up to 31 days, with actual and credited times in UTC. Personal data.

Cost center, 1 operation

get_user_cost_centersGet user cost centersGETAgents: ask firstReturns the cost center code of 1 to 20 employees.

Custom property, 1 operation

list_custom_propertiesList custom propertiesGETAgents: ask firstLists the custom property definitions that have a key set, grouped by category, with name, key, help text and sort order. Each employee's values are in customProperties of get_user_masters, under the same key.

Department, 1 operation

list_departmentsList departmentsGETAgents: ask firstLists the current departments that have a department code set, with parent code, name, description, sort order, visibility and open and close dates.

Department head, 1 operation

list_department_headsList department headsGETAgents: ask firstReturns the current heads of 1 to 20 departments (codes from list_departments): direct heads, and the resolved first-line heads taken from the nearest parent department when a department has none.

Employee, 1 operation

get_user_mastersGet user mastersGETAgents: ask firstReturns the profiles of 1 to 20 employees: name, English name, email, phones, birthday, gender, home address, join and leave dates, contract type, primary department and job codes, custom values. Personal data.

Employee change, 1 operation

list_user_changesList user changesGETAgents: ask firstLists the employees created, updated or deleted on a date (YYYY-MM-DD), up to 20 per page; pass nextPageKey as pageKey while hasNext is true. Today's date can return changes that are not final yet.

Employee department, 1 operation

get_user_departmentsGet user departmentsGETAgents: ask firstReturns the departments and job titles of 1 to 20 employees as of a reference date (default today): department code and name, primary flag, head flag, display order and job title.

Employee number, 1 operation

list_employee_numbersList employee numbersGETAgents: ask firstLists employee numbers, up to 20 per page; pass nextPageKey from the previous answer while hasNext is true. Only employees with an employee number set in flex are listed. Employee numbers feed every per-employee tool.

Holiday, 1 operation

list_holidaysList holidaysGETAgents: ask firstLists the company's holidays per holiday group between two dates (inclusive, at most 366 days): statutory public holidays (substitute holidays included) and the company's own holidays.

Job item, 1 operation

list_job_itemsList job itemsGETAgents: ask firstLists the job codes that have a code set: job roles, job ranks, job titles, job levels and job groups, each with its code and name.

Leave of absence, 1 operation

get_user_leaves_of_absenceGet user leaves of absenceGETAgents: ask firstReturns the leaves of absence (begin and end dates) of 1 to 20 employees. Personal data.

Use flex Open API from Claude Code, Cursor or Codex

Connect flex Open API in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its flex Open API operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect flex Open API

Create your workspace
Sign up free. Nothing to install.
Connect flex Open API once
Add your flex Open API connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.