Wiresk

Wiresk

What is a Webhook Trigger

Estimated reading time: 3 min
Flat-style diagram showing how a webhook trigger works. On the left, an icon of a computer labeled "External System" points to a URL box containing "https://api.wiresk.com/api/odata/routing-key/api-key," which then points to a circular arrow icon labeled "Flow." The title "Webhook Trigger" is displayed at the top.

A Webhook Trigger starts a Flow as soon as another app sends data to Wiresk through a special link (HTTP request). This means Wiresk can act immediately when an event occurs, instead of waiting for a scheduler to run.

Use a Webhook Trigger when:

  • The other app can send data straight to a link.
  • You want the Flow to run instantly.
  • The app can create a webhook itself or lets you add Wiresk’s webhook link.

When you create a Webhook Trigger, Wiresk:

  1. Generates a Webhook URL unique to your Flow.
  2. Embeds two key elements in the URL:
    • Routing Key – Identifies which Flow to trigger.
    • API Key – Authenticates the incoming request.
  3. Waits for incoming HTTP requests from the external system.
  4. Passes the received data to the Flow’s next steps for processing.

Use this when the external system supports sending webhooks but Wiresk does not have a direct API-based setup for that app.

  1. Create or open a Flow in Wiresk.
  2. Click Add Trigger and choose HTTP Trigger.
  3. Configure the settings:
    • Description – A label to identify this webhook in your Flow.
    • API Key – Select or create a Group-level API Key for authentication.
    • Parameters – Add any required parameters for the incoming request.
  4. Save the Trigger.
  5. Wiresk will generate a Webhook URL that includes both the Routing Key and API Key.
  6. Paste this URL into the webhook configuration of the external application.
  7. Test by triggering an event in the external app and confirming that Wiresk receives the data.
Screenshot of the HTTP Trigger setup panel in Wiresk. The Description field is filled with “HTTP Trigger test.” The API Key field is set to “Default Api Key,” with a dropdown to select or search for keys, and an option to “Create new API Key” displayed below.

Some Wiresk Triggers set up the webhook for you automatically through the connected app’s API.
This applies to supported apps like Dynamics CRM, Airtable, Zoho CRM, and Mailchimp.

When you select these Triggers:

  • Wiresk uses the app’s API to create and register the webhook in the external system.
  • You don’t need to manually paste the URL in the app — Wiresk handles the registration.
  • Example Triggers include:
    • Dynamics CRM — On Update Record
    • Airtable — New Record
    • Zoho CRM — Record Updated
    • Mailchimp — New Subscriber

For more control over when a Flow runs, you can enable Filters in an HTTP Trigger or app-specific webhook Trigger.

With Filters:

  • Wiresk checks incoming data against your defined conditions before the Flow continues.
  • If the data meets the conditions, the Flow proceeds normally.
  • If it does not meet the conditions, Wiresk stops the Flow at the Trigger level (no Methods run).

Typical filter options include:

  • Equals / Does Not Equal – Match a field to a specific value.
  • Is Null / Is Not Null – Check if a field is empty or filled.
  • Like / Not Like – Match a value pattern (useful for partial matches).

Example:
If you only want to process webhooks for new customer sign-ups from a certain country:

  1. Add a Filter on the “country” field.
  2. Choose “Equals” as the operator.
  3. Enter the country code (e.g., “US”).
    Only webhooks with country = US will trigger the Flow.
Screenshot of the “HTTP Trigger (with Filter)” settings in Wiresk for Eats365. The Description field says “Filter by country.” API Key is “Default Api Key,” Platform is “Eats365,” and Entity is set to “Manual.” Under Configure Filter, there is one filter where the field “country” equals “US.”
  • Description: “Account record update”
  • Connection: Select Dynamics CRM connection.
  • API Key: Choose a Group API Key.
  • Record Type: Select “Account.”
    When an account record is updated in Dynamics CRM, the CRM sends update data to Wiresk automatically via the webhook, which then runs the Flow.
  • Filtering Attributes (Optional): This allows you to choose specific fields in the Dynamics record that will be monitored for changes. If you select one or more filtering attributes, the webhook will only trigger the Flow when those particular fields are updated.
    • For example, if you select emailaddress1 as a filtering attribute, the Flow will run only when the account’s primary email field changes.
    • If you leave this empty, the webhook will trigger for updates to any field in the selected record type.
    • When an account record meeting these conditions is updated in Dynamics CRM, the CRM sends the update data to Wiresk via the webhook, which then runs the Flow.
Screenshot of the “On Record Update” trigger settings in Wiresk for Dynamics CRM. The Description field says “Trigger when records are updated.” Connection is set to “Dynamics DEV,” API Key is “Default Api Key,” Record Type is “Account,” and there is a section for Filtering Attributes with a collapsed menu.
  • Treat the Webhook URL as sensitive information since it contains both the Routing Key and API Key.
  • Anyone with this URL can trigger your Flow.
  • Add conditional checks in the Flow to validate incoming data before processing.
  • Use Option 2 when available — it’s faster and avoids manual setup errors.
  • For unsupported apps, use the HTTP Trigger and configure the webhook manually.
  • Use Filters to reduce unnecessary Flow runs and protect resources.
  • Always send a test event to confirm data is received.
  • Name your Triggers clearly to make them easy to identify in Flow Builder.