Gamfi
HRConnect AI agents to Gamfi, the employee onboarding and lifecycle platform. Agents add employees, start and manage workflow processes, complete actions, and download reports so onboarding runs on schedule with a full paper trail.
What This Integration Enables
Gamfi is a people platform built around one object: the process. A process is a running instance of a workflow attached to a named employee, made up of actions that someone is expected to complete. Onboarding is the obvious case, but the model covers any lifecycle sequence a company wants to run consistently across people. Everything in this connector either creates a process, moves one along, reports on one, or closes one out.
FlowRunner agents work that object model directly. They add an employee to the Gamfi application with their name, email, and company, and look one up by ID, email, or phone number. They list the companies and the workflow templates configured in the account, which is where the IDs for everything else come from, and List Workflows also reports whether a workflow contains SMS or email actions. They start a process for an employee against a workflow with a key date, and list every running process with its employee, manager, status, progress, and action counts. They mark a single action complete, and add an action to a running process as long as that action exists in the underlying workflow. Three report operations download process, business sequence, and workflow reports into FlowRunner file storage and return a URL that later steps in the flow can use.
Two behaviors change how these flows should be built. Start Process creates a Gamfi account for any employee or role participant who does not already have one, using the details supplied, and the workflow it starts may contain SMS and email actions that reach that person directly. Starting a process is therefore not a bookkeeping entry. It contacts a human being. And the two ways out of a process are not equivalent: Close Process sets the status to Completed without counting the individual actions inside it, while Delete Process removes the process permanently and cannot be undone. One rewrites the conclusion, the other destroys the evidence. FlowRunner's connectors are built and verified against each vendor's official API, and both of these are documented Gamfi behaviors rather than edge cases to be discovered in production.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The Quarterly Close That Reads the Actions
At quarter end somebody has to decide what to do with onboarding processes that never finished. The agent runs List Processes and sorts every open process into two groups using progress and action counts: those where the remaining actions are administrative leftovers, and those where a required action, a policy acknowledgment or a mandatory training step, is still untouched. It runs Download Process Report so the detail behind each judgment is attached rather than summarized. The people operations owner gets both lists, grouped by the responsible manager. They close the first group and route the second group back to managers with a named owner and a date. The clean up still happens quarterly. What changes is that Completed now means the same thing on every record.
Hire to First Day, Without the Second Entry
A candidate is marked hired in the recruiting tracker. The agent reads the record from Airtable, resolves the right entity with List Companies and the right template with List Workflows, and runs Add Employee followed by Start Process with the start date as the key date. Because the chosen workflow contains email actions, the process itself begins contacting the new hire on Gamfi's schedule, which is the point of running onboarding in a platform rather than in a checklist. The agent posts the started process and its workflow name to the hiring manager in Slack so the manager knows what their new joiner is about to receive and can object before day one rather than after.
Reports Where the Rest of the Business Reads Them
HR reporting rarely lives in the HR tool. On a monthly schedule the agent runs Download Process Report, Download Business Sequence Report, and Download Workflow Report for the templates that matter, each of which lands in FlowRunner file storage with a URL. It uploads the files to the HR reporting folder in Google Drive and writes a short summary of the headline movements. Nobody exports anything by hand, and the same three reports arrive on the same day every month, which is what makes a trend readable.
Human-in-Loop Highlight
The gate sits on closing a process, and the reason is in Gamfi's own description of the operation: Close Process changes the status to Completed without counting the individual actions inside it. That is a useful escape hatch when a person genuinely finished their onboarding outside the tool. It is a quiet falsification when the process stalled because a mandatory step was never done, because the record afterward says the same thing in both cases. Delete Process is worse in a different direction, since it removes the process permanently and takes the evidence of what was actually completed with it. So an agent may find, sort, and evidence every stale process, and it stops there. The message reads: "14 onboarding processes open more than 90 days. 9 have only reminder actions outstanding. 5 have an untouched Policy Acknowledgment action, listed by employee and manager. Close the 9, or review all 14 first?" A named owner answers, and the agent closes exactly what was approved. This is human-in-the-loop protecting an audit trail rather than a transaction. Nobody loses money when a process is closed wrongly. What is lost is the ability to prove, later, that a person was actually trained.
Agent Capabilities
13 actionsEmployees
2- Add Employee Add an employee to your Gamfi application so they can use the platform. Requires first name, last name, email, and a company ID from List Companies. Returns the created user record with its numeric ID.
- Get Employee Retrieve one employee's profile by numeric ID, email address, or phone number, including assigned locations, categories, and custom fields.
Configuration
2- List Companies Return the companies configured in the application with ID, name, and description. Used to resolve the company ID that Add Employee and Start Process require.
- List Workflows Return the workflow templates available in the application with ID, name, category, and whether the workflow contains SMS or email actions. Read that last field before starting anything, because it tells you whether the process will contact the employee directly.
Processes
4- Start Process Start a workflow based process for an employee against a workflow ID and a key date. If the employee has no Gamfi account, one is created from the details supplied.
- List Processes Return running processes with the associated employee, workflow, manager, status, progress, and action counts. This is the source for any hygiene review or dashboard.
- Close Process Close a single process by setting its status to Completed. This does not count the individual actions inside the process, so it records an outcome rather than verifying one.
- Delete Process Permanently delete a process. This cannot be undone and removes the record of what was completed inside it.
Actions
2- Complete Action Mark a single action within a process as Completed, by process ID and action ID.
- Add Action To Process Add an action to an existing process. The action must already exist in the workflow the process is based on.
Reports
3- Download Process Report Download the process report and store it in FlowRunner file storage, returning a URL for later steps in the flow.
- Download Business Sequence Report Download the process report in the context of business sequences and store it in FlowRunner file storage, returning a URL.
- Download Workflow Report Download a report for a specific workflow ID and store it in FlowRunner file storage, returning a URL.
Frequently Asked Questions
What can FlowRunner do with Gamfi?
FlowRunner agents can run Add Employee, Get Employee, and List Companies in Gamfi, plus 10 more actions.
Does connecting Gamfi to FlowRunner require OAuth?
No. Gamfi connects to FlowRunner with an API key, no OAuth flow required.
Can Gamfi trigger a FlowRunner workflow automatically?
Gamfi doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with Gamfi
$100 in credits. No card required. Connect in minutes.