Faktoora MCP integration for AI agents.
Connect AI agents to Faktoora through 7 structured actions, including get project, create project, delete project, and attach project document. Review authen…
- ACTION CONTRACTS
- 7
- 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 Faktoora integration exposes
The Faktoora Agent App exposes 7 provider-backed actions for finance and productivity work. Its current contract lets an authorized agent retrieve a faktoora project by uuid, create a faktoora project, and permanently delete a faktoora project without deleting its attached document. 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 Faktoora account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Faktoora capabilities.
Showing 7 of 7 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_projectREADRetrieve a Faktoora project by UUID.
INPUTS: projectId
create_projectWRITECreate a Faktoora project.
INPUTS: name / description / place / eta / estMinutes
delete_projectHIGH IMPACTPermanently delete a Faktoora project without deleting its attached document.
INPUTS: projectId
attach_project_documentREVIEWAttach one Faktoora document to an empty project.
INPUTS: projectId / documentId / documentType
detach_project_documentREVIEWDetach one Faktoora document from a project.
INPUTS: projectId / documentId / documentType
list_projectsREADList Faktoora projects with pagination, filtering, and sorting.
INPUTS: page / perPage / keyword / status / customerId
update_projectWRITEPartially update a Faktoora project.
INPUTS: projectId / name / description / place / eta
INPUT CONTRACTS
Know what the action needs before it runs.
get_project
projectIdREQUIRED- The Faktoora project UUID.
create_project
nameREQUIRED- The project name.
descriptionOPTIONALplaceOPTIONALetaOPTIONALestMinutesOPTIONAL
delete_project
projectIdREQUIRED- The Faktoora project UUID.
attach_project_document
projectIdREQUIRED- The Faktoora project UUID.
documentIdREQUIRED- The Faktoora document UUID.
documentTypeREQUIRED- The type of Faktoora document to attach or detach.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Project
Retrieve a Faktoora project by UUID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_projectControl Create Project
Create a Faktoora project. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_projectVerify with List Projects
List Faktoora projects with pagination, filtering, and sorting. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
list_projectsSAFETY BOUNDARY
Operate Faktoora with explicit limits
- Authorize Faktoora 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.
- Treat `delete_project` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Faktoora rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Faktoora task completed successfully.
CONNECTION MODEL
API key
Faktoora API key sent in the X-API-KEY header. See https://docs.faktoora.com/docs/glossary/#api-key.
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
- 2
- WRITE SIGNALS
- 2
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 2
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 Faktoora.