Installing a template

Install a template from the marketplace or the app: the install checklist, connecting a bank or destination without leaving it, installing the same template twice, automations that arrive switched off, and agents installing through the API, MCP or CLI.

3 min read

On this page

Installing a template makes real dashboards, automations, feeds, tables or widgets in your workspace, from your own banks and destinations. Nothing in a template carries anyone else's data.

Install from the marketplace#

Install a template

  1. Get template

    On the listing page choose Get template. From the website you sign in (or sign up) and pick the workspace to install into; in the app you are already there.

  2. Work through the checklist

    Each requirement — a bank, a feed, a table, a Google Sheets or Excel file, a database — shows as met, needing a choice, or missing. Pick what to use for each. Your progress is kept if you reload or step away.

  3. Connect what is missing

    Connect a bank or a destination from inside the checklist; you come back to the same step with it selected. For Google Sheets, Excel, a SQL database or a BankSync table, the install can create the sheet or table for you with the template's columns.

  4. Install

    BankSync checks every choice before it writes anything, then makes each resource and shows a summary of what it made.

The same template can be installed more than once, for example once per client. Each install has its own name and its own resources.

What to expect#

  • Automations arrive switched off. Turning one on asks you to approve its connections. If your plan does not include automations, you are offered the upgrade then; installing itself works on any plan.
  • Columns a destination cannot hold are adapted (for example a date stored as text) or left out, and the summary lists each one.
  • If one resource fails — a destination answers with an error, say — the others stay. The summary shows Retry for the failed one, and retrying never makes a second copy of what already worked.
  • Steps your plan does not include are left out, not failed. A template can use a step that needs a higher plan, such as AI categorising. On a plan without it, the checklist says “Included on plan: what it adds” with a link to the plans, and everything else installs. The install still finishes as Installed.
  • Provenance. Everything an install made shows “From template by creator” in the workspace tree and on its page.

Templates and your plan#

A template's page says what it needs a higher plan for. For example: “Works on every plan; AI categorising on Professional”. You can install it on any plan.

  • On a plan without the step: the checklist lists each step it leaves out and what it adds. Nothing is refused because of it. The summary shows the step as left out, with the plan that includes it.
  • After you upgrade: open the install from the summary or Settings › Workspace › Installed templates and choose Add what your plan now includes. BankSync makes only the steps that were left out. It never makes a second copy of what is already there.
  • Room on your plan still counts. A template that needs more tables or feeds than your plan has left is not installed until you upgrade or free some up. The checklist says how many it needs.

For a Notion, Sheets, Excel or Airtable template — or one for another product the creator names, such as Coda or Smartsheet — sold on another site, enter your email and BankSync sends you the creator's link. The form and the email name the product the template opens in. No account is needed, and nothing is installed in a workspace.

A template for another product is only offered once BankSync staff have reviewed it, and its page says where the link opens ("Opens on site").

Agents and code#

Developers and agents can plan and install a template, a saved template from your library, or a template passed inline, with a key that has marketplace:write:

  • API: POST /v1/installs/plan, then POST /v1/installs; read one with GET /v1/installs/{installId}.
  • MCP: installs_plan, installs_create, installs_get.
  • CLI: banksync installs plan, banksync installs create.

The plan answers planGated (steps your plan leaves out) and planRequirements. After an upgrade, installs_get and GET /v1/installs/{installId} list planIncludedNow; add them with installs_update or PATCH /v1/installs/{installId} and action: "addPlanIncluded".

Installs are limited to 50 an hour per workspace.

Use this page with your AI assistant

Every BankSync doc is available as plain Markdown for agents and LLMs.