projects.import_matchmaking_answer_fileImport a host-provided original document into a file question in a Project matchmaking application. Requires a host-supplied file reference, a valid question block_key and current answers_revision. Limit: 25 MiB. Retrieves and attaches original bytes; does not submit or start Autofill. Identical retries use the same idempotency_key. An uncertain transfer needs authoritative file inventory verification before another upload. The application upload section remains available without host file input.
- Operation
- write
- OAuth scopes
- mcp
Availability depends on your assigned tools. Scopes do not grant record access. Read the tool description and current resource before changing it; follow the required revision and idempotency fields below.
Provider portal inputs
| Name and description | Required |
|---|---|
block_keyFile question block_key from the application's contract. | Yes |
expected_answers_revisionSee the input schema for constraints. | Yes |
fileSee the input schema for constraints. | Yes |
idempotency_keySee the input schema for constraints. | Yes |
item_idStable public identifier for the referenced resource. | No |
provider_slugCopy provider_slug from providers.list; named slugs are valid. | Yes |
workspace_slugMatching workspace: copy workspace_slug (mmw_) from projects.get or projects.list; not project_slug. | Yes |
View exact input schema
Result
Check the structured result for success or an error before continuing. Read the affected record to confirm your change.
View exact output schema
For this workflow’s steps and prerequisites, read the Matchmaking guide.
