How to in Zapier
- Open Zapier and Create a New Zap: In the top navigation, click Make a Zap. This opens the Zap editor where you’ll define a trigger and subsequent actions.
- Select Trigger App: Tables: In Trigger, search for Tables and select it. Choose the event you want to start the zap with, such as New Record, Updated Record, or Trigger Button Clicked.
- Choose Trigger Event: Pick a trigger that fits your workflow: e.g., New Record to start on creation, Updated Record to respond to changes, or Button Clicked to manually start a flow.
- Configure Trigger: Select Table: From the Tables trigger, choose the specific table you want to monitor. This binds the trigger to that data source.
- Test Trigger: Click Test Trigger to pull sample data from the selected table. Confirm you can see current and new data as expected.
- Add Action: Create Record: Add an action step, choose Tables (or the target app), and select Create Record. Map fields from the trigger step to the destination table fields.
- Add Action: Increment Value: If you need sequential IDs or counters, add Increment Value and specify the numeric field and amount to increase.
- Add Action: Update Records: Configure Update Records to push latest data from apps back into the table. Map the record ID and fields to update.
- Add Action: Continue Zap Button Clicked: Use this to pause the zap until you click a button in the table to continue the process on demand.
- Add Action: Duplicate Table: Clone a template table if you need a fresh workspace for a recurring process. This copies fields and settings for consistency.
- Add Action: Delete Records: Clean up records you no longer need. Configure to delete specific records after a workflow completes.
- Add Filter (Optional): Insert a Filter step to run actions only when specific conditions are met (e.g., status changes, certain field values).
- Test End-to-End: Run a full test from trigger to final action. Verify data mapping and conditional logic behave as intended.
- Enable Zap: Turn on the Zap. Monitor task history to confirm runs are executing as configured and adjust if needed.