Every workflow begins with a Trigger. The Trigger defines the event BotSkyrik should wait for before starting the workflow.

When you open the Trigger node, you first choose the channel where the workflow will operate. After that, you can configure one or more trigger events for that channel.

BotSkyrik keeps this configuration in one place so you can see the channel, configured triggers, and the events that are currently able to start the workflow.

At the top of the Trigger configuration, select the channel where this workflow should run.

BotSkyrik currently uses a single-channel workflow model. A workflow is connected to one channel at a time rather than combining multiple messaging channels inside the same workflow.

Depending on the channels available in your workspace, you may see options such as WhatsApp, Telegram, Instagram, Messenger, and other supported channels.

Choose the channel first because the trigger options shown afterward are based on that channel.

In the example above, Instagram is selected. The panel below then shows the triggers already configured for that Instagram workflow.

The Configured Triggers area shows every event that can currently start the workflow.

Triggers are organized into groups so related events stay together. For example, you may see groups related to:

• messages and conversations

• contact data

• integration events

The available groups and events can expand as BotSkyrik adds more capabilities.

A workflow can contain more than one configured trigger. If any configured trigger matches, the same workflow can begin.

Use Add New Trigger when you want to add another starting condition.

For messaging channels such as Instagram, the Message & Conversation group contains events based on how the customer interacts with your account.

For Instagram, these can include events such as:

Direct Message — someone sends a DM to your Instagram account.

Post / Reel Comment — someone comments on a post or Reel.

Story Reply — someone replies to one of your Instagram Stories.

Live Comment — someone comments during an Instagram Live.

You can select the event or combination of events that should use the trigger.

The example above is editing a trigger for a Direct Message containing the keyword price.

At the top of the editor, BotSkyrik also shows which trigger you are editing and which channel it belongs to. This is useful when a workflow contains several triggers.

Inside Message Events, select the places where the trigger should listen.

For example, if you enable both Direct Message and Story Reply, the same trigger configuration can respond to matching messages coming from either source.

You do not need to create a completely separate keyword configuration for every selected message event.

This is an important part of the BotSkyrik trigger model: the selected message events can share the same keyword rules.

When you choose a comment-based event, BotSkyrik can provide additional options for deciding which content the trigger should watch.

Depending on the event, you may be able to configure the trigger around examples such as:

• any applicable post
• a specific post or Reel
• upcoming content
• a particular supported live event

The available choices depend on the selected channel and event.

Use these options when you want a workflow to respond only to interactions associated with particular content rather than every eligible interaction on the account.

The Keyword Trigger section defines the words or phrases that should actually start the workflow.

Enter one or more keywords that represent the intent this workflow is designed to handle.

For example:

price

You can add additional keywords when customers may express the same intent in different ways.

The matching rule can also be selected from the available dropdown. For example, Keyword contains means the keyword can appear anywhere inside a longer customer message.

If the keyword is price, a message such as:

What is your price?

can match the trigger.

Keyword matching is not case-sensitive, so values such as PRICE, Price, and price are treated the same way.

BotSkyrik uses one shared keyword configuration for the message events selected inside the trigger.

For example, if you select:

• Direct Message

• Post / Reel Comment

• Story Reply

and configure the keyword:

price

the same keyword rule applies across those selected events.

You do not need to enter price separately for DMs, again for comments, and again for Story replies.

This keeps the trigger easier to maintain, especially when the same customer intent can arrive from several places on the same channel.

For message-based workflow triggers, BotSkyrik expects you to define the keyword or intent that should enter the workflow.

This prevents the workflow from taking over every normal customer message or comment.

If a customer sends something that does not match the configured workflow trigger, the conversation can continue through the normal AI experience instead of being forced into an unrelated automation.

For example, imagine you have a workflow designed specifically for people asking about pricing.

You configure:

price

Messages that match that intent can enter the workflow.

A completely unrelated customer question does not need to enter the pricing workflow. Your AI agent can continue handling that conversation normally.

This makes workflows useful for specific automated journeys while allowing the AI to remain available for general conversation.

Continue scrolling down in the Trigger editor and you will also find the AI Intention configuration.

AI Intention gives you another way to help BotSkyrik understand when the trigger is relevant based on what the customer is trying to accomplish, rather than relying only on exact wording.

Use this area when you want to describe the customer intent the workflow should recognize.

For example, instead of trying to manually predict every possible phrase a customer might use when asking about pricing, you can provide guidance about the intention behind the trigger.

Keep the instruction focused on the purpose of the workflow. The clearer the intention, the easier it is for BotSkyrik to distinguish this workflow from unrelated conversations.

You may need to scroll further down the Trigger editor to reach this setting because it appears below the keyword configuration shown in the screenshot above.

Keywords and AI Intention can work together to make a trigger more precise.

Keywords give you clear matching rules for important terms and phrases, while AI Intention can help BotSkyrik understand the broader meaning behind customer messages.

You do not need to make the configuration unnecessarily complicated. For many workflows, a few strong keywords and a clear intention are enough.

The goal is to define which customer interactions belong in this workflow.

After saving a trigger, return to the main Trigger panel to see it inside Configured Triggers.

You can then add additional triggers when the same workflow needs more than one starting point.

For example, the same workflow could potentially begin from a matching customer message, a contact-data event, or an event received from a connected business system.

Each trigger remains visible in its appropriate group so you can understand at a glance what can start the workflow.

A workflow does not always need to begin with a customer message. BotSkyrik can also start a workflow when something changes in the contact's data.

To configure this, return to All Triggers, choose Add New Trigger, and open the Contact Data group.

The Contact Data Event dropdown determines what change BotSkyrik should watch for. The available events currently include New Contact Created, Tag Added, Tag Removed, Custom Field Changed, and System Field Changed.

These options may expand as additional contact events are added to BotSkyrik, but the configuration follows the same pattern: choose the event first, then provide any information required for that event.

In the example above, the workflow is configured for New Contact Created. An optional condition has also been added so the workflow only starts when the new contact matches the specified rule.

Choose New Contact Created when the workflow should begin after a new contact is created in BotSkyrik.

If you leave the Conditions area empty, the trigger does not require any additional contact-data condition.

If you only want certain newly created contacts to enter the workflow, add one or more conditions below the event.

For example, you could configure a condition using a System Field and require a particular value before allowing the workflow to start.

The screenshot above shows an example where the Full Name system field is checked using the contains operator.

The values shown in the screenshot are only an example. Configure the fields and conditions according to the journey you are building.

Choose Tag Added when the workflow should start after a particular tag is applied to a contact.

After selecting the event, BotSkyrik displays a Tag field. Choose the workspace tag you want this trigger to watch.

The workflow will then respond to that specific tag event rather than every tag change in the workspace.

Tag Removed works the same way, except the workflow begins when the selected tag is removed from the contact.

This makes the event itself very specific:

Tag Added → choose the tag

or

Tag Removed → choose the tag

You can still add conditions if the tag event should only start the workflow for contacts that meet additional criteria.

Choose Custom Field Changed when the workflow should begin after one of your workspace Custom Fields changes.

Once this event is selected, choose the specific Custom Field BotSkyrik should monitor.

For example, if your workspace contains fields for customer preferences, qualification information, status, or other business data, you can select the relevant field and use its change as the starting event.

The trigger watches the field you select; it does not automatically listen to every Custom Field.

If the field change alone is sufficient, no additional condition is required. If the workflow should only start for particular contacts or values, use the Conditions area to narrow the trigger further.

System Field Changed works similarly, but it watches one of BotSkyrik's built-in contact fields.

After selecting this event, choose the System Field you want to monitor.

The available System Fields are based on the workflow's selected channel and the contact information available in BotSkyrik.

For example, a workflow could monitor a supported identity or contact field and begin when that field changes.

As with Custom Fields, additional Conditions are optional.

The Conditions area lets you decide whether the selected Contact Data event is enough on its own or whether the contact must also match additional rules.

If you leave the list empty, there are no extra conditions.

Select Add Condition when you want to narrow the trigger.

A condition can evaluate information from sources such as:

System Fields — built-in contact information available in BotSkyrik.

Custom Fields — fields created for your workspace.

Tags — tags currently associated with the contact.

After selecting the source, choose the field or tag and then select the appropriate comparison rule.

For example, a System Field condition can be configured in a structure such as:

System Field → Full Name → contains → Noor

The screenshot above shows this exact configuration as an example.

The available operators can change depending on the type of field being evaluated. A text field, number field, boolean field, or tag does not necessarily require the same comparison options.

You can add more than one condition to the same Contact Data trigger.

When multiple conditions are present, BotSkyrik lets you choose whether the contact must:

Match ALL conditions — every configured rule must match.

or

Match ANY condition — matching one of the configured rules is enough.

This allows you to make a Contact Data trigger as broad or as specific as necessary.

For example, the event itself might be New Contact Created, while the conditions decide which newly created contacts should actually enter this particular workflow.

It helps to think of a Contact Data trigger in two parts.

The event answers:

What changed?

The conditions answer:

Should this particular contact enter the workflow?

For example:

New Contact Created
plus optional contact conditions.

Or:

Tag Added → Qualified Lead
plus any additional conditions you need.

Or:

Custom Field Changed → Project Status
plus an optional rule based on other contact data.

This keeps the trigger focused without requiring a separate workflow for every small variation.

Contact Data triggers can exist alongside the Message & Conversation triggers you configured earlier.

They are not a separate workflow.

For example, one workflow could have a message-based entry point and another Contact Data entry point, with either configured event able to start the same workflow.

The Configured Triggers screen keeps these entries grouped so you can clearly see which triggers belong to Message & Conversation, Contact Data, and the other available trigger families.

The third trigger group is Integration Events.

Integration Events allow a workflow to begin when something happens inside a connected external service rather than when a customer sends a message or contact data changes.

To configure one, return to All Triggers, select Add New Trigger, and choose Integration Event.

BotSkyrik will then ask you to choose the integration that should provide the event.

The available integrations can expand over time. The current configuration includes integrations such as Tally, Calendly, and Cal.com.

Start with the Integration dropdown.

Choose the external service that should start the workflow.

For services that require an existing connection, connect the provider from Integrations before attempting to use its workflow events.

For example, Calendly and Cal.com must already be connected before their booking events can be selected.

Once the provider is chosen, the remaining configuration adapts to that integration.

When you select Tally, the supported event is Form Submitted.

The Event field is therefore already set to:

Form Submitted

Next, use the Tally Form dropdown to choose the specific form that should start this workflow.

BotSkyrik loads the available forms from your connected Tally account, so you can select the actual form rather than manually entering an ID.

In the screenshot above, the selected form is:

AI Chatbot Budget Inquiry

This means submissions from that form can start the workflow.

When you select a Tally form, BotSkyrik prepares the connection automatically.

Once configuration is complete, the green Ready message confirms that BotSkyrik has prepared the form for workflow events.

The status shown in the screenshot means BotSkyrik has:

• added the required hidden contact identifier to the form

• registered the signed Tally submission webhook

You do not need to manually create the webhook for this workflow.

When the green Ready confirmation appears, the Tally trigger is prepared to receive submissions.

If preparation fails, BotSkyrik displays the error in the Trigger panel so you can correct the connection before publishing the workflow.

Once the trigger is active, a matching form submission becomes the event that starts the workflow.

The flow is essentially:

Customer submits selected Tally form → BotSkyrik receives the submission event → Workflow starts

This is different from a Message trigger because the customer does not need to send another DM after completing the form.

The external event itself becomes the workflow entry point.

If you choose Calendly, BotSkyrik lets you select the booking event that should start the workflow.

Calendly must first be connected in Integrations. If it is not connected, BotSkyrik will tell you to connect it before using Calendly events.

After choosing Calendly, select an event such as:

Booking Created

Booking Rescheduled

Booking Cancelled

Choose the event that represents the point where this workflow should begin.

For example, if you are creating a confirmation workflow, you might select Booking Created.

If the workflow should respond when an existing appointment changes, choose Booking Rescheduled.

A cancellation workflow can instead use Booking Cancelled.

After selecting the required booking event, BotSkyrik prepares the event connection.

When preparation is complete, the Trigger panel displays:

Ready — Calendly booking events are active.

If the provider is connected but the event has not yet been prepared, use the Prepare Calendly events option shown in the Trigger configuration.

Wait for the Ready confirmation before relying on the trigger in a published workflow.

Cal.com uses the same general booking-event model.

First select Cal.com as the integration, then choose the event that should start the workflow:

Booking Created

Booking Rescheduled

or

Booking Cancelled

Cal.com must already be connected in your BotSkyrik Integrations before these events can be used.

Cal.com also lets you control which booking type the trigger should listen to.

Under Booking Type, you can choose:

Any booking type

or select a specific booking type from your connected Cal.com account.

Use Any booking type when the workflow should start for every matching Cal.com booking event.

Choose a particular booking type when the workflow belongs to one specific appointment or service.

For example:

Booking Created → Consultation

would be more specific than listening to every booking created in the account.

After configuration is prepared successfully, BotSkyrik displays the Ready confirmation for Cal.com booking events.

Not every integration requires exactly the same configuration.

Tally needs a form.

Calendly needs a booking event.

Cal.com can use a booking event together with an optional booking-type filter.

This is why the Integration Event panel changes based on the provider you select.

Rather than expecting every integration to follow one fixed form, configure the fields that BotSkyrik displays for the selected provider.

As additional integrations and event types are introduced, they can follow the same pattern without changing the basic Trigger workflow.

Message & Conversation, Contact Data, and Integration Events are different ways of entering the same workflow.

You can configure more than one trigger when several events should lead into the same automation.

For example, a workflow might be able to start from a customer message as well as from an external form submission.

The Configured Triggers panel keeps each entry organized under its own group while all configured trigger entries ultimately lead into the same workflow.

Before moving on, return to Back to All Triggers and review the configured entries.

Check that:

• the correct channel is selected

• each required trigger appears under the correct group

• message keywords or AI Intention are configured where required

• Contact Data fields and conditions are correct

• Integration Events show the expected provider and event

• connected integrations display a Ready state where preparation is required

Any configured trigger can start the workflow, so each one should represent a deliberate entry point.

With the Trigger configuration complete, BotSkyrik now knows when the workflow should begin.

The next part of the workflow determines what happens after it starts.

From here, we can move into the Workflow Nodes and configure each building block individually, beginning with the Message Node.