JOBka
HRConnect AI agents to JOBka, a Czech employee communication and HR app for frontline teams. Agents manage employees and groups, publish and notify posts, and move files in and out of storage so company updates reach every worker automatically.
What This Integration Enables
JOBka is built for the part of the workforce that does not have a company laptop. It calls itself the company in your pocket, and every design decision follows from that. Content is organized into post-list modules such as news, health and safety, or HR announcements. Delivery can escalate to email and SMS, and a post can be shown as a pop up. Most importantly, the platform tracks not just whether a post was sent but whether each employee read it and confirmed it. Group membership decides who receives what, which makes the employee roster the thing that determines reach.
Agents work both halves. On the people side they list and read employees with filters on display name and personal number, create, update, and delete them, and move them in and out of groups by numeric id. Groups themselves are created, read, updated, and deleted, with a type that controls hierarchy and an optional managing admin drawn from the backoffice administrator list. On the content side agents enumerate the post-list modules and read posts with their scheduling and confirmation configuration. They create a post with a title and HTML body targeted at every employee or at a specific set of groups and employees, publish a draft, and send follow up notifications scoped to everyone, to those who have not confirmed, or to those who have not read. Files move both directions: Upload File puts a FlowRunner file into JOBka storage so it can be attached to a post, and Download File pulls a JOBka file back into FlowRunner storage.
Two operational details matter when building flows. Publish times are handled in UTC while the company profile carries its own configured time zone, so an agent scheduling a morning announcement should read Get Company and convert rather than assume. And API access is not self-service: the Client ID and Client Secret are issued by JOBka support, and the service exchanges them for a short-lived token on each run, so the credential setup is a request to the vendor rather than a checkbox in an account screen.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Roster Sync From the HR System
Employment changes are recorded in the HR system of record. On a schedule the agent reads new hires, role changes, and departures from BambooHR, then reconciles them against JOBka. New starters get Create Employee with their display name and personal number, followed by Add Employee To Group for their site and shift. Role changes trigger Update Employee and a pair of group moves, Remove Employee From Group for the old team and Add Employee To Group for the new one, so a worker who moves from nights to days stops receiving the night shift feed the same day. Departures are staged rather than executed, because Delete Employee is permanent and cannot be undone.
Safety Notice With Confirmation Chasing
A revised safety procedure is approved. The agent runs Upload File for the PDF, then Create Post in the health and safety module with the title, the HTML body, the attachment, and the target groups, leaving the publish time empty so it stays a draft. After the internal communications owner approves, Publish Post makes it visible. Two days later the agent runs Get Post to read the confirmation configuration and runs Notify Post scoped to recipients who have not confirmed, using the confirmation reminder type. Three days after that it does the same for those who have still not read it. The chase happens on its own; the decision to escalate to a reminder was made once, in advance.
Document Archive Out of the App
Compliance needs a record of what was published and what was attached. On a monthly schedule the agent walks List Post Modules, runs List Posts per module for the period, and runs Get Post for each to capture scheduling, delivery settings, and the default translation content. For every attachment it runs Get File Metadata and Download File to bring the file into FlowRunner storage, then writes the whole set into a dated folder alongside a manifest sheet in Google Sheets. The archive matches what employees actually saw, rather than what someone believes was sent.
Human-in-Loop Highlight
The dangerous operation in JOBka is not a delete, it is a send. Notify Post pushes a notification for a published post to a chosen recipient set, and Create Post can enable email and SMS delivery, which means a mistargeted announcement reaches personal phones belonging to people who may be mid shift or asleep. There is no unsend, and an SMS blast to an entire frontline workforce is felt immediately by everyone who receives it. So the agent always creates the post as a draft, with the publish time left empty, and stops there. It routes to the internal communications owner with the numbers made explicit: "Draft ready in [module]. Targeting [group names], which currently resolves to [N] employees. Email delivery on, SMS delivery on, pop-up on. Publish time [local time] in the account time zone. Approve, narrow the audience, or turn SMS off?" Roster syncs, group moves, drafting, and archiving run unattended. Anything that makes a phone buzz in someone's pocket goes through a human-in-the-loop check first.
Agent Capabilities
23 actionsCompany
1- Get Company Returns the JOBka company profile for the connected account, including its display name, configured time zone, and the languages enabled for content and translations. Read this before creating multilingual posts or scheduling a publish time, since publish times are handled in UTC.
Employees
5- List Employees Lists employees with optional filters by display name or personal number, paginated up to 100 per page by default. Returns each employee's id, display name, personal number, contact details, and state.
- Get Employee Retrieves a single employee by numeric id, including contact details, current state, the groups they belong to, and their registered access tokens. Used to inspect an employee before updating them or changing their group membership.
- Create Employee Creates a new employee. Display name and personal number are required; email, phone, and a free text note are optional. Returns the id of the new employee for use with Add Employee To Group or Update Employee.
- Update Employee Updates an existing employee by numeric id. Display name and personal number are required and replace the current values; email, phone, and note are optional. Fields left empty are omitted from the update request.
- Delete Employee Permanently removes an employee from the account by numeric id. This cannot be undone, so verify the id with Get Employee first and route the removal for confirmation rather than running it inside an unattended sync.
Groups
7- Add Employee To Group Adds an employee to a group by numeric ids. Membership controls which posts and content the employee receives, so this operation is what actually changes a person's reach.
- Remove Employee From Group Removes an employee from a group by numeric ids. The employee stops receiving content targeted at that group. Neither the employee nor the group is deleted.
- List Groups Lists employee groups with an optional display name filter, paginated up to 100 per page by default. Returns each group's id, display name, note, and type. Used to resolve an audience and its size before a post goes out.
- Get Group Retrieves a single group by numeric id, including its display name, note, type, assigned admin, and parent group.
- Create Group Creates a new employee group. Display name is required. Group type controls hierarchy, and a subgroup requires a parent group id. Optionally assigns a managing admin and a note.
- Update Group Updates an existing group by numeric id. Display name is required, and the group type, note, and assigned admin can be changed. Read Get Group first to confirm current values.
- Delete Group Permanently deletes an employee group by numeric id. Employees are not deleted but lose membership in this group, which silently changes who receives future posts. Cannot be undone.
Posts
6- List Post Modules Lists the post-list modules configured in the account. Each module is a separate stream of posts, for example news, health and safety, or HR announcements, identified by a module id used by the other post actions.
- List Posts Lists posts within a specific post-list module, paginated up to 100 per page by default. Returns each post's id, title, publish and expiry timestamps, delivery settings, and pop-up flag.
- Get Post Retrieves a single post by module id and post id, including scheduling, delivery settings, confirmation configuration, and default translation content. Read this before publishing or before sending a reminder.
- Create Post Creates a post in a post-list module with a title and HTML body for the default translation. Targets every employee, or a specific set of groups and employees. Optionally schedules a publish time in UTC, controls email and SMS delivery, and shows the post as a pop up. Leaving the publish time empty creates it as a draft, which is how a flow stages content for approval.
- Publish Post Publishes an existing draft post so it becomes visible to its targeted recipients. Routed for sign-off, because the audience and the delivery channels are both decided at this moment.
- Notify Post Sends a notification for an already published post to a selected set of recipients: everyone, only those who have not confirmed, or only those who have not read it. The notification type can be a standard notification, a reminder, or a confirmation reminder. Routed for sign-off, since delivery can include SMS to personal phones.
Files
3- Upload File Uploads a FlowRunner file to JOBka file storage and returns the JOBka file id, which can be referenced as an attachment in posts.
- Get File Metadata Retrieves metadata for a JOBka file by its file id, including the stored file name, size in bytes, and MIME type.
- Download File Downloads a JOBka file by its file id into FlowRunner file storage, returning the saved file URL along with the file name, MIME type, and size. Used to archive published attachments outside the app.
Administrators
1- List Admins Lists backoffice administrators in the account with their id, display name, and contact details. Used to find admin ids when assigning group managers.
Frequently Asked Questions
What can FlowRunner do with JOBka?
FlowRunner agents can run Get Company, List Employees, and Get Employee in JOBka, plus 20 more actions.
Does connecting JOBka to FlowRunner require OAuth?
JOBka uses a custom authentication method to connect to FlowRunner.
Can JOBka trigger a FlowRunner workflow automatically?
JOBka doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with JOBka
$100 in credits. No card required. Connect in minutes.