taskId. Use the
Tasks API to poll that task until it is no longer RUNNING.
Task triggers are reached through the me flow as a
WorkspaceUser, so authenticate with a workspaceToken. All requests go to:
This page is optimized for Filed MCP tools and AI agents. It spells out the
minimal mutation sequence for tax prep and data entry so agents do not need to
infer trigger arguments from product UI code.
Shared return type
BothtriggerTaxPrep and triggerDataEntry return TriggerTaskResult.
The background task ID. Poll it through Tasks or through the
client’s task list until the task reaches
COMPLETED or FAILED.Trigger tax prep
triggerTaxPrep starts a TAX_PREP task for a client. The task extracts forms,
reconciles data, and can optionally continue into data entry if the tax software
fields are provided.
Arguments
The client to run tax prep for.
The return form for the client:
F1040, F1041, F1065, F1120, F1120S,
or F990.Optional existing tax prep task ID. Pass this when reusing or re-running a
specific tax prep task. Omit it to start a fresh task.
The tax software provider key. Use this with
softwareConnectionId and
softwareClientId when the run should prepare for or continue into data entry.The Filed connection ID for the tax software integration.
The client identifier inside the tax software.
Optional software-specific client version string.
When
true, tax prep continues into data entry during the same run. Provide
software, softwareConnectionId, and softwareClientId when setting this.When
true, reconciliation runs again even if an earlier reconciliation result
exists.When
true, start a run even when an existing tax prep task is already running
for the client.Optional per-run skill selection. Omit it to apply all active skills. Pass
explicit workspace or user skill name lists to constrain the run.
Example: tax prep only
Example: tax prep with data entry
Trigger data entry
triggerDataEntry starts data entry from an existing tax prep task. Use this
when tax prep has already completed or prepared fields and the user now wants to
send those fields to tax software.
Arguments
The source tax prep task ID. In the web app, this is the latest
TAX_PREP task
for the client.The client whose prepared fields should be entered.
Optional tax software provider key.
The Filed connection ID for the target tax software integration.
The client identifier inside the tax software.
Example request
Example response
Find the latest tax prep task
If an agent needs to trigger data entry and does not already have a tax prep task ID, read the latest clientTAX_PREP task first.
The client whose latest tax prep task should be used as the data entry source.
Use this value as
TriggerDataEntryInput.taskId.The task state:
RUNNING, COMPLETED, or FAILED. Prefer a completed tax prep
task before triggering data entry.Poll trigger results
Poll the task returned by either mutation through the client’s task list. UseTAX_PREP for tax prep runs. Data entry is represented as stages within the tax
prep pipeline and by the task returned from triggerDataEntry.
Use
RUNNING to keep polling, COMPLETED to read results, and FAILED to show
or report errorMessage.Machine-readable data entry failure code when a data entry stage fails. Values
include
INVALID_CREDENTIALS, CLIENT_NOT_FOUND, TIMEOUT, and UNKNOWN.MCP usage pattern
For Filed MCP tools and AI agents:- Query the client and confirm
returnType. - Query workspace connections and select the tax software connection.
- For tax prep only, call
triggerTaxPrepwithrunDataEntry: false. - For tax prep plus data entry, call
triggerTaxPrepwithrunDataEntry: trueand include the software connection fields. - For data entry after tax prep, query the latest
TAX_PREPtask and calltriggerDataEntry. - Poll the returned
taskIdand surfaceerrorMessageorsubTasks.errorCodeif the task fails.