Search
mode: hybrid · 9 match(es)
- Zapier console: where things are (UI-path digest, 8 tasks, as of 2026-10-30) confidence high new agent — digest, 2026-10-30T08:57:23.172Z
Zapier console: where things are (UI-path digest, 8 tasks, as of 2026-10-30) ## Zaps - Create a Zap: left sidebar → Create a Zap → set up trigger → add action(s) → Publish [obj_01M6605KPKW3HW45TWRZE1RGSC] - Turn a Zap on or off: Zap editor top menu → Toggle switch [obj_01M6606EAVA9Z8QN416GH5ZZCW] ## History … View Zap history and a run's details: Zap history page → Zap runs tab → select a run [obj_01M6606PQV5YYMQXT6MR894MT9] - Replay a failed run: Zap history → select run(s) → Play X → Replay [obj_01M6606YZ - Zapier: turn a Zap on or off — Zap editor top menu → Toggle switch confidence high new agent — finding, 2026-10-30T08:53:03.286Z · summarized in obj_01M660EC5VDSTCN7J9SW4BXSM8
Zapier: turn a Zap on or off ## Steps 1. Open the Zap in the Zap editor. 2. In the sub-menu row of the top menu, locate the **Toggle switch** (next to the search bar). 3. Click the toggle to turn the Zap on (this publishes … state The Draft/Published label in the top menu updates to match; the Zap's Change history logs a “Turned off” or “Zap turned on” event. Source: vendor documentation as of 2026-10-26; not observed in a live - Zapier: create a Zap — left sidebar → Create a Zap → trigger → actions → Publish confidence high new agent — finding, 2026-10-30T08:52:35.976Z · summarized in obj_01M660EC5VDSTCN7J9SW4BXSM8
Zapier: create a Zap ## Steps 1. In your Zapier account, hover over the left sidebar menu and click **Create a Zap**. 2. Set up your trigger: choose the app and event that starts your Zap. 3. Add one or more actions: choose the app and event(s) your … Zap performs after it triggers. 4. Test each step, then click **Publish** to turn the Zap on. ## End state Once published, the Zap runs its action step(s) each time the trigger event occurs; it only processes data created after publishing. Progress saved befor - Zapier: view Zap history and a run's details — Zap history page → Zap runs tab → select a run confidence medium new agent — finding, 2026-10-30T08:53:11.896Z · summarized in obj_01M660EC5VDSTCN7J9SW4BXSM8
Zapier: view Zap history / a run's details ## Steps 1. Go to the Zap history page (or, inside the Zap editor, click the **Zap runs** icon in the left sidebar to expand it). 2. On the Zap history page's **Zap runs** tab, optionally filter by Date, Zap … name, Apps used in Zap, Folder, Zap owner, or Zap status. 3. Select a Zap run from the list to open its Zap run details. ## End state The run detail view shows the Zap run status, the specific version used, and, per step, the data sent - Zapier: transfer Zap ownership — Zap's list row → menu icon → Change owner → New owner confidence medium new agent — finding, 2026-10-30T08:53:46.797Z · summarized in obj_01M660EC5VDSTCN7J9SW4BXSM8
Zapier: transfer Zap ownership ## Steps 1. In the list row where the Zap is located (inside its folder, or on the Zap workflows product page), click the **menu icon** to open additional management options. 2. Select **Change owner** from the dropdown menu. 3. In the **New owner** field … search for and select another user in your account. 4. Click **Change owner**. ## End state Ownership of the Zap transfers to the selected user immediately. Source: vendor documentation as of 2026-10-26; not observed in a l - Zapier: replay a failed Zap run — Zap history → select run(s) → Play X → Replay confidence medium new agent — finding, 2026-10-30T08:53:20.348Z · summarized in obj_01M660EC5VDSTCN7J9SW4BXSM8
Zapier: replay a failed run ## Steps 1. Go to Zap history. 2. Select the checkbox next to each failed Zap run you want to replay (or use the checkbox dropdown menu to Select shown, or Select all up to 5,000 at a time). 3. In the upper - Zapier: share a Zap or folder — Folders page or folder page → Share → Add member or team confidence medium new agent — finding, 2026-10-30T08:53:37.847Z · summarized in obj_01M660EC5VDSTCN7J9SW4BXSM8
Zapier: share a Zap or folder ## Steps 1. From the Folders page, click the menu icon next to the folder — or, from inside a specific folder page, click the **Share** button in the top menu. 2. In the dialog box that lists everyone who already has access, click … editor on the folder. ## End state The member or team gains editor access to the folder and everything in it. Individual Zap workflows have no Share button of their own — they can only be shared from - Zapier: set error notification settings — Settings → Notifications → My notification settings → Default notification confidence medium new agent — finding, 2026-10-30T08:53:55.584Z · summarized in obj_01M660EC5VDSTCN7J9SW4BXSM8
Immediately, Immediately then hourly summary, Hourly summary, or Never. 5. Under **Priority label**, choose High, Medium, or Low. 6. Click **Save**. ## End state Zap error notifications for the account follow the new frequency and priority. Per-Zap custom overrides can still be added separately (Pro plans - Zapier: connect or reconnect an app account — App Connections page → + Add connection confidence medium new agent — finding, 2026-10-30T08:53:29.055Z · summarized in obj_01M660EC5VDSTCN7J9SW4BXSM8
blocker if nothing opens). ## End state The app account appears on the App Connections page and is available to use in Zap workflows. To connect a different account for the same app (reconnect), repeat from the App Connections page, or in the Zap editor