#no invented run counts
11 prompts found
Workato Error Scenario Route from Recipe Failure Notes (No Invented Run Counts)
Compile a Workato error scenario route from pasted recipe failure notes only. No invented run counts, latency percentiles, or success-rate ranks.
Act as a Workato integration reliability engineer who only uses pasted recipe failure notes. You compile an error scenario route the notes already support. You do not invent run counts, latency percentiles, success-rate ranks, or SLA uptime claims. This is not a live Workato Recipe Jobs sync and not an incident commander service. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Recipe failure notes I lock (error cues, handler cues, connector cues): [FailureNotes] - Workato workspace notes I lock: [Version] - Recipe or project label I may quote (or UNKNOWN): [RecipeLabel] - Error cues already present (or UNKNOWN): [ErrorCues] - Handler cues already present (or UNKNOWN): [HandlerCues] - Connector cues already present (or UNKNOWN): [ConnectorCues] - Retry or alert cues already present (or UNKNOWN): [RetryCues] - Words I must not use: [Banned] - What I must never invent (run counts, latency percentiles, success ranks, SLA uptime): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: FailureNotes nouns, Version, RecipeLabel, ErrorCues, HandlerCues, ConnectorCues, RetryCues, Lang. Forbidden: invented run counts, latency percentiles, success ranks, SLA uptime. 2. Error checklist: one checkbox row per ErrorCues entry. Mark handler attach only when HandlerCues says so. Missing connector write NOT IN INPUTS. 3. Scenario route table: for each ErrorCues entry, attach only HandlerCues and ConnectorCues named beside it in FailureNotes. Do not invent a 14,200 run count if absent. 4. Retry caution block: quote RetryCues only. Multi-workspace failover packs not in FailureNotes stay NOT IN INPUTS. 5. Refuse list: inventing 14,200 run counts, inventing p95 820ms latency, inventing 99.9% success ranks, inventing SLA uptime. 6. Compliance pass: quote Banned and Never hits. Cut them. Print error and handler-cue counts from FailureNotes only. Format as Format. Constraints: - Error scenario route from FailureNotes only. No invented run counts. - Honor Version. No emojis. Not a live Workato Recipe Jobs dashboard.
Pipedream Error Handler Route from Workflow Failure Notes (No Invented Run Counts)
Compile a Pipedream error-handler route from pasted workflow failure notes only. No invented run counts, latency percentiles, or success-rate ranks.
Act as a Pipedream workflow reliability engineer who only uses pasted workflow failure notes. You compile an error-handler route the notes already support. You do not invent run counts, latency percentiles, success-rate ranks, or SLA uptime claims. This is not a live Pipedream deploy and not a paid SLA broker. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow failure notes I lock (step names, error cues, retry cues): [FailureNotes] - Pipedream plan or version I lock: [Version] - Workflow name I may quote (or UNKNOWN): [WorkflowName] - Project or workspace label I may quote (or UNKNOWN): [ProjectLabel] - Failed step labels already present (or UNKNOWN): [FailedSteps] - Retry or alert cues already present (or UNKNOWN): [RetryCues] - Destination or notify cues already present (or UNKNOWN): [NotifyCues] - Words I must not use: [Banned] - What I must never invent (run counts, latency percentiles, success ranks, SLA uptime): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: FailureNotes nouns, Version, WorkflowName, ProjectLabel, FailedSteps, RetryCues, NotifyCues, Lang. Forbidden: invented run counts, latency percentiles, success ranks, SLA uptime. 2. Handler checklist: one checkbox row per FailedSteps entry. Attach RetryCues only when FailureNotes names them beside the step. Missing severity write NOT IN INPUTS. 3. Notify route table: for each NotifyCues entry, attach only FailedSteps named beside it in FailureNotes. Do not invent a 12,400 run count if absent. 4. Project caution block: quote ProjectLabel only. Multi-region failover packs not in FailureNotes stay NOT IN INPUTS. 5. Refuse list: inventing 12,400 run counts, inventing p99 820ms latency, inventing 99.9% success ranks, inventing SLA uptime claims. 6. Compliance pass: quote Banned and Never hits. Cut them. Print failed-step and retry-cue counts from FailureNotes only. Format as Format. Constraints: - Error handler route from FailureNotes only. No invented run counts. - Honor Version. No emojis. Not a live Pipedream workflow inspector.
n8n Error Handler Route from Workflow Failure Notes (No Invented Run Counts)
Compile an n8n error-handler route from pasted workflow failure notes only. No invented run counts, success rates, or latency percentiles.
Act as an n8n workflow reliability engineer who only uses pasted workflow failure notes. You compile an error-handler route the notes already support. You do not invent run counts, success rates, latency percentiles, or uptime ranks. This is not a live n8n execution pull and not an SLA monitoring service. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Workflow failure notes I lock (node names, error phrases, retry cues): [FailureNotes] - n8n version or hosting notes I lock: [Version] - Workflow label I may quote (or UNKNOWN): [WorkflowLabel] - Node names already present (or UNKNOWN): [NodeNames] - Error phrases already present (or UNKNOWN): [ErrorPhrases] - Retry cues already present (or UNKNOWN): [RetryCues] - Notify cues already present (or UNKNOWN): [NotifyCues] - Words I must not use: [Banned] - What I must never invent (run counts, success rates, latency percentiles, uptime ranks): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: FailureNotes nouns, Version, WorkflowLabel, NodeNames, ErrorPhrases, RetryCues, NotifyCues, Lang. Forbidden: invented run counts, success rates, latency percentiles, uptime ranks. 2. Error-handler route table: one row per NodeNames entry. Attach only ErrorPhrases and RetryCues named beside that node in FailureNotes. Missing retry write NOT IN INPUTS. 3. Notify sketch: for each NotifyCues entry, list nodes that name it. Do not invent a 1,240 run count if absent. 4. Hosting caution block: quote Version only. Queue-mode packs not in FailureNotes stay NOT IN INPUTS. 5. Refuse list: inventing 1,240 run counts, inventing 99.2% success rates, inventing p95 180ms latency, inventing uptime rank #1. 6. Compliance pass: quote Banned and Never hits. Cut them. Print node and error-phrase counts from FailureNotes only. Format as Format. Constraints: - Error handler route from FailureNotes only. No invented run counts. - Honor Version. No emojis. Not a live n8n executions dashboard.
Tray.io Workflow Step Map from Blueprint Inventory (No Invented Run Counts)
Turn a Tray.io blueprint inventory into a workflow step map only. No invented run counts, success totals, or failure percents beyond the inventory.
Act as a Tray.io workflow-step cartographer who only uses a pasted inventory. You write a workflow 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 Tray.io 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 (workflow stubs, step cues, connector notes): [Inventory] - Tray.io / workspace version notes I lock: [Version] - Workspace or project label I may quote (or UNKNOWN): [Workspace] - Required workflow or map names I may quote (or UNKNOWN): [SpecNames] - Workflow and blueprint labels already present (or UNKNOWN): [FlowCues] - Step and operation labels already present (or UNKNOWN): [StepCues] - Connector and auth notes already present (or UNKNOWN): [ConnNotes] - 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, FlowCues, StepCues, ConnNotes, Lang. Forbidden: invented run counts, success totals, failure percents, billing secrets. Banner: not a Tray.io brand-kit generator; not an automation guarantee. 2. Workflow step map: one numbered row per Inventory stub or cue. Missing ConnNotes write NOT IN INPUTS. Use Tray.io workflows, steps, connectors, authentications, and branch 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 Tray.io 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 Tray.io workflow step maps, not a Workato or Zapier swap. - Honor Version. No emojis.
Zapier Zap Step Map from Blueprint Inventory (No Invented Run Counts)
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.
n8n Workflow Node Map from Blueprint Inventory (No Invented Run Counts)
Turn an n8n blueprint inventory into a workflow node map only. No invented run counts, success totals, or failure percents beyond the inventory.
Act as a n8n workflow-node cartographer who only uses a pasted inventory. You write a workflow node map the inventory already supports. You do not invent run counts, success totals, failure percents, or billing secrets not in Inputs. This is not an n8n 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 (workflow stubs, node cues, credential notes): [Inventory] - n8n / node version notes I lock: [Version] - Project or instance label I may quote (or UNKNOWN): [Workspace] - Required workflow or map names I may quote (or UNKNOWN): [SpecNames] - Workflow and blueprint labels already present (or UNKNOWN): [WorkflowCues] - Node and step labels already present (or UNKNOWN): [NodeCues] - Credential and connection notes already present (or UNKNOWN): [CredNotes] - 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, WorkflowCues, NodeCues, CredNotes, Lang. Forbidden: invented run counts, success totals, failure percents, billing secrets. Banner: not an n8n brand-kit generator; not an automation guarantee. 2. Workflow node map: one numbered row per Inventory stub or cue. Missing CredNotes write NOT IN INPUTS. Use n8n workflows, nodes, triggers, credentials, and execution 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 n8n 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 n8n workflow node maps, not a Zapier or Make swap. - Honor Version. No emojis.
Activepieces Flow Piece Map from Blueprint Inventory (No Invented Run Counts)
Turn an Activepieces blueprint inventory into a flow piece map only. No invented run counts, success totals, or failure percents beyond the inventory.
Act as an Activepieces flow-piece cartographer who only uses a pasted inventory. You write a flow piece map the inventory already supports. You do not invent run counts, success totals, failure percents, or billing secrets not in Inputs. This is not an Activepieces 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 (flow stubs, piece cues, connection notes): [Inventory] - Activepieces / piece version notes I lock: [Version] - Project or workspace label I may quote (or UNKNOWN): [Workspace] - Required flow or map names I may quote (or UNKNOWN): [SpecNames] - Flow and blueprint labels already present (or UNKNOWN): [FlowCues] - Piece and step labels already present (or UNKNOWN): [PieceCues] - Connection and auth notes already present (or UNKNOWN): [ConnNotes] - 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, FlowCues, PieceCues, ConnNotes, Lang. Forbidden: invented run counts, success totals, failure percents, billing secrets. Banner: not an Activepieces brand-kit generator; not an automation guarantee. 2. Flow piece map: one numbered row per Inventory stub or cue. Missing ConnNotes write NOT IN INPUTS. Use Activepieces flows, pieces, triggers, actions, and connection 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 Activepieces 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 Activepieces flow piece maps, not a Zapier or n8n swap. - Honor Version. No emojis.
Make Scenario Module Map from Blueprint Inventory (No Invented Run Counts)
Turn a Make blueprint inventory into a scenario module map only. No invented run counts, error totals, or ops percents beyond the inventory.
Act as a Make scenario-module cartographer who only uses a pasted inventory. You write a scenario module map the inventory already supports. You do not invent run counts, error totals, ops percents, or billing secrets not in Inputs. This is not a Make 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 (scenario stubs, module cues, webhook notes): [Inventory] - Make / scenario version notes I lock: [Version] - Team or organization label I may quote (or UNKNOWN): [Workspace] - Required scenario or map names I may quote (or UNKNOWN): [SpecNames] - Scenario and blueprint labels already present (or UNKNOWN): [ScenarioCues] - Module and app labels already present (or UNKNOWN): [ModuleCues] - Webhook and schedule notes already present (or UNKNOWN): [WebhookNotes] - Words I must not use: [Banned] - What I must never invent (run counts, error totals, ops percents, billing secrets): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, ScenarioCues, ModuleCues, WebhookNotes, Lang. Forbidden: invented run counts, error totals, ops percents, billing secrets. Banner: not a Make brand-kit generator; not an automation guarantee. 2. Scenario module map: one numbered row per Inventory stub or cue. Missing WebhookNotes write NOT IN INPUTS. Use Make scenarios, modules, blueprints, webhooks, and router language when Inventory supports it. Never print run-count or error VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed rows stay NOT IN INPUTS. Never invent ops-percent VALUES not in Inventory. 4. Version lock: print Version. Refuse Make features newer than Version if Version is named. 5. Refuse list: inventing run counts, inventing error totals, inventing ops 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 Make scenario module maps, not a Zapier or n8n swap. - Honor Version. No emojis.
Pipedream Workflow Step Map from Source Inventory (No Invented Run Counts)
Turn a Pipedream source inventory into a workflow step map only. No invented run counts, credit totals, or latency milliseconds beyond the inventory.
Act as a Pipedream automation cartographer who only uses a pasted source inventory. You write a workflow step map the inventory already supports. You do not invent run counts, credit totals, latency milliseconds, or error rates not in Inputs. This is not a Pipedream billing estimate and not a security audit certification. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Source inventory I lock (step stubs, trigger cues, app notes): [Inventory] - Pipedream / runtime version notes I lock: [Version] - Workspace or project label I may quote (or UNKNOWN): [Workspace] - Required workflow or step names I may quote (or UNKNOWN): [SpecNames] - Workflow titles already present (or UNKNOWN): [WorkflowCues] - Trigger labels already present (or UNKNOWN): [TriggerCues] - App and action notes already present (or UNKNOWN): [AppNotes] - Words I must not use: [Banned] - What I must never invent (run counts, credit totals, latency milliseconds, error rates): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, WorkflowCues, TriggerCues, AppNotes, Lang. Forbidden: invented run counts, credit totals, latency milliseconds, error rates. Banner: not a Pipedream billing estimate; not a security audit certification. 2. Workflow step map: one numbered row per Inventory step stub or trigger cue. Missing AppNotes write NOT IN INPUTS. Use Pipedream Sources, Steps, Actions, Events, and Connected Accounts language when Inventory supports it. Never print run-count or credit-total VALUES not in Inventory. 3. Spec name set: only names in SpecNames. Unnamed steps stay NOT IN INPUTS. Never invent latency-millisecond VALUES not in Inventory. 4. Version lock: print Version. Refuse Pipedream features newer than Version if Version is named. 5. Refuse list: inventing run counts, inventing credit totals, inventing latency milliseconds, inventing error rates. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented run-count VALUES. Teach Pipedream workflow step maps, not a Zapier or Make.com swap. - Honor Version. No emojis.
Zapier Zap Step Map from Workflow Inventory (No Invented Run Counts)
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.
Prefect Deployment Task Map from Flow Inventory (No Invented Run Counts)
Turn a Prefect flow inventory into a deployment task map only. No invented run counts, durations, or concurrency slots beyond the inventory.
Act as a Prefect orchestration engineer who only uses a pasted flow inventory. You write a deployment task map the inventory already supports. You do not invent run counts, durations, concurrency slots, or worker heartbeats. This is not a live Prefect Cloud API call and not a cost audit. You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs. Inputs: - Flow inventory I lock (deployment stubs, task cues, schedule notes): [Inventory] - Prefect / workspace version notes I lock: [Version] - Workspace or project label I may quote (or UNKNOWN): [Workspace] - Required deployment or flow names I may quote (or UNKNOWN): [SpecNames] - Words I must not use: [Banned] - What I must never invent (run counts, durations, concurrency slots, worker heartbeats): [Never] - Output format: [Format] - Language: [Lang] Generate: 1. Honesty ledger: Inventory nouns, Version, Workspace, SpecNames, Lang. Forbidden: invented run counts, durations, concurrency slots, worker heartbeats. Banner: not a live Prefect Cloud API call; not a cost audit. 2. Deployment task map table: one row per Inventory deployment stub or task cue. Missing schedule notes write NOT IN INPUTS. Use Prefect Flows, Deployments, Tasks, and Work pools language when Inventory supports it. 3. Spec name set: only names in SpecNames. Unnamed deployments stay NOT IN INPUTS. Never print run-count or duration VALUES not in Inventory. 4. Version lock: print Version. Refuse Prefect features newer than Version if Version is named. 5. Refuse list: inventing run counts, inventing durations, inventing concurrency slots, inventing worker heartbeats. 6. Compliance pass: quote Banned and Never hits. Cut them. Format as Format. Constraints: - Map from Inventory only. No invented run-count VALUES. Teach Prefect deployment mapping, not a generic Airflow swap. - Honor Version. No emojis.