Configure Plaid bank-feed settings
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Follow this guide to set the environment and connection values used by the optional Plaid integration before connecting bank accounts.
What you’ll accomplish
Set the environment and connection values used by the optional Plaid integration before connecting bank accounts. It forms part of Pixie CRM Enterprise CRM's Accounting & Bookkeeping module and uses the module's permission-aware controller, status and mapping flow rather than a generic spreadsheet process.
How it works
The module includes actions to create a Plaid token, update the environment, connect bank accounts, update selected accounts and fetch new transactions. A verification controller is also included.
Plaid availability and data freshness depend on the external institution and configured environment. Pixie CRM does not manufacture missing bank data.
If a connection fails, record the time and non-sensitive error state, then review credentials, redirect configuration and institution status.
Follow these steps
- Obtain approved Plaid credentials.
- Go to Plaid Environment settings.
- Select the correct environment.
- Enter credentials through the protected settings form.
- Save and use the Connect action from Bank Accounts.
- Complete the institution flow and select accounts.
- Verify new transactions in Banking Feeds.
Settings to check
Check it worked
After the action is saved, Pixie CRM keeps the Accounting record connected to its source and updates the visible status or ledger data supported by this workflow. Review the saved result rather than relying only on a success message. Where the action posts accounting data, total debits and credits must balance and the accounts must match the approved mapping or manual selection.
- Open the saved record and confirm its final status.
- Review the source reference and every debit and credit line where ledger data was created.
- Use the relevant register, ageing, reconciliation or report to verify the wider effect.
Common mistakes to avoid
- Never paste production secrets into support messages.
- Test in a non-production environment where possible.
- Do not reconnect repeatedly when a token is valid.
- Review regional and institution availability.
- Use the least destructive correction available and record the reason for material changes.
- Do not bypass a permission, approval or closed-period control by changing unrelated data.