Wiresk

Wiresk

Standard HTTP – Triggers

Estimated reading time: 1 min

What will start your automation…

HTTP Standard HTTP - Triggers

Run Once Tab: This tab allows you to schedule a Flow to execute a single time at a specific date and time. This is ideal for one-time operations such as data syncs, cleanups, or initial configuration steps. After execution, the schedule will be automatically cleared unless rescheduled manually.

Run Tab: This tab is used to set up repeating schedules:

  • Repeat feature: This dropdown determines how long the automation will continue repeating based on the selected frequency (Minutely or Hourly). You can choose from:
    • Repeat Forever
      • The automation will continue to run indefinitely at the defined interval (e.g. every 15 minutes).
      • No end condition is specified.
    • Repeat for (x) Times
      • You set a specific number of repetitions.
      • Requires the field Number (x) of Repeat Times to be filled (e.g. 10 times).
    • Repeat Between Start & End Dates
      • The automation will run only within a defined date range.
      • Additional fields will appear to select start and end dates.
      • Useful for limited-time schedules like campaigns or batch jobs.
  • Daily at Multiple Times: Sets the Flow to run several times per day based on a minutely or hourly interval.
  • Daily: This allows a Flow to run x times per day at a specific time.
  • Weekly: This allows you to run a Flow weekly by selecting the days and time.
  • Monthly: This will monitor your Trigger every month on a defined date and hour.
  • Yearly: This will monitor your Trigger on a specific date and hour every year.
  • Specific dates: This will start your Trigger on specific dates and time.

For more details, see Wiresk Scheduler – The Fundamentals.

After configuring your Trigger, you can load sample data into the Example Input panel in Flow Builder. This gives you a preview of what the Trigger returns and prepares the data for mapping.

How to get it:

  • Enter manually: Add your own sample data in the JSON editor, plain JSON string, or form view.
  • Use predefined Trigger samples: Triggers provide ready-made sample data that can be pulled directly into the Example Input panel.
  • Capture Example Input: Enable this option to record real data the next time the Flow runs. The captured sample will automatically appear in the panel.

With Sample Input in place, you can review the field structure and connect Trigger outputs to Method parameters with confidence.

For more details, refer to Example Input – How it Works.

Configuration Table:

Name*Retrieve Records via HTTP Request
Connection*Select your connection or create one.
TimeoutYou can additionally set the Trigger duration to limit the information processed per execution to optimize performance and resource usage.
Recurrence Rule/scheduler*Set up your recurrence rule.

PARAMETERS

This tab enables you to configure the Trigger.

URL

The endpoint to retrieve data from. Supports both absolute and relative URLs. Example: https://api.example.com/v1/orders.

Method

Choose the HTTP method used for the request. Typically GET for retrieving data, but POST, PUT, or PATCH can be used if the API requires a body.

Headers

Add custom HTTP headers to your request. Common examples include Content-Type or Authorization.

Query Parameters

Add key-value pairs that define URL filters or parameters. Example: status=active or limit=50.

Add

Used to insert a new header or query parameter. Opens the key-value configuration panel.

This tab allows you to preview the data that will be retrieved and included in the output.

In specific Trigger instances, data can only be previewed when it is available for retrieval. If no event occurs from the Trigger, a message “No data available” will be displayed.

preview data button 2025 04 09 Standard HTTP - Triggers

Use this button to preview the data based on the “Configure Parameter” tab.

(*) required field

Sample response 
The response depends entirely on the API response of the URL you connect to.
Because this is a generic HTTP request Trigger, Wiresk doesn’t modify the structure, it displays the raw JSON as returned by the endpoint.

Once your Flow is configured, you can test or automate it using the Run panel or by managing Triggers from the Flow Management screen.

  • Run Flow: Manually runs the Flow once using sample data. Ideal for testing logic and field mapping. See How to Run a Flow.
  • Run Scheduler: Force-runs the Trigger immediately using live input. This bypasses the recurrence rule and is useful for verifying real data mapping. Learn more in Wiresk Scheduler – The Fundamentals.

From the Trigger management panel (clock icon), you can:

  • Activate or deactivate Triggers
  • Force-run the scheduler
  • Copy Routing Keys (for HTTP Triggers)

If your Flow uses a Webhook Trigger, it runs automatically on each incoming webhook—no scheduler required. It remains active until you manually deactivate it.