What will start your automation…
Refer to Airtable – create a connection.
Triggers List and Settings Copy Link
Recurrence rule / scheduler settings Copy Link
Run Once Tab: This tab allows you to schedule a Flow to execute a single time at a specific date and time. This is ideal for one-time operations such as data syncs, cleanups, or initial configuration steps. After execution, the schedule will be automatically cleared unless rescheduled manually.
Run Tab: This tab is used to set up repeating schedules:
- Repeat feature: This dropdown determines how long the automation will continue repeating based on the selected frequency (Minutely or Hourly). You can choose from:
- Repeat Forever
- The automation will continue to run indefinitely at the defined interval (e.g. every 15 minutes).
- No end condition is specified.
- Repeat for (x) Times
- You set a specific number of repetitions.
- Requires the field Number (x) of Repeat Times to be filled (e.g. 10 times).
- Repeat Between Start & End Dates
- The automation will run only within a defined date range.
- Additional fields will appear to select start and end dates.
- Useful for limited-time schedules like campaigns or batch jobs.
- Repeat Forever
- Daily at Multiple Times: Sets the Flow to run several times per day based on a minutely or hourly interval.
- Daily: This allows a Flow to run x times per day at a specific time.
- Weekly: This allows you to run a Flow weekly by selecting the days and time.
- Monthly: This will monitor your Trigger every month on a defined date and hour.
- Yearly: This will monitor your Trigger on a specific date and hour every year.
- Specific dates: This will start your Trigger on specific dates and time.
For more details, see Wiresk Scheduler – The Fundamentals.
Get sample with the”Use” button Copy Link
After you’ve configured your Trigger parameters, select the “Use” button to fetch a live sample of data from the Trigger.
What it does:
- Extracts real data based on your Trigger setup
- Validates your parameters by showing if they match existing records
- Prepares data for field mapping – the sample helps you map your Trigger output to your Method parameters in the Flow. Refer to FIELD MAPPING documentation.
Think of it as a preview step: it makes sure your Trigger is working and gives you real data to work with when setting up the rest of your flow.
Scheduled Triggers: Copy Link
These Triggers will start your Flow automatically at a specific time or intervals instead of being triggered real-time event (Webhooks).
List Bases Copy Link
● If there are more than 1000 bases, the response will include an offset (like a marker to the next page).
● To get the next batch of bases, you need to send another request and include that offset in the parameter.
For more detail, see Airtable API reference List Bases
Configuration Table:
| Name* | List Bases |
| Connection* | Select your connection or create one. |
| Timeout | You can additionally set the Trigger duration to limit the information processed per execution to optimize performance and resource usage. |
| Recurrence Rule/scheduler* | Set up your recurrence rule. |
PARAMETERS
This tab enables you to configure the Trigger.
Retrieve record by*:
Select the type of records to retrieve:
- All Records
- New Records
- Updated Records
This tab allows you to preview the data that will be retrieved and included in the output.
In specific Trigger instances, data can only be previewed when it is available for retrieval. If no event occurs from the Trigger, a message “No data available” will be displayed.
Use this button to preview the data based on the “Configure Parameter” tab.
(*) required field
Response example
{
"id": "usrtJtpUUBJucxCKl",
"name": "Wiresk Table 01",
"permissionLevel": "create"
}⚠️ Reminder: Click “Use” to validate your Trigger with sample data before saving.
Retrieve records using Wiresk’s Query Builder Copy Link
⚠️ Please note that preview is not available for this Method due to Notion’s unsupported Metadata format. However, while preview is unavailable, the data can still be mapped without any issues. You may continue building Flows and applying field mappings as needed—the functionality remains fully operational aside from the preview limitation.
Configuration Table:
| Name* | Retrieve records using Wiresk’s Query Builder |
| Connection* | Select your connection or create one. |
| Timeout | You can additionally set the Trigger duration to limit the information processed per execution to optimize performance and resource usage. |
| Recurrence Rule/scheduler* | Set up your recurrence rule. |
PARAMETERS
Retrieve by*:
- All Records
- New Records
Dataset*:
Select your Airtable base.
Entity*:
Select the base table from which data will be retrieved.
This tab enables you to define specific criteria to narrow down the records being retrieved.
Select the button to configure filters.
Configure which columns or fields of data will be retrieved and included in the output.
To visualize the records. You must select at least 1 Columns to get the Preview Data.
If you get this message:” Cannot convert undefined or null to object”, it means there is no records.
Customize which columns are displayed and retrieved. Minimum 1 column, maximum 50 columns.
This option is for sorting the data in the columns by Ascending or descending order.
Number of records:10
By default, 10 records will be shown.
Begin at record: 0
The display starts at record 0.
(*) required field
⚠️ Reminder: Click “Use” to validate your Trigger with sample data before saving.
List Comments Copy Link
if you’re replying to a comment, the original comment might not be visible on the same results page, and the other way around.
For more detail, see Airtable API reference List comments
Configuration Table:
| Name* | List Comments |
| Connection* | Select your connection or create one. |
| Timeout | You can additionally set the Trigger duration to limit the information processed per execution to optimize performance and resource usage. |
| Recurrence Rule/scheduler* | Set up your recurrence rule. |
PARAMETERS
This tab enables you to configure the Trigger.
Base ID*:
Select the Base or enter it ID.
Table ID or Name*:
Select the Base table or enter it ID.
Record ID*:
Select the primary field (record) from the table that contains comments.
Page size:
If specified, this will determine the number of comments to return. Must be less than or equal to 100. Default is 100.
Offset:
A pointer to a specific comment. If specified, the returned comments will begin at the specified offset. An offset to the next set of comments will be provided by the API if the number of returned comments exceed the page Size.
Retrieve record by:
Select the comments type:
- All Records
- New Records
- Updated Records
This tab allows you to preview the data that will be retrieved and included in the output.
In specific Trigger instances, data can only be previewed when it is available for retrieval. If no event occurs from the Trigger, a message “No data available” will be displayed.
Use this button to preview the data based on the “Configure Parameter” tab.
(*) required field
Response example
{
"id": "usrtJtpUUBJucxCKl",
"createdTime": "2024-08-16 07:02:30",
"lastUpdatedTime": "2024-08-16 07:02:30",
"text": "Hello, world!",
"author": [
{
"output_field": "id",
"display_name": "Id",
"sample_data": "usrL2PNC5o3H4lBEi",
"type": "string",
"in_methods": [
"ListComments",
"CreateComment",
"UpdateComment"
]
},
{
"output_field": "email",
"display_name": "Email",
"sample_data": "info@wiresk.com",
"type": "string",
"in_methods": [
"ListComments",
"CreateComment",
"UpdateComment"
]
},
{
"output_field": "name",
"display_name": "Name",
"sample_data": "Wiresk Comments",
"type": "string",
"in_methods": [
"ListComments",
"CreateComment",
"UpdateComment"
]
}
]
}⚠️ Reminder: Click “Use” to validate your Trigger with sample data before saving.
Webhook Trigger: Copy Link
Airtable Webhook Copy Link
Note that tables, fields, and views in the specification must be specified by ID rather than by name. You may find the IDs for each of these with the manage fields UI.
For developers, see Airtable Webhooks.
Configuration Table:
| Description* | Name or description of the Webhook |
| Connection* | Select your connection or create one. Refer to how to create a connection. |
| API Key* | Select or Create an API Key for authenticating the Webhook request. |
PARAMETERS
*Base ID:
Select the specific Airtable base (database) or input its unique Base ID manually
Filters:
Data Type:
Select one or more data types:
Table Data: record and cell value changesTable Fields: field changesTable Metadata: table name and description changes
Record Change Scope:
From Source:
Lets you define which types of actions should trigger the webhook. You can select one or multiple sources:
Client: changes generated by a user through the web or mobile clientsPublic Api: changes generated through the Airtable APIForm Submission: changes generated when a form view is submittedForm Page Submission: changes generated when an interface form builder page, form layout page, or record creation button page is submittedAutomation: changes generated through an automation actionSystem: changes generated by system events, such as processing time function formulasSync: changes generated through Airtable SyncAnonymous User: Changes made by unidentified users.Unknown: Source couldn’t be determined.
Watch Data in Field IDs:
Enter field IDs.
Note: Use the Enter key to input multiple values.
Only trigger when specific field IDs change. If omitted, all fields within the table/view/base are watched.
For example, instead of tracking any record update, you can track changes to just the “Status” or “Approved” field by referencing their field IDs.
Warning: If fields are specified and one of the specified fields are deleted, the webhook will generate an error payload and the webhook will go into an error state and payloads will no longer be generated. More information about the error reponse is available in Webhooks payload.
Change Type:
Select one or more change types:
Add: Trigger when a new record is created.Update: Trigger when an existing record is modified.Remove: Trigger when a record is deleted.
Watch Schemas of Field IDs:
Enter specific Airtable field IDs.
Note: Use the Enter key to input multiple values.
This option is related to changes in the structure (schema) of specific fields. If you provide field IDs here, the webhook will only trigger for schema changes (like renaming a field or changing its type) for those particular fields. If omitted, schemas of all fields within the table/view/base are watched.
Warning: If fields are specified and one of the specified fields are deleted, the webhook will generate an error payload and the webhook will go into an error state and payloads will no longer be generated. More information about the error reponse is available in Webhooks payload.
Source Options:
Only create data when the structure of these fields changes. If you don’t specify, Wiresk will watch the structure of all fields in the table/view/base.
Page ID:
Enter the specific ID of an Airtable Page
View ID:
Enter the specific ID of an Airtable View within the selected table.
This allows you to monitor changes specifically within a particular view of your data. For example, you might only want to trigger a workflow when records are added or modified within a specific filtered view.
Includes:
By default, the payloads only contain the data that changed. In order to generate payloads with more contextual data, an includes object may be added to the specification:
Include Cell Values in Fields IDs:
Enter specific Airtable field IDs.
Note: Use the Enter key to input multiple values.
A list of fields to include regardless of whether or not they changed.
Include Previous Cell Values:
Select : True – False
If you set this to “True”, the webhook payload will include the previous values of the cells that were changed during an “Update” operation. This allows you to see what the data was before the modification.
Include Previous Fields Definitions:
Select : True – False
If you set this to “True”, the webhook payload will include the previous definitions (schema) of the fields that were changed (relevant for “Table Fields” data type). This would be useful for tracking changes to field properties like their type or options.
(*) required field
Test and automate your Flow Copy Link
Once your Flow is configured, you can test or automate it using the Run panel or by managing Triggers from the Flow Management screen.
- Run Flow: Manually runs the Flow once using sample data. Ideal for testing logic and field mapping. See How to Run a Flow.
- Run Scheduler: Force-runs the Trigger immediately using live input. This bypasses the recurrence rule and is useful for verifying real data mapping. Learn more in Wiresk Scheduler – The Fundamentals.
From the Trigger management panel (clock icon), you can:
- Activate or deactivate Triggers
- Force-run the scheduler
- Copy Routing Keys (for HTTP Triggers)
If your Flow uses a Webhook Trigger, it runs automatically on each incoming webhook—no scheduler required. It remains active until you manually deactivate it.