Templated MCP integration for AI agents.
Connect AI agents to Templated through 7 structured actions, including get account, create render, and delete render. Review authentication, inputs, workflow…
- 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 Templated integration exposes
The Templated Agent App exposes 7 provider-backed actions for design & media and marketing work. Its current contract lets an authorized agent get the current templated account associated with the api key, create a templated render from one template with optional shared layer overrides and image or pdf output settings, and delete a templated render by its render id. 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 Templated account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Templated capabilities.
Showing 7 of 7 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_accountREADGet the current Templated account associated with the API key.
create_renderWRITECreate a Templated render from one template with optional shared layer overrides and image or PDF output settings.
INPUTS: templateId / format / transparent / flatten / cmyk
delete_renderHIGH IMPACTDelete a Templated render by its render ID.
INPUTS: renderId
get_renderREADRetrieve a single Templated render by its render ID.
INPUTS: renderId
get_templateREADRetrieve a single Templated template by its template ID.
INPUTS: templateId / includeLayers / includePages
list_rendersREADList all renders owned by the current Templated account.
list_templatesREADList Templated templates with optional filters for name, dimensions, and tags.
INPUTS: query / page / limit / width / height
INPUT CONTRACTS
Know what the action needs before it runs.
create_render
templateIdREQUIRED- Template ID to render.
formatOPTIONAL- Output format for the render.
transparentOPTIONAL- Whether the background should be transparent for PNG renders.
flattenOPTIONAL- Whether PDF output should be flattened.
cmykOPTIONAL- Whether PDF output should use CMYK color mode.
delete_render
renderIdREQUIRED- The render ID.
get_render
renderIdREQUIRED- The render ID.
get_template
templateIdREQUIRED- The template ID.
includeLayersOPTIONAL- Whether to include template layers in the response.
includePagesOPTIONAL- Whether to include template pages in the response.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Account
Get the current Templated account associated with the API key. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_accountControl Create Render
Create a Templated render from one template with optional shared layer overrides and image or PDF output settings. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_renderVerify with Get Render
Retrieve a single Templated render by its render ID. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_renderSAFETY BOUNDARY
Operate Templated with explicit limits
- Authorize Templated with API key and grant only the provider access required by the selected actions.
- 2 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_render` 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 Templated rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Templated task completed successfully.
CONNECTION MODEL
API key
Templated API key used with the Authorization Bearer header. Find it in the API Key tab: https://app.templated.io/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
- 5
- WRITE SIGNALS
- 1
- HIGH IMPACT
- 1
- REVIEW SIGNALS
- 0
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 Templated.