Add a row to Airtable for every Pushcut action executed

Every time a Pushcut action is executed, this workflow creates a new record in an Airtable table, giving you a running log of what was run and when.

Pushcut

Airtable

Download this workflow Browse more workflows

2 steps Setup ~5 min Used on 805 sites Free to import

The Add a row to Airtable for every Pushcut action executed workflow on the FlowMattic canvas, with 2 steps across Pushcut, Airtable — The workflow as it appears in the builder after import. Each step opens for editing.

What this workflow does

Pushcut actions are quick to tap and quick to forget. If you use them to mark tasks done, start routines or record events from your phone, there is no easy list of what you ran afterwards. This workflow writes each executed action to Airtable, where you can sort, count and review them.

The Pushcut trigger fires whenever an action is executed and passes the data Pushcut sends with that event to FlowMattic. The Airtable step then runs Create Record, adding one new record to the base and table you choose. You decide which parts of the Pushcut data go into which Airtable fields.

There is no Filter in the template, so every executed action becomes a record. Each run also appears in Task History, which shows what Pushcut sent and how Airtable answered. That helps when you first map the fields and want to see exactly which values arrive from Pushcut.

Habit and routine tracking

Tap a Pushcut action each time you finish a workout or take medication. Airtable keeps one record per tap, so you can count them by week.

Field work check-ins

A technician runs a Pushcut action on arrival at a job. Each check-in becomes an Airtable record the office can review against the schedule.

Audit trail for home or office automations

Pushcut actions that open a gate or start a device each leave a record in Airtable, giving you a history of when they were used.

How this workflow runs

What happens at each step once the workflow is on, and what you need before you import it.

Step 1Trigger
Pushcut Action Executed
Starts a run each time a Pushcut action is executed. The data Pushcut sends with that event becomes available to map into the Airtable record.
Step 2Action
Airtable Create Record
Adds one Airtable record per executed action, in the base and table you select. Map the Pushcut event data into your table's fields, and connect your Airtable account after import.

What you need

FlowMatticCore
Pushcut AccountAccount
Airtable AccountAccount

After importing, map your own data. To keep the template universal, not every step is pre-filled. Open each step in the builder and connect your accounts and fields (channels, lists, sheets, recipients) before you switch the workflow on.

Make it yours

Changes worth making after you import it.

Add a created-time field to your Airtable table. Airtable fills it in for each new record, so you can see when every action was logged.
Add a Filter after the trigger if you only want certain actions logged. Base the condition on a value Pushcut sends with the event, after a test run shows what those values are.
Execute one Pushcut action right after import so FlowMattic captures a sample event. Its values are then ready to map into the Airtable fields.

Questions about this workflow

Does every Pushcut action create an Airtable record?

Yes, as imported. Any executed action that reaches the trigger starts a run, and the run adds one record. Add a Filter if you want to log only some of them.

Which Pushcut details can I store in Airtable?

Any value that arrives from Pushcut when the action runs can go into a field. Execute an action as a test after import to see the values, then map the ones you want into your table.

Can the workflow update an existing Airtable record instead of adding one?

Not as imported. The Airtable step uses Create Record, so each executed action adds a new record and existing ones are left alone.

Do I need both a Pushcut and an Airtable account?

Yes. You connect Pushcut for the trigger and Airtable for the record step. The Airtable base and table need to exist before you map the fields.