Start from Shopify events or authenticated external triggers. Read and update Shopify, transform data, and call external APIs without operating webhook infrastructure.
Cloudhooks receives Shopify webhooks and authenticated external triggers, then runs your JavaScript in a managed environment. Your team does not need to host the endpoint, maintain SSL, wire Shopify credentials, operate queue workers, or build a logging stack.
Run hooks from Shopify events or authenticated requests from external systems.
Use authenticated Shopify GraphQL and REST clients from your hook code.
Cloudhooks handles endpoint registration, trigger authentication, queueing, and execution.
Use Shopify examples or your own payloads in the cloud sandbox. Change fields to simulate edge cases, run the hook, and inspect each action before the integration can affect production data or notify a customer.
Start with preloaded webhook examples, modify any field, and test again..
Inspect console output, Shopify responses, external API responses, return values, and errors from the test run..
Write, test, and debug without ngrok, port forwarding, or a local webhook endpoint.
For each retained execution, inspect the incoming payload, code behavior, action responses, timing, console output, and errors. Diagnose production behavior from one execution record instead of assembling evidence across several infrastructure tools.
Review payloads, action responses, errors, output, and timing for the retention period included with the plan.
Filter executions by date, status, or resource identifier to find the relevant run.
Cloudhooks captures execution logs by default; your team does not need a separate logging service for hooks.
If an external API is unavailable or a hook contains a bug, inspect the failed execution and correct the underlying problem. While the execution remains within the plan's retention window, replay its original payload and inspect the new result.
Re-run a retained execution after fixing code or restoring the destination system..
Copy a production payload into the sandbox, change fields, and verify the fix before replaying.
For enabled hooks, Cloudhooks can retry short 429 waits and schedule eligible HTTP actions after longer Retry-After periods.
Store configuration in store-level and hook-level environment variables and access it through context.env. Change credentials or environment-specific values without embedding them in the JavaScript business logic.
Start with 100 free actions each month. Usage above that is billed progressively, with no seat fee or minimum monthly subscription.
What is Cloudhooks?
Cloudhooks is a managed Shopify integration runtime for developers and agencies. Run JavaScript from Shopify webhooks or authenticated external triggers, read or update Shopify with GraphQL, transform data, and call external APIs without operating your own webhook infrastructure.
Do I need a server or DevOps experience?No. Cloudhooks provides the webhook endpoints, managed execution environment, Shopify authentication, queues, HTTP action retries, and execution logs. You write and operate the integration logic without provisioning a webhook server or queue worker.
Do I need a developer to use Cloudhooks?Yes. Cloudhooks is built for developers and technical operators who write JavaScript. If you need no-code merchant automation, Shopify Flow is usually the better starting point. Use CloudHooks when the integration requires custom transformations, external APIs, Shopify GraphQL operations, or precise business logic
What happens when Shopify changes its API?Cloudhooks monitors the Shopify API versions used by its built-in clients and provides notices and an upgrade path. Shopify schema changes can still affect your business logic, so review documented breaking changes and test the hook before its version is upgraded.
How do environment variables work?Define store-level and hook-level environment variables and access them through context.env. Use them for credentials and environment-specific configuration so those values do not need to be embedded in your JavaScript.
What's the execution timeout? A hook execution can run for up to 30 seconds. If your integration needs longer processing, contact us to discuss the workload and architecture.
What limits apply to external triggers?External triggers currently support 200 requests per minute, 1,000 per hour, and 5,000 per day. Contact us before launch if the integration requires higher inbound limits.
How is Cloudhooks different from Shopify Flow?Shopify Flow is a no-code tool for merchant automation. Cloudhooks is a developer-first runtime for custom integrations: write JavaScript, call external APIs, run Shopify GraphQL queries and mutations, and implement logic that does not fit a visual workflow. They solve different primary jobs and can be used alongside each other.
Which Shopify events can trigger hooks?CloudHooks supports more than 30 Shopify webhook topics, including orders, customers, products, inventory, fulfillments, and refunds. External systems can also start hooks through authenticated HTTPS triggers.
How does pricing work?The first 100 actions each month are free. Actions 101-10,000 cost $0.01 each, and actions 10,001-200,000 cost $0.005 each. Contact us for usage above 200,000 monthly actions. Shopify may display a monthly spending authorization during installation; it is a billing limit, not a forecast of your bill.
What happens when an external service goes down?Cloudhooks records the execution for the retention period included with your plan. After the service recovers, inspect the failure and replay the retained execution. HTTP actions can also recover from eligible 429 responses when rate-limit handling is enabled for the hook.
How do external triggers work?External triggers expose HTTPS endpoints with Bearer token, API key, Basic Auth, or HMAC authentication. Use them to start a hook from an ERP, warehouse system, payment provider, internal service, or any system that can send an HTTP request. The hook can then read or update Shopify and call additional APIs.
Can I use npm packages?
Cloudhooks does not support npm installs. The runtime includes common capabilities such as Axios, Shopify REST and GraphQL clients, email, PostgreSQL access, cryptographic utilities, and hookUtils. Check the runtime documentation before committing to a library-dependent design.
Is there a local development environment?
No. Development happens in the Cloudhooks cloud editor and sandbox. Write, test, and debug where the hook runs without configuring ngrok, port forwarding, a local webhook endpoint, or separate environment plumbing.
It's become my go-to for any custom integration. Much easier than having to set up your own endpoint or serverless functions.
This app is a lifesaver. We have been migrating several post purchase events from Amazon Lambda to cloudhooks.
Cloudhooks was really useful for adding some after order automation for a client without requiring our own server.