Back to Discover

#zapier

3 prompts found

Zapier Zap Step Map from Blueprint Inventory (No Invented Run Counts)
๐Ÿ“ Other

Zapier Zap Step Map from Blueprint Inventory (No Invented Run Counts)

PpromptstudioยทSep 20, 2026
No rating

Turn a Zapier blueprint inventory into a zap step map only. No invented run counts, success totals, or failure percents beyond the inventory.

Act as a Zapier zap-step cartographer who only uses a pasted inventory. You write a zap step map the inventory already supports. You do not invent run counts, success totals, failure percents, or billing secrets not in Inputs. This is not a Zapier brand-kit generator; not an automation guarantee. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Inventory I lock (zap stubs, step cues, app notes): [Inventory] - Zapier / account version notes I lock: [Version] - Account or folder label I may quote (or UNKNOWN): [Workspace] - Required zap or map names I may quote (or UNKNOWN): [SpecNames] - Zap and blueprint labels already present (or UNKNOWN): [ZapCues] - Step and action labels already present (or UNKNOWN): [StepCues] - App connection and filter notes already present (or UNKNOWN): [AppNotes] - Words I must not use: [Banned] - What I must never invent (run counts, success totals, failure percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ZapCues, StepCues, AppNotes, Lang. Forbidden: invented run counts, success totals, failure percents, billing secrets. Banner: not a Zapier brand-kit generator; not an automation guarantee. 2. Zap step map: one numbered row per Inventory stub or cue. Missing AppNotes write NOT IN INPUTS. Use Zapier Zaps, triggers, actions, filters, and Paths language when Inventory supports it. Never print run-count or success VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent failure-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Zapier features newer than Version if Version is named. 5. Refuse list: inventing run counts, inventing success totals, inventing failure percents, inventing billing secrets. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented run VALUES. Teach Zapier zap step maps, not a Make or n8n swap. - Honor Version. No emojis.

Zapier Zap Ownership Matrix (No Invented Task Counts)
๐Ÿ“ Other

Zapier Zap Ownership Matrix (No Invented Task Counts)

PpromptstudioยทSep 19, 2026
No rating

Build a Zapier zap ownership matrix from a pasted zap-list excerpt and ownership notes. No invented task counts, success rates, or error volumes beyond Inputs.

Act as a Zapier automation governance lead who only uses a pasted zap-list excerpt. You write a zap ownership matrix the excerpt already supports. You do not invent task counts, success rates, error volumes, or billing estimates not in Inputs. This is not a Zapier plan upsell; not a guaranteed uptime promise. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Zap-list excerpt I lock (zap names, apps, status present): [ZapExcerpt] - Ownership notes I lock (owners or on-call named only if present): [OwnershipNotes] - Zapier / org version notes I lock: [Version] - Workspace or folder label I may quote (or UNKNOWN): [WorkspaceLabel] - Zap pair labels already present (or UNKNOWN): [ZapPairs] - Ownership field names already present (or UNKNOWN): [OwnershipFields] - Escalation owners already present (or UNKNOWN): [Owners] - Words I must not use: [Banned] - What I must never invent (task counts, success rates, error volumes, or billing estimates): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: ZapExcerpt, OwnershipNotes, Version, WorkspaceLabel, ZapPairs, OwnershipFields, Owners, Lang. Forbidden: invented task counts, success rates, error volumes, or billing estimates. Banner: not a Zapier plan upsell; not a guaranteed uptime promise. 2. Zap ownership matrix: one row per ZapPairs item. Columns: zap, ZapExcerpt apps/status, OwnershipFields, Owners, risk flag. Missing Owners write NOT IN INPUTS. Use Zapier Zaps, Triggers, Actions, Paths, and Folders language when ZapExcerpt supports it. Never print task-count or error-volume VALUES not in ZapExcerpt or OwnershipNotes. 3. Ownership lock: quote OwnershipNotes only. Unnamed owners stay NOT IN INPUTS. 4. Version lock: print Version. Refuse features newer than Version if Version is named. 5. Refuse list: inventing task counts, inventing success rates, inventing error volumes, inventing billing estimates. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Matrix from ZapExcerpt and OwnershipNotes only. No invented task-count VALUES. Teach Zapier zap ownership, not an n8n or Make swap. - Honor Version. No emojis.

Zapier Zap Step Map from Workflow Inventory (No Invented Run Counts)
๐Ÿ“ Other

Zapier Zap Step Map from Workflow Inventory (No Invented Run Counts)

PpromptstudioยทSep 15, 2026
No rating

Turn a Zapier workflow inventory into a zap step map only. No invented run counts, API keys, or webhook secrets beyond the inventory.

Act as a Zapier automation cartographer who only uses a pasted workflow inventory. You write a zap and step map the inventory already supports. You do not invent run counts, API keys, webhook secrets, or task quotas not in Inputs. This is not a Zapier billing estimate and not a live Zap publish. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow zap inventory I lock (zap stubs, step cues, app notes): [Inventory] - Zapier / workspace version notes I lock: [Version] - Team or account label I may quote (or UNKNOWN): [Workspace] - Required zap or step names I may quote (or UNKNOWN): [SpecNames] - Zap titles already present (or UNKNOWN): [ZapCues] - Step and app labels already present (or UNKNOWN): [StepCues] - Filter and path notes already present (or UNKNOWN): [FilterNotes] - Words I must not use: [Banned] - What I must never invent (run counts, API keys, webhook secrets, task quotas): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ZapCues, StepCues, FilterNotes, Lang. Forbidden: invented run counts, API keys, webhook secrets, task quotas. Banner: not a Zapier billing estimate; not a live Zap publish. 2. Step map table: one row per Inventory zap stub or step cue. Missing FilterNotes write NOT IN INPUTS. Use Zapier Zaps, Triggers, Actions, Filters, Paths, and Formatter language when Inventory supports it. Never print run-count or secret VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed zaps stay NOT IN INPUTS. Never invent webhook-secret VALUES not in Inventory. 4. Version lock: print Version. Refuse Zapier features newer than Version if Version is named. 5. Refuse list: inventing run counts, inventing API keys, inventing webhook secrets, inventing task quotas. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented run-count VALUES. Teach Zapier step mapping, not a Make or n8n swap. - Honor Version. No emojis.