Docsend2pdf MCP integration for AI agents.
Connect AI agents to Docsend2pdf through 1 structured actions, including convert. Review authentication, inputs, workflows, and safety guidance.
- ACTION CONTRACTS
- 1
- AUTHENTICATION
- No account authorization
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Docsend2pdf integration exposes
The Docsend2pdf Agent App exposes 1 provider-backed actions for productivity and design & media work. Its current contract lets an authorized agent convert a docsend document url to pdf and return json-safe download metadata. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses No account authorization. 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 Docsend2pdf account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Docsend2pdf capabilities.
Showing 1 of 1 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
convertREVIEWConvert a DocSend document URL to PDF and return JSON-safe download metadata.
INPUTS: url / email / passcode / outputName / returnPdfBase64
INPUT CONTRACTS
Know what the action needs before it runs.
convert
urlREQUIRED- The DocSend document URL to convert.
emailOPTIONAL- The optional email address required by some protected DocSend links.
passcodeOPTIONAL- The optional passcode required by password-protected DocSend links.
outputNameOPTIONAL- The preferred PDF filename for the converted document.
returnPdfBase64OPTIONAL- Whether to return the PDF bytes as base64 when file transit is unavailable or not desired.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Convert
Convert a DocSend document URL to PDF and return JSON-safe download metadata. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
convertVerify with Convert
Convert a DocSend document URL to PDF and return JSON-safe download metadata. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
convertSAFETY BOUNDARY
Operate Docsend2pdf with explicit limits
- Authorize Docsend2pdf with No account authorization and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned Docsend2pdf data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Docsend2pdf rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Docsend2pdf task completed successfully.
CONNECTION MODEL
No account authorization
Docsend2pdf uses No account authorization. Connection requirements and availability are determined by the provider and the Working Machines deployment.
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
- 0
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 1
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 Docsend2pdf.