Yeeflow

Yeeflow is the no-code workflow and application platform. Agents create and update list items with fields and files, start workflows and complete their tasks, set delegations and variables, manage users, departments, groups, and positions, and react to webhook events.

Verified 1 trigger 76 actions API key available

Yeeflow website Capability data verified 2026-08-24

A supplier invoice arrives and has to enter the approval process

Get List Fields and Get Form Variables resolve the field keys this application was built with

Create List Item files the invoice data and Attach File To Item stores the document with it

Start Workflow submits the request, naming the requester it is being filed for

List Pending Tasks confirms the task reached the approver the process named

Agent posts the task with the values it extracted and any discrepancy it found

The named approver decides, and the agent records only the outcome that person chose

What This Integration Enables

Yeeflow is a no-code platform for building internal applications, and the applications people build on it are approval processes: purchase requests, onboarding checklists, change requests, expense claims. That makes this connector different from most of the catalog. Yeeflow is not a passive store an agent writes to. It is a system whose entire design is that a named person acts at a named step, and it already knows who that person is.

FlowRunner agents work with that rather than around it. They read a list's field definitions before writing, because a Yeeflow list is whatever the person who built the app made it and there is no fixed schema to code against. They create and update items singly or in batches, attach files, start workflows on behalf of a requester, read the pending task queue, set form and task variables, and manage the organization structure the routing depends on: users, departments, locations, groups and positions. Positions are worth calling out, because a position can be held globally or only within a department or location, which is what lets a process route to "the finance manager of that office" rather than to a hard-coded name. Every one of these operations is built and verified against the Yeeflow official API.

One naming note, because it causes real confusion. Yeeflow calls a packaged, reusable action inside an application an "agent". Those are the things List Application Agents and Run Agent deal with. Throughout this page, the FlowRunner side is the flow and the Yeeflow side is the application agent.

Without FlowRunner

Requests filed by hand Someone opens the application, retypes what an email already said, and attaches the file again

Approvers chase their own inbox A pending task waits until the approver happens to look, and nobody upstream knows it is waiting

Integrations bypass the process A shortcut that writes straight into the list skips the workflow, so the audit trail has a hole in it

With FlowRunner

Requests filed from their source Data and documents land in the list and the process starts from the system the request came from

Pending work comes to the approver The task, its variables and the context around it arrive on the channel the approver already watches

The process stays the process Items enter through the workflow rather than around it, so the approval history stays complete

Use Case Scenarios

Requests that file themselves and still go through the process

An invoice arrives in a monitored mailbox. A flow extracts the supplier, amount, purchase order reference and due date, resolves the field keys with Get List Fields, and creates the item with the document attached. Then it calls Start Workflow rather than leaving the item sitting in a list, so the request enters the approval chain the business actually designed, with the requester named on it. The approver sees a complete request instead of a stub. When the process finishes, the approved invoice moves on to QuickBooks Online and the result posts back to the requester. Nothing skipped a step to get there.
An approval queue that does not depend on somebody logging in

List Pending Tasks answers what is waiting and for whom. A flow sweeps it on a schedule, groups by assignee, and posts each person their queue in Slack with the request values already summarized from Get Task Variables. Items that have waited past their service level are escalated to the line manager rather than repeated at the same person. Where somebody is genuinely away, the flow raises the delegation question to their manager rather than creating one on its own, because moving somebody's approvals to a colleague is a change in who holds authority.
Joiners, movers and leavers kept in step with the HR system

When a hire is confirmed upstream, a flow calls Create User with the invitation email switched on, files them into their department, and adds them to the groups their role needs. It then assigns their position scoped to the office they work in, so every workflow that routes by role reaches them correctly from day one. When someone leaves, the flow uses Disable User rather than Delete User: their sign-in stops, and their records and their history in every workflow they touched stay intact. Offboarding that erases a person from an approval history is not tidier. It is a broken audit trail.

Human-in-Loop Highlight

Process Task is the operation that separates this integration from a data sync, and it is the one an agent should not use on its own. Its outcome can be Approve or Reject, which means an API key can stand in as the approver of record on a step a business designed for a named human. The approval history will show the step as completed. It will not show that nobody read the request.

So a FlowRunner flow prepares the task and hands over the decision. It reads the variables, checks the invoice against the purchase order, resolves the vendor, and writes what it learned back with the outcome that changes nothing, so the working data is saved without the task moving. Then it posts to the person the workflow named: "PO-4471 from Halstead Supply, 12,480. Line totals match the purchase order, but the delivery note is three units short and the contract's price expired last month. Approve, reject, or ask the requester?" The approve or the reject is theirs, and Process Task carries only the outcome they chose. The same discipline covers Create Delegation and Enable Delegation, which reroute somebody's approvals to a colleague. That is a change in who is authorized, not a convenience setting, and a flow proposes it rather than performing it. Yeeflow already built the place where a person decides, and FlowRunner's job is to make sure a person is still the one standing in it. That is the whole human-in-the-loop commitment, applied to a system that shares it.

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

76 actions

Lists and Items

Get List Returns a list's general information. Field definitions come from the operation below rather than from here.
Get List Fields Returns a list's built-in and custom fields. Run it first: a Yeeflow list is defined by whoever built the application, and its field names are the keys every item operation wants.
Query List Items Reads items with filters, sorting and paging, narrowing the returned fields because a Yeeflow list can be very wide.
Get List Item Returns one list item.
Create List Item Adds an item to a list, keyed by field name rather than by column index.
Create List Items In Batch Adds many items in one call. Workflow triggering is off by default here, so an import does not start the processes a single create would unless the flow turns it on.
Update List Item Changes only the fields given. It carries a row version, so an edit made elsewhere in the meantime is refused rather than silently overwritten.
Update List Items In Batch Changes many items in one call, each with its own values.
Delete List Item Removes one item from a list.
Delete List Items In Batch Removes several items from a list in one call.
Attach File To Item Uploads a file into a named attachment field on an item, which matters because a list can have several.
Add File To Document Library Uploads a file into a document library list, creating the folder path along the way if it does not exist yet.
Download Document Library File Downloads a document library file into FlowRunner file storage and returns its URL.

Users

Get User By Account Returns a user by their login account, which is usually their email address.
Get User Returns one user by identifier.
Search Users Searches users with paging. Status here is not a plain active flag, so a flow reads the meaning rather than assuming it.
Create User Adds a user to the organization, with the invitation email deciding whether the person is told they now have an account.
Update User Changes a user's name, email, department, line manager or custom attributes.
Disable User Deactivates a user, stopping their sign-in while keeping their records and their history in every workflow. The safe offboarding write.
Enable User Reactivates a user who was disabled.
Delete User Removes a user from the organization. Disable User keeps the record and the workflow history, which is what most offboarding actually wants.

Departments

List Departments Reads departments, either as a whole tree or as one department's children.
Create Department Adds a department, at the top of the organization or under a parent.
Update Department Renames a department, moves it under another, or changes its manager.
Delete Department Deletes a department. The people in it stay, without one.

Locations

List Locations Reads the organization's locations.
Get Location Returns one location.
Create Location Adds a location to the organization.
Update Location Changes a location's name, code, address, phone or manager.
Delete Location Deletes a location.

Groups

List Groups Reads the organization's groups.
Create Group Adds a group, which is how a workflow addresses a set of people rather than one person.
Update Group Renames a group or changes its description.
Delete Group Deletes a group. Any workflow step addressed to it stops having anyone to address, so this is worth checking before it runs.
List Group Users Reads the people in a group.
Add Users To Group Adds people to a group.
Remove Users From Group Takes people out of a group.

Positions

List Positions Reads the organization's positions, which are job roles a workflow can address.
Create Position Adds a position, optionally with the people who hold it.
Update Position Renames a position.
Delete Position Deletes a position.
List Position Users Reads the people holding a position.
Add Users To Position Gives people a position, scoped globally or to a particular department or location. That scoping is what lets a process route to a role within an office rather than to a named individual.
Remove Users From Position Takes a position away from people.

Workflows

Start Workflow Starts a workflow and submits its form, optionally on behalf of another person, which is what an integration filing requests for people needs.
List Pending Tasks Reads the workflow tasks waiting to be acted on, narrowed to one person's queue for reminder and escalation flows.
Get Task Variables Returns a task's variables and their current values, which is what a flow reads before deciding how to present it.
Process Task Acts on a workflow task. Its outcome can complete a step, approve, reject, or save the variables without moving the task at all. The approve and reject outcomes are the ones this page's human gate exists for.
Get Form Variables Returns a workflow form's variables. Run it before starting a workflow, because the ids it returns are the keys that call wants.
Update Form Variables Sets values on a workflow form's variables.

Delegations

List Delegations Reads the rules that pass somebody's workflow tasks to a colleague, for example while they are away.
Get Delegation Returns one delegation rule.
Create Delegation Creates a rule that passes somebody's tasks to a colleague, either across all workflows or across named ones. It changes who is authorized to act, so it belongs behind a person's confirmation.
Update Delegation Changes a delegation rule.
Enable Delegation Switches a delegation rule on.
Disable Delegation Switches a delegation rule off without deleting it.
Delete Delegation Deletes a delegation rule. Disabling keeps it for the next time somebody is away.

Service Portal

Search Portal Users Reads the external users of a service portal, who are separate from the organization's own users.
Create Portal User Creates an external portal account. Leaving the password empty and sending an invitation lets the person set their own credential, which is the right default.
Set Portal User Password Sets a portal user's password on their behalf, bypassing the reset they would normally go through. It belongs only where the credential is generated and delivered securely.
Delete Portal User Removes an external user from a service portal.
List Portal Groups Reads a service portal's groups.
Create Portal Group Adds a group to a service portal.
Update Portal Group Renames a service portal group or changes its description.
Delete Portal Group Deletes a service portal group.
Count Portal Group Users Returns how many people are in a portal group without listing them, which is the cheap check before a bulk change.
Add Users To Portal Group Adds portal users to a portal group.
Remove Users From Portal Group Takes portal users out of a portal group.

Application Agents

List Application Agents Reads the packaged actions defined on an application, which Yeeflow calls agents and a flow runs by id.
Get Agent Returns an application agent's definition, including the variables it expects.
Run Agent Runs an application agent with a set of variables, which is how a flow reuses logic the application already owns rather than reimplementing it.

Files

Upload File Uploads a file and returns a file object. The upload is temporary, so a following create, workflow start or agent run has to claim it.
Download File Downloads a Yeeflow file into FlowRunner file storage and returns its URL.

Webhooks

Get Webhook Returns one webhook subscription.
Create Webhook Registers a webhook for delivery to a system other than FlowRunner. For a flow, the trigger below manages its own.
Delete Webhook Removes a webhook subscription and stops its deliveries.

Triggers

1 triggers

Event Triggers

On Task Event Fires when a Yeeflow workflow task is created, updated or deleted. It is what lets a flow react the moment a request reaches somebody's queue rather than on the next scheduled sweep. The task appears, the flow gathers the context around it, and the person who has to decide gets the decision put in front of them while it still matters.

Frequently Asked Questions

What can FlowRunner do with Yeeflow?

FlowRunner agents can run Get List, Get List Fields, and Query List Items in Yeeflow, plus 73 more actions.

Does connecting Yeeflow to FlowRunner require OAuth?

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

Can Yeeflow trigger a FlowRunner workflow automatically?

Yes. Yeeflow supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Yeeflow

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us