Hushh

Execute the Full Plaid Workflow

Use this console to test both Production and Sandbox Plaid workflows, then sync data to Supabase through your API layer.

Active Environment

Credentials: Missing

Prod: missing | Sandbox: missing

Profile Creation Agent Profile Update Agent

Step 0 - Connect a Bank Account

Launch Plaid Link to connect a bank account. On success we capture the public token and automatically exchange it for an access token.

Products requested in Link

AuthIdentitySignal

These should match the MuleSoft flow. Missing products can cause 400 errors downstream.

Functional Workflow

Step 1 — User Initiation

Hushh or a partner app calls the MuleSoft CloudHub REST interface to request Plaid data.

Step 2 — Token Generation

Public, access, and link tokens are created so the user can connect accounts securely.

Step 3 — Data Retrieval

With the access token, the API fetches accounts, transactions, and asset data from Plaid.

Step 4 — Data Synchronization

Responses are transformed into a unified schema and persisted inside Supabase.

Step 5 — Confirmation Response

The MuleSoft API returns a structured JSON payload confirming the sync.

Step 1 — Enter Runtime Inputs

User ID (for Supabase)

Public Token

Access Token

Link Token

Step 2 — Run the Workflow

2.1 Exchange the public token for a secure access token

2.2 Create the link token for Plaid Link onboarding

2.3 Fetch account details via Plaid /accounts/get

2.4 Optional: fetch consolidated financial data via MuleSoft

2.5 Push the unified payload to Supabase for storage

Follow the buttons in order (1 to 5). Step 2.4 is optional if you want richer identity/transactions/liabilities fields before pushing to Supabase. You can repeat steps with fresh tokens at any time.

Execute the Full Plaid Workflow

Step 0 - Connect a Bank Account

Functional Workflow

Step 1 — Enter Runtime Inputs

Step 2 — Run the Workflow

Step 3 — Response Console

Products

Solutions

Developers

Company

Community

Support