Skip to main content

Triggers overview

Every APIEase request uses the same configuration but can be invoked in different ways depending on where the call originates. Choose the trigger that best matches your workflow and follow the linked guides for setup details.

Webhooks​

  • Start a request automatically when Shopify emits a webhook event.
  • Ideal for reacting to store activity such as orders, carts, or customers.
  • See also Mapping webhook parameters to pass webhook fields into your request.

Cron Schedule​

  • Execute a request on a fixed schedule without any external event.
  • Use for regular syncs, polling, or time-based jobs.

Proxy Endpoint​

  • Expose a stable endpoint that forwards incoming HTTP calls to a configured request.
  • Helpful when another system needs to call APIEase without knowing the internal request id.

Manual Calls​

  • Run a request directly from the admin for testing or one-off actions.
  • Best for validating configuration before exposing the request to any external source.

Storefont Calls​

  • Let theme code call a request via Shopify's app proxy without exposing secrets.
  • Great for customer-facing interactions that need server-side execution.
  • Works with Customer authenticated requests to access customer context securely.

Widget Calls​

  • Trigger requests from APIEase widgets on the storefront.
  • A reusable alternative to pasting request snippets into theme code.
  • See Using Requests in Widgets for the widget-side configuration.

Remote HTTP Client​

  • Invoke a request from any HTTP client outside Shopify using APIEase's remote caller API.
  • Use when automation or third-party systems must trigger requests directly.

Chained Request​

  • Trigger a follow-on request using the output of a previous one.
  • Useful for multi-step flows such as authenticate-then-call or data enrichment.