In Skippet, you can automate repetitive tasks and workflows on your data.

Automations let you make Skippet do actions automatically on your behalf whenever specific conditions, which you define through triggers, are met. Skippet automations can range from simple to advanced.

For example:

notifying your team when a new deal is added to the Deals table
notifying a client when a task is completed in the Client tasks table
creating new tasks on a predefined schedule
pulling events from your Google calendar into a Skippet table using Zapier
connecting a form on your website to a Skippet table using Zapier

Directions: you can set the automations in a view from the Automations section in the settings bar.

Automations basics

An automation consists of a trigger and one or more actions:

the trigger is the “when”—the cause that starts an automation
an action is the “then”—the effect that happens when an automation runs

For example:

when the Process status of an issue in the Project issues table is set to Done (trigger), then set the Issue status to Archived (action)
when the status of an existing task in the Client tasks table is set to Done (trigger), then send a notification to the related client (action)

To set up an automation you need to first select and set up a trigger, and then select and set up one or more actions connected to it.

Once you set up the automation, you can turn it on by toggling the switch to ON from the automation details settings, and then publish the changes to your view.

Recommendation: while you can create automations in any view, the best practice is to create them in the view where the trigger database lives.

Setting up triggers

In Skippet, most triggers are fired when something happens to database items. So, when you set up a trigger, you first need to pick a trigger database, and then you may specify additional conditions that the trigger has to meet before it starts the automation.

For example, when setting a When item updated trigger, you can specify that only the updated items having their Process status field updated to a certain value can trigger the automation.

Setting up actions

Action settings vary from action type to action type.

For example, when setting an Update an existing item action, you can select the item to update as the item that triggers the automation in the first place.

Trigger list

Here is a list of all the triggers available in Skippet. You will soon be able to read about each trigger in a dedicated article. Until then, please reach us via the Help messenger if you have any questions.

Trigger	Definition	Example
When item created	Triggers when a new item is created in a database.	When a new task is created then…
When item updated	Triggers when an existing item in a database is updated.	When the status of a task changes to Done then…
When item deleted	Triggers when an existing item is deleted.	When a task is deleted then…
On a fixed schedule	Triggers at a specific date. This date can just be fixed.	When the start of the month arrives then…
On a schedule for each item	Triggers at a certain date for each item. This date could be fixed or different for each item.	When the deadline of a task arrives then…
When Zapier automation runs	Triggers when a Zapier automation is run.	When a new task is received from your calendar via Zapier then…

Action list

Here is a list of all the actions available in Skippet. You will soon be able to read about each action in a dedicated article. Until then, please reach us via the Help messenger if you have any questions.

Action	Definition	Example
Create a new item	Creates a new item in a target database.	…then create a new task in the tasks table with a deadline of two days from now.
Update an existing item	Updates a specific existing item in a target database.	…then update the status of a specific task to Done.
Update multiple existing items	Update multiple existing items in a target database.	…then update the status of all the tasks related to a specific project to Done.
Duplicate multiple existing items	Duplicate multiple existing items in a target database.	…then duplicate all the template tasks and relate them to the triggering project.
Delete an existing item	Delete a specific existing item in a target database.	…then delete a specific task.
Delete multiple existing items	Delete multiple existing items in a target database.	…then delete all the tasks that have been completed more than two months ago.
Notify users	Triggers at a specific date (and time) for each item. The date (and time) can be the same or different for each item.	…then send a message to a group of users.
Trigger a Zapier automation	Triggers when a Zapier automation is run	…then send the data of a newly created event to Zapier to push them to Google Calendar.

What’s next?

In Skippet, you can handle sensitive data by setting permissions on each view, limiting which users can access which data.

When-Zapier-automation-runs trigger

Trigger-a-Zapier-automation action

When-item-created trigger

When-item-deleted trigger

Delete-multiple-existing-items action