Qingflow MCP integration for AI agents.
Connect AI agents to Qingflow through 21 structured actions, including find members, add record comment, and process record. Review authentication, inputs, w…
- ACTION CONTRACTS
- 21
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Qingflow integration exposes
The Qingflow Agent App exposes 21 provider-backed actions for productivity and data work. Its current contract lets an authorized agent find qingflow workspace member ids by email address or mobile number, add a comment to one qingflow business-data record, and submit, approve, reject, complete, or copy a qingflow workflow node. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Qingflow account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Qingflow capabilities.
Showing 12 of 21 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
find_membersREADFind Qingflow workspace member IDs by email address or mobile number.
INPUTS: email / mobile
add_record_commentWRITEAdd a comment to one Qingflow business-data record.
INPUTS: appKey / applyId / userId / message / mentionUserIds
process_recordREVIEWSubmit, approve, reject, complete, or copy a Qingflow workflow node.
INPUTS: appKey / applyId / userId / auditNodeId / decision
create_recordWRITECreate one business-data record in a Qingflow application and return its asynchronous request ID.
INPUTS: appKey / userId / applyUser / answers
get_departmentREADGet one Qingflow department by department ID.
INPUTS: departmentId
get_formREADGet the current form fields, options, and field metadata for a Qingflow application.
INPUTS: appKey / userId
get_memberREADGet one Qingflow workspace member by external user ID.
INPUTS: userId
get_operation_resultREADGet Qingflow's processing result for a create, update, or other asynchronous request.
INPUTS: requestId
get_recordREADGet one Qingflow business-data record and its current field answers.
INPUTS: appKey / applyId
list_appsREADList Qingflow applications visible to the workspace or one specified member.
INPUTS: userId / favoritesOnly
list_departmentsREADList Qingflow departments, optionally rooted at one department.
INPUTS: departmentId
list_membersREADList members in the connected Qingflow workspace.
INPUTS: pageNumber / pageSize
INPUT CONTRACTS
Know what the action needs before it runs.
find_members
emailOPTIONAL- The member email address.
mobileOPTIONAL- The member mobile number.
add_record_comment
appKeyREQUIRED- The Qingflow application key shown in the application URL.
applyIdREQUIRED- The Qingflow application-data record ID.
userIdOPTIONAL- The Qingflow member external user ID.
messageREQUIRED- The comment message.
mentionUserIdsOPTIONAL- External member user IDs mentioned by the comment.
process_record
appKeyREQUIRED- The Qingflow application key shown in the application URL.
applyIdREQUIRED- The Qingflow application-data record ID.
userIdREQUIRED- The Qingflow member external user ID.
auditNodeIdREQUIRED- The workflow node ID being processed.
decisionREQUIRED- The workflow decision to apply.
create_record
appKeyREQUIRED- The Qingflow application key shown in the application URL.
userIdOPTIONAL- The Qingflow member external user ID.
applyUserOPTIONAL- The Qingflow member identity used to submit the record.
answersOPTIONAL- Field answers used to create the Qingflow record.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Find Members
Find Qingflow workspace member IDs by email address or mobile number. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
find_membersControl Add Record Comment
Add a comment to one Qingflow business-data record. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_record_commentVerify with Get Department
Get one Qingflow department by department ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_departmentSAFETY BOUNDARY
Operate Qingflow with explicit limits
- Authorize Qingflow with API key and grant only the provider access required by the selected actions.
- 3 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Qingflow rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Qingflow task completed successfully.
CONNECTION MODEL
API key
Qingflow OPEN API super-admin access token. Sign in at https://qingflow.com/passport/login, then open Qing Marketplace > Extensions > Third-party Connections > OPEN API > Configuration to copy the token.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 14
- WRITE SIGNALS
- 3
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 4
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Qingflow.