Automation reliability survey

Help shape a practical testing tool for webhook-based automations. We are looking for where failures happen, how teams find them, and what evidence would make releases safer.

Please do not include client names, credentials or private payloads. Answers are stored on this site's server. Your IP address is not stored with your answers. Email is stored only if you explicitly agree to follow-up. See Privacy & trust.

1. About your work

This helps us separate builder, agency, internal-team and business needs instead of treating every automation user the same.

Which describes you best? (required)

What best describes your responsibility for automations? (required for the four listed audience types)

Which tools do you build with? (optional, choose any) n8n Make Zapier Custom code / scripts Other tools

How many automations have you delivered or been responsible for? (required)

2. Reliability today

These answers show where current testing breaks down and which problems deserve attention first.

How do you usually test an automation before handoff or release? (required)

How often do automation changes cause unexpected problems? (required)

How do you usually discover a problem? (required)

What is the biggest consequence when an automation problem gets through? (required)

What is the biggest reliability problem you face with automations? (optional, up to 1000 characters)

3. Value and future interest

This tells us whether repeatable evidence is worth building and whether future research is worth pursuing.

How valuable would repeatable tests and regression reports be? (required)

Would you consider testing an early version? (required)

Your answer does not register you for a programme or guarantee access, timing or a release.

Optional follow-up You may email me about this research or a possible future LoopSpec pilot. This is not marketing, and pilot participation is not guaranteed. Email (required only if you tick the box)