--- title: "Automation Templates" description: "BankSync’s ready-made automations, installed from the Automations tab, an Automate menu or the marketplace: what starts each, what it does, what it asks you to pick, and how to install one." section: "Automations" canonical: "https://banksync.io/docs/automations/automations-templates" specs: ["automations","marketplace"] operationBindings: [{"capability":"marketplace","operation":"marketplace.listings.search"},{"capability":"marketplace","operation":"marketplace.installs.plan"},{"capability":"marketplace","operation":"marketplace.installs.create"}] --- A template is an automation BankSync has already built: a trigger, the steps and a name. BankSync publishes each one as its own template on the marketplace, marked as by BankSync, beside the templates other creators publish. **Installing** one makes the automation in your workspace, **switched off**, with the bank, feed or table you choose already bound. One that adds rows also makes the table it adds them to, with a column for each value it records. Nothing runs until you switch it on and a member approves what it may do. ## Where they are - **The Automations tab**, under the list: **Start from a template**. - **The Automate menu** on a table's toolbar, a bank's page, a feed's header, the Clients list and the Support page, which lists the templates that start from something there, with that table, bank or feed filled in. - **The marketplace**, with every other template. - **Your agent, the API and the CLI**: `marketplace_search` to find one, then `installs_plan` and `installs_create` over MCP; `GET /v1/marketplace/listings`, `POST /v1/installs/plan` and `POST /v1/installs` on the API; `banksync marketplace search` and `banksync installs` in the CLI. See [Building with an agent, the CLI or the API](/docs/automations/automations-with-agents-and-code). ## Installing one 1. Choose a card. It shows what starts the automation and what it needs from your workspace. 2. The install checklist asks for what the template needs: the bank (and, for a template that reads one account, which of its accounts), the feed or the table, where it writes (a sheet, workbook, Notion database, Airtable table or database of a destination you connected, or connect one there), and — for a table template — the status option or date field it starts on. 3. **Install** makes the automation, switched off, and lists it with what else the install made. 4. Open it in the builder to pick anything left (such as which of your table's columns gets each value), test it, then switch it on and approve its grant, as for any automation. A template whose steps your workspace cannot run is not offered, never offered broken. ## The templates | Template | Starts when | What it does | | ----------------------------------------------------------------- | ------------------------------------------------------------------ | -------------------------------------------------------------------------------------------------------------------------- | | Tell me when a bank needs reconnecting | A bank needs signing in again | Tells the workspace, so a feed never quietly stops. | | Re-run a feed after reauth | A bank works again after someone signs in to it | Runs the feed you pick, if it reads that bank, and waits for it to finish. | | Log failed deliveries to a table | A feed could not deliver to its destination | Adds a Failed deliveries table, then one row per failed delivery: when, which feed and run, the destination and the error. | | Send a digest after each run | A feed finishes a run | Tells the workspace how many rows the run wrote, skipped and failed. | | Notify the workspace when support replies | BankSync support answers one of your cases | Puts a notice in every member's tray. | | Log closed cases to a table | One of your support cases is closed | Reads the case and adds one row to a Closed cases table it makes: when, the case number, its subject and kind. | | Escalate a case that misses its response time | One of your support cases passes its response time unanswered | Reads the case and tells the workspace's owners and admins which one it is. | | Log a weekly transaction count | Every Monday at 08:00 | Reads the last seven days of the account you pick and adds one row to a Weekly transaction counts table it makes. | | Email me when a balance runs low | The account you pick goes under the amount you set | Emails you the balance, once each time it drops under (and at once if it is already under when you switch it on). | | Notify when a row is added | A row is added to the table (offered from a table) | Posts a message on the new row's conversation, so the people watching it hear about it. | | Post to a thread when a status changes | A row's status becomes the option you pick (offered from a table) | Posts a message on the row's conversation. | | Copy a row when a payment lands | A row's status becomes the option you pick (offered from a table) | Adds a copy of the row (when, which row and its values) to a Paid rows table it makes. | | Copy a row to another table when it enters a view | A row enters the view you are looking at (offered from a table) | Adds a copy of the row (when, which row and its values) to a Copied rows table it makes. | | Email me about large transactions | A transaction of at least the amount you set arrives in an account | Emails you what it was, which way the money went and with whom. | | Email me when a payment lands | Money of at least the amount you set lands in an account | Emails you how much arrived and who paid it. | | Weekly money summary email | Every Monday at 08:00 | Reads the last seven days of the account you pick and emails you the money in, the money out and the three biggest spends. | | Send new transactions to Google Sheets, Notion, Excel or Airtable | Every day at 06:00 UTC | Bank to a destination with that one tool offered: the sheet, Notion database, workbook or Airtable table you pick. | | Bank to a destination | Every day at 06:00 UTC | Reads what changed in a bank's accounts, applies your enrichments and syncs the records to the destination you pick. | | Save emailed receipts to a table | Mail reaches a mailbox | Reads the documents attached to the mail and syncs one row per document or line item to the destination you pick. | The last two are the steps a feed is made of; see [Steps for banks, feeds, tables and mailboxes](/docs/automations/automations-banking-steps). A sync feed's page offers the same thing from the other direction as **Convert to an automation**. The marketplace's Automations tab lists the ones that stand on their own: sending new transactions to Google Sheets, Notion, Excel or Airtable, the large-transaction, payment and low-balance alerts, the weekly money summary, saving emailed receipts and the reconnect alert. Every template in the table stays in the app's gallery. The money alerts and the summary arrive by email, to the person who switches the automation on (the member who approves it); to email the owners and admins, or the owners, admins and editors, change **Who should get it?** in its **Send an email** step. They never email anyone outside the workspace. Each email says which automation sent it and links to it, where you switch it off.