When a record is created is a trigger that starts an automation once for every new record in a database app (the trigger decides when an automation starts, and the filter decides whether it continues). It's meant to help you react to new entries right away, without watching the database yourself.
You can use this trigger for many things, including:
Creating a follow-up task when a new seller lead is added to your CRM.
Emailing the hiring manager when a new application comes in.
Note:
It runs once per new record. Changes to an existing record don't start it. Use When a record is updated → for that.
How the record was created matters. Records created by hand or by the API start the trigger. Imports start it only if
Trigger automationsis on for the import, and other automations only ifTrigger automationsis on in the action's settings. Records submitted through a form start it too. A record that's still being created doesn't start it until it's created.A manual run doesn't create a record. It runs the automation on records that already exist.
Who can use the When a record is created trigger?
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 create, edit, pause, run, or delete automations, you need to be a
Workspace adminin the workspace the database app belongs to. Only workspace admins see the automations button in a database app.
Set up the When a record is created trigger
To set up the trigger:
Open the database app and click the automations icon at the top right (
Create and view automations).Select
New automation.Select
When a record is createdfrom the list of triggers.Add a filter if the automation should only continue for certain values. Learn more about filters below →
Select
Add actionand choose what should happen.Select
Create automation.
The trigger reads like a sentence: When a record is created in {app}. It has no settings of its own, so there's nothing to choose except the database app. By default, it's the one you opened the automation from.
To give the trigger your own name, select its name and type a new one.
Filter the When a record is created trigger
The filter decides whether the automation continues after it's been triggered. Under And if the following conditions are met, Tape already shows an empty row with the title field and Contains. Build your first condition in that row: Where {field} {option} {value}. Select Add filter to combine more conditions, or select Add filter group for rules with several parts. Learn more about filters →
Tip: Filter on the values you need at the moment of creation, such as the lead source or the amount. Values someone fills in later aren't set yet when the record is created.
Let's look at an example
Let's say you want a follow-up task for every new seller lead. Here's how:
Open your
Leadsapp and set the trigger toWhen a record is createdinLeads.Add the filter
WhereLead typeIsSeller.Select
Add action→Create record, and choose yourTasksapp.Enter "Call new lead: " and insert the
Namefield as the title of the task.Select
Create automation.
The next time someone adds a seller lead, you should see a new task in Tasks!
When a record is created errors
If the status next to the automation's name shows
Brokenin red, part of the automation doesn't fit the trigger, often an action that needs a current record. The part that doesn't fit is shown in red. While the automation isBroken, it doesn't run and you can't start a manual run. Tape then showsTrigger runs manually not possible because of broken automation.If a run fails, you can see each step and its message in the automation's runs. To see the runs of an automation, click the play button next to
Manual runat the top right of the editor (View all runs), or usecmd/ctrl+1. TheRunspanel lists the runs of the last 30 days. Select a run to see each step and its message. To see the runs of all automations, selectRunsin the sidebar of the Automation Center.If an automation that creates records in the same database app starts itself again and again, see My automation runs in a loop →.
Lots of automation activity in a short time can delay automations across your organization. The delay is temporary. Tape checks the load again shortly and runs waiting automations automatically. Learn more about limits and throttling →
Test, pause, edit, or delete an automation with this trigger
Manual runruns the automation once on the records you choose. It has real effects, so the example creates real tasks. Learn more about testing →New automations you create in the editor are
Activeright away. To pause one, selectActivenext to the automation's name. It switches toPaused. Select it again to turn the automation back on.To edit an automation, open the database app, click the automations icon at the top right, then select the automation. Select
Save changeswhen you're done.To delete an automation, open it and click
•••at the top right, then selectDelete. Confirm withDelete. You can also click•••next to the automation in the list of automations, then selectDelete. Deleting can't be undone.To switch to another trigger, hover over the trigger and click
•••to the right of it, then selectTurn intoand choose a trigger. The filter and the actions stay. If an action or a filter condition doesn't fit the new trigger, for exampleUpdate recordafter switching to a schedule, orHas changedafter switching away fromWhen a record is updated, the status next to the automation's name turns red and showsBrokenuntil you change or remove it.
Learn more
FAQs
Does this trigger run when I create a record by hand?
Does this trigger run when I create a record by hand?
Yes! A new record in the database app starts it. Records created by the API start it, too. An import starts it only if Trigger automations is on for the import. Another automation starts it only if Trigger automations is on in its action's settings.
Does it run for records that already exist?
Does it run for records that already exist?
No. It only runs for new records. To run an automation on existing records, use Manual run. Learn more →
Why does my automation start another run?
Why does my automation start another run?
Records created by an automation only start other automations if Trigger automations is turned on in the action's settings. It's off by default. If you turned it on, turn it off again or create the record in another database app. Learn more about action settings →
What's the difference between this trigger and When a record is updated?
What's the difference between this trigger and When a record is updated?
When a record is created runs once for each new record. When a record is updated runs on changes to records that already exist.
Are there other triggers I can use?
Are there other triggers I can use?
Yes! An automation can start when a record is created, updated, or deleted, when a comment is added, when a date arrives, on a schedule, and more. See every trigger in Automation triggers →
Are you a developer using the Tape API for automations?
Are you a developer using the Tape API for automations?
The automation API has its own documentation for developers. Full reference: Triggers in the developer docs →
Still have more questions? Find answers and get help from community experts in the Tape community →.
