PinkWallet Website Logo
Agentic AI Payment New
Bank
Convert
Invest
Crypto
Help
About Us
API
Join early access
Automation · n8nAgent keyAbout 3 minVerified 2026-10-01

Connect n8n to Pink Agentic AI Payments

Add an MCP Client node pointed at Pink with a Bearer credential; the AI Agent node gets the tools. Works with n8n workflows with an AI Agent node. Plans: n8n Cloud or self-hosted.

Create a free sandbox workspaceAll 15 clients

What you get

n8n asks Pink before it pays

Once connected, n8n can see its budget, the payees it may pay and the rules that apply, run a dry run, request a payment and file the receipt. The rules you set in Pink decide each request: allowed on the spot, sent to a person on the phone, or blocked. n8n never holds a card number or a bank login.

Step by step

  1. 1

    Create a free sandbox workspace

    Open agentic-sandbox.pinkwallet.com, type a company name, pick a template (coffee shop, startup or e-commerce) and click Create workspace. You get an admin key for the console and one key per AI agent. Keep the admin key: the sign-in page asks for it.
    After creating a workspace: the admin key and one key per agent are shown once
    After creating a workspace: the admin key and one key per agent are shown once
  2. 2

    Copy an agent key

    From the workspace page or the console.
    The console's Keys & connect tab with the OAuth URL and the agent keys
    The console's Keys & connect tab with the OAuth URL and the agent keys
  3. 3

    Add an MCP Client tool node

    In your workflow, add the MCP Client tool to the AI Agent node. Set the endpoint to https://agentic-sandbox.pinkwallet.com/mcp, the server transport to HTTP Streamable, and authentication to Bearer Auth with a credential holding the agent key.
  4. 4

    Run the workflow

    Give the agent the purchase as input. The execution log shows each Pink tool call.
  5. 5

    Watch the approval land in the console

    Open the sandbox console (link on the workspace page). Requests that cleared, asked a person or were blocked are all listed with the rule that decided them. Approve the pending one and the agent continues.
    Approvals in the console: the rule that stopped the request, the agent's reason, the evidence
    Approvals in the console: the rule that stopped the request, the agent's reason, the evidence

Try it: say this to n8n

Say this

“Check my budget with Pink, then order 20 kg of espresso beans from Counter Culture Coffee for $420. After that, order $890 of weekly supplies from Sysco.”

What you will see

The first order is allowed on the spot and the agent receives a single-use test credential. The second stops at the store manager's rule ($500–$2,000): it shows up under Approvals in the console, and the agent waits for a person. Approve it there and the agent picks up the credential.

Why those two rules exist →

Pink's side, in three screens

The sandbox workspace page with the admin key and one key per agent
Keys are shown once when the workspace is created.
Pink's sign-in page: admin key, agent selector, Allow and Deny
Sign-in: choose which agent the app acts as.
The console's Approvals tab with a pending request
Requests that need a person wait here and on the phone.

FAQ

My node only shows an SSE endpoint field

Update n8n; older MCP Client tool nodes predate Streamable HTTP. The MCP Client (step) node has the transport selector in all recent versions.

Official documentation

Menu names and settings paths follow each vendor's documentation at the verified date. If a vendor moves a menu, the linked page is the source of truth; the Pink side does not change.

Other clients

ClaudeClaude CodeAnthropic Messages APIChatGPTOpenAI Responses APIOpenAI Agents SDKGemini CLICursorWindsurfVS Code · GitHub CopilotMicrosoft Copilot StudioLangChain · LangGraphCrewAIYour own agent

← All clients  ·  Pink Agentic AI Payments  ·  Request early access

Contact Email: [email protected]
FacebookTelegramX (Twitter)DiscordYouTube
PinkWallet © 2026
About Us
Products
Services
Legal & Risk Disclosures
VASP:

ALTIVOX SPHERE SPÓŁKA ZO.O. is a wholly owned subsidiary of PinkWallet, registered in Poland in the Polish Ministry of Finance's virtual-currency activity register (registration number: RDWW-1797), authorized to provide cryptocurrency exchange and digital asset custody services in the EU under AML/CTF regulations.

MSB (US):

PinkWallet (Pink Technologies Inc) is registered as a Money Services Business with the U.S. Department of the Treasury, FinCEN (Registration No. 31000321450011), enabling it to provide users with cross-border fund settlement and international payment services under the U.S. regulatory framework.

MSB (Canada):

PinkWallet (Pink Wallet Technology Inc.) is registered as a Money Services Business with FINTRAC, Canada's financial intelligence unit (Registration No. C100001073), enabling it to provide users with cross-border fund settlement and virtual currency services under the Canadian regulatory framework.

Verify on the official registers