Make Credential Requests

Creating and authorizing a connection in the Make scenario editor remains the standard manual workflow. For agents, Credential Requests are the recommended secure handoff, including for Make Endpoints and custom-app testing: the owner completes a Make authorization link, and the agent resumes with managed connection or key identifiers instead of handling provider secrets. No scenario is required just to request credentials.

Keep authorization separate from Endpoint execution, custom-app authoring, and business operations. This skill covers MCP and SDK/REST agents; preserve the selected authorized interface:

• Plugin/V2 MCP (/claude, /cursor, /openai, /copilot, /v2): discover the live tools, then use connection_create → authorization link → connection_get for supported current-user selections. Within scenario building, keep the make-scenario-building connection workflow; no SDK is required.
• SDK-generated standard MCP: when exposed, credential-requests_create calls SDK createAction(), not the legacy SDK create(). credential-requests_get reads request detail. Use the exact names and schemas returned by the active server; this is a different tool surface from Plugin/V2 MCP.
• SDK/REST: use an existing authorized host/client and load request flows. These workflows do not require a scenario MCP connection; the skill installs no package or access.