Skip to main content

Call automation action

Start another automation from inside an automation. Call it once for the current record, or once for every collected record, and reuse the same steps.

Written by Leo

Call automation is an action that starts another automation (the automation that calls is the caller, and the automation that starts is the callee). It's meant to help you build a set of steps once and reuse it from many automations, instead of copying the same actions again and again.

You can use this action for many things, including:

  • Starting a shared Create onboarding tasks automation whenever a candidate moves to Hired.

  • Sending a follow-up to every seller lead from a weekly view, one run per lead.

Adding the Call automation action in a new Leads automation: Add action, searching Call, selecting Call automation, then opening the automation dropdown and choosing Remind the lead owner under Callable automations

There are two versions:

  • Call automation triggers another automation on the current record.

  • Call automation on collected triggers another automation on every record of a collection, one run per record.

Note:

  • The callee must start with When another automation calls. Only automations with this trigger show up in Select an automation.

  • The callee's database app depends on the version. For Call automation, the callee lives in the same database as the caller. For Call automation on collected, it lives in the database of the collected records, which can be a different database.

  • Each call is its own run. It uses actions of its own, and the callee's trigger filter is applied: a record that doesn't match produces no run.

Who can use the Call automation action?

  • Automations are available on all plans: Free, Plus, and Premium. The number of automation actions per month depends on your plan. See the limits for your plan on our pricing page.

  • To add or change this action, you need to be a workspace admin of the workspace the database app is in. You also need full access to every database the automation uses.

Add the Call automation action

Build the callee first, because the caller needs to select it. To create the callee:

  1. Open the database app and click the automations icon in the top bar (tooltip Create and view automations), then select New automation. The icon is only there for workspace admins, and not on mobile.

  2. Choose the trigger When another automation calls. In an existing automation, hover over the trigger, click •••, and select Turn into → Automation calls.

  3. Add the actions the callee should run. Select Create automation.

The When another automation calls trigger in the automation editor.

Then, in the caller:

  1. Open the automation and select Add action.

  2. Select Call automation to call it on the current record, or Call automation on collected to call it on every collected record.

  3. Select Select an automation, or the automation that Tape preselected, and choose the callee under Callable automations. If you see No callable automation found, select Create automation.

  4. For Call automation on collected, also check the collection. Tape preselects the nearest collection above this action. Without one, it reads Select collected records.

  5. Select Save changes.

Call automation settings

Call automation reads as Trigger another automation on the current record by calling Select an automation:

  • Select an automation: the automation to start. It lists the automations in the database app that start with When another automation calls. Until you choose one, the automation shows as Broken.

The action Trigger another automation on the current record by calling Select an automation in the automation editor

Call automation on collected reads as Trigger another automation on collected records in Select collected records by calling Select an automation:

  • Select collected records: the collection to go through. It lists collections that earlier actions made, for example Search for records, Get view, or Get related. It shows No results until you add one.

  • Select an automation: the automation to start once per record. It lists the automations in the database app of the collected records.

A new automation for Tasks with Search for records in Tasks, followed by the action Trigger another automation on collected records in Tasks by calling Select an automation, and the status Broken

Both actions have the usual action menu: Settings, Continue on error, Deactivate, Turn into, Duplicate, and Remove. Learn more about action settings →

Pass values to the callee

The callee can declare input variables of its own. In the callee, hover over the trigger, click •••, and turn on Pass variable values to add inputs. In the caller, select Add variable under the action, choose an input of the callee, then choose Set value to enter text or values, or Calculation to compute the value.

In the callee's trigger menu, you can also turn on Pass field values and select the caller's database app. The callee can then use the caller's record values under Calling / <record name>.

Inside the callee, the inputs are available as variables, like any other variable. Learn more about record values and variables →

The When another automation calls trigger

The callee starts with When another automation calls in a database app. It runs on the record it was called with.

  • You can select a paused automation, but it doesn't run when it's called. Keep the callee Active.

  • The callee has a trigger filter like any other trigger. If the record doesn't match, no run starts.

  • The callee can be called from more than one caller.

Let's look at an example

Let's say your recruiting team creates the same onboarding tasks for every new hire, from two different automations. Here's how to build the steps once:

  1. Create the callee Create onboarding tasks with the trigger When another automation calls.

  2. Add Create record actions that create the tasks in a Tasks database app. Select Create automation.

  3. In the caller, set the trigger to When a record is updated and add the filter Stage Has changed to Hired.

  4. Select Add action → Call automation and choose Create onboarding tasks.

  5. Select Create automation, or Save changes if the caller already exists.

The next time a candidate moves to Hired, the tasks are created. Change the tasks in one place, and every caller uses the update.

Call an automation for many records

Use Call automation on collected when there's no current record, for example when the caller runs on a schedule. Here's how:

  1. Create the callee Send follow-up with the trigger When another automation calls.

  2. In the caller, use the trigger On a scheduled time or interval and set it to every Monday.

  3. Select Add action → Get view and choose a view such as Leads without follow-up.

  4. Select Add action → Call automation on collected, check that Tape preselected the collection from Get view, and choose Send follow-up.

  5. Select Create automation, or Save changes if the caller already exists.

Each lead in the view gets its own run of Send follow-up.

To call an automation for records in a related database app, first collect them with Get related, then use Call automation on collected. Learn more about collected records →

Call automation errors

  • No callable automation found means the database app has no automation that starts with When another automation calls. Select Create automation.

  • A call that doesn't produce a run usually means the callee's trigger filter didn't match the record.

  • A single collect action returns at most 1,000 records, so a call on collected runs for at most 1,000 records. For more records, split the work into batches. Learn more → Learn more about limits and throttling →

  • If two automations call each other, they can run in a circle. Learn more about automations that run in a loop →

  • The caller needs the current record, so Call automation isn't offered for triggers without a record, such as On a scheduled time or interval. Use Call automation on collected there.

  • The caller doesn't wait for the callee. It continues right away, and the callee runs as its own run. If the callee fails, the caller's run isn't affected. Check the callee's runs to see its errors.

Test, pause, or edit Call automation

  • Use Manual run on the caller to run it once. The callee runs for real, so test with a record that is safe to change.

  • A simulated run on the caller doesn't change data. It starts the callee as a simulated run too.

  • To change what the call does, edit the callee. The caller doesn't need to change.

  • New automations you create in the editor are Active right away. To stop calls, pause the caller (select Active below its name, then select Save changes), or remove the Call automation action.

Learn more

FAQs

Can I call an automation in another database app?

Not directly with Call automation, because the callee lives in the same database as the caller. To work on records in another database, collect them first, then use Call automation on collected. The callee has to be in the database of the collected records.

Why is my automation not in the list?

Only automations that start with When another automation calls appear under Callable automations. Open the automation, hover over the trigger, click •••, and select Turn into → Automation calls.

Can I call an automation that is paused?

You can select a paused automation, but it doesn't run when it's called. Keep the callee Active.

Does each call use actions from my limit?

Yes. Each call starts its own run, and the actions of that run count like any other run. A run can use up to 1,000 actions. Learn more about automation usage →

Can I call the same automation for a list of values instead of records?

Not at this time. Call automation on collected goes through collected records. For a list of values in a field, use Loop actions and call the automation inside the loop. Inside the loop, Call automation still runs on the current record. Pass the loop value with Add variable.

Are you a developer using the Tape API for automations?

The automation API has its own documentation for developers. Full reference: current_record_call_automation in the developer docs →

Still have questions? Find answers and get help from community experts in the Tape community →

Did this answer your question?