matchmaking_application_editor.replace_from_config_fileSave the exact host-provided JSON file reviewed by validate_config_file into this Portal's draft. Read the findings and stored-answer impact first; supply its private validation_token and the same file bytes. Changed bytes or state require a new review. This does not publish or notify; those need separate review and consent. Retry identical input with the same client_request_id. If file input is unavailable, use prepare_config_replacement or the existing application editor. This toolset requires a specific grant and is not assigned by default; request access through Support. Saved drafts and published question changes can mark earlier matching results as out of date. These tools do not rerun matching, contact recipients or create Deals.
- 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 |
|---|---|
allow_destructive_changesLegacy compatibility field. Draft saves do not delete stored answers; publishing requires its own destructive opt-in and approval. | No |
client_request_idUnique request identity. Retry an uncertain result with identical arguments and the same key. | Yes |
fileSee the input schema for constraints. | Yes |
provider_slugProvider workspace returned by providers.list. | Yes |
user_confirmedSee the input schema for constraints. | No |
validation_tokenSee the input schema for constraints. | Yes |
workspace_slugMatching workspace from projects.list or projects.get; use workspace_slug, not the Project id. | 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 criteria editor guide.
