What Is a Trigger

A Trigger is the first step of every Flow in Wiresk. It tells the system when to start running the automation.

You can think of the Trigger as the condition or event that activates the Flow. Once this event happens, Wiresk moves on to the next step (one or more Methods).

Without a Trigger, a Flow cannot run.

Types of Triggers in Wiresk Copy Link

Triggers in Wiresk define when a Flow should start. The platform supports several types of Triggers, depending on your use case, the connected app, and the data source.

Each type fits a different situation. Below is a breakdown with examples and links to related help articles.

1. Event-Based Triggers Copy Link

These Triggers activate the Flow when a specific event happens in an external system.
Wiresk either polls the app (checks for updates at regular intervals) or listens to incoming data via webhooks, depending on the integration.

Examples:

• New contact created in HubSpot
• New row added in Google Sheets
• New email received in Gmail

These are ideal for automations that respond to real-time updates or incoming data from other systems.

2. Scheduled Triggers Copy Link

Scheduled Triggers start a Flow based on a recurrence rule you define. This is helpful when you want your Flow to run at regular intervals without waiting for a specific event from an external app.

Common use cases include:

• Checking for new data on a schedule
• Pulling reports at set times
• Syncing systems daily or weekly
• Sending scheduled alerts or reminders

Examples of recurrence:

• Every 15 minutes
• Every Monday at 08:00
• The 1st of every month

You define the schedule directly when setting up the Trigger. Once saved, Wiresk automatically activates the scheduler and runs the Flow based on that rule. There’s no need for additional configuration after saving.

To learn how Wiresk’s scheduler works and how to set it up properly, see: Wiresk Scheduler: The Fundamentals

3. HTTP Triggers Copy Link

An HTTP Trigger allows an external system to start a Wiresk Flow by making a request to a specific URL.

When you set up this Trigger, Wiresk generates a Routing Key URL. This URL is unique to your Flow and your Group. It looks like an API endpoint, and you can configure any system to send a POST request to it with relevant data.

This is ideal when:

• The external system supports sending HTTP requests but not webhooks
• You need full control over the request structure
• You want to simulate webhooks without waiting for polling

HTTP Triggers support:

• Routing Key for identifying the target Flow
• API Key for authentication
• Field Filters to control when the Flow should actually run (based on data conditions)

Learn more:

• How API Keys, HTTP Triggers and Routing Keys Work

4. Manual Trigger (Run Once) Copy Link

This Trigger type is used for manual testing or one-time execution.
You can start the Flow yourself by opening the Flow Builder and clicking the Run button.

It’s commonly used when:

• You want to test a Flow before activating it
• You’re handling one-off tasks (e.g., import a list, send a notification)

There’s no schedule or automation with this option. It runs once and stops.

More info:

• Troubleshooting error
• How to run a flow

Trigger Settings and Features Copy Link

When configuring a Trigger in Wiresk, you can adjust several options depending on the type of Trigger you choose:

App and Action: Choose the app (e.g., HubSpot) and what type of event to watch (e.g., new record).

Entity: Select the specific object, such as “Contact,” “Deal,” or “Ticket.”

Filters (optional): Add conditions to narrow the scope. For example, “Only trigger when contact lifecycle stage is ‘Lead’.”

Recurrence Rule (for scheduled Triggers): Define how often to check for new data. Options include minutely, hourly, daily, etc.

Preview Data: See a sample of what data will be available for mapping in the next steps.

Webhook Settings: Wiresk supports webhook-based Triggers for apps that can send real-time updates. The setup is simple and depends on whether the app supports native webhook creation through API.

In apps that support API-based webhook creation, Wiresk allows you to configure the webhook directly within the Trigger step. For example, in the Dynamics CRM Trigger “On Update Record,” you’ll find the following settings:

• Description: A label for the webhook
• Connection: Choose or create a Wiresk Connection to your Dynamics account
• API Key: Select or generate an API Key to authenticate incoming requests
• Record Type: Select the CRM object to monitor (e.g., Contact, Account, Opportunity)
• Filtering Attributes: (Optional) List the fields to monitor. Only updates to these fields will trigger the webhook.
  For example, you can list “Status,” “Owner,” or “Priority.” This narrows the trigger to relevant changes only.

Wiresk handles the registration and communication with the external system through the connected app’s API.

If the app does not support native API-based webhook creation, you can manually create the webhook in the external app’s system (if supported).

In that case, use Wiresk’s HTTP Trigger. Wiresk provides a Routing Key URL and API Key. You can configure the external system to send HTTP requests to that URL whenever an event occurs.

For more information on HTTP Triggers and authentication setup, see: How API Keys, HTTP Triggers and Routing Keys Work

Example Copy Link

Use Case: Start a Flow when a new deal is added in HubSpot.

• Trigger: HubSpot → Retrieve New Records → Entity: Deal
• Recurrence: Every 10 minutes
• Condition Filters: Only deals with amount > $1000

Once this Trigger runs and finds a matching deal, the Flow continues to the next Method step.

Important Notes Copy Link

• You must have a valid Connection to the app before configuring the Trigger.
• Some Triggers require permissions or additional setup in the external app (e.g., Gmail labels, API keys).
• If the Trigger is not correctly configured or returns no data, the Flow will not proceed.

Don’t stop here! Copy Link