> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dialogshift.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Make.com: Incoming trigger

> A Make.com scenario starts a Journey Messaging flow — optionally filtered by a specific booking ID

With the incoming trigger, a Make.com scenario starts a Journey Messaging flow inside DialogShift. This lets you send messages based on any external event — for example when a payment provider has processed a payment, or when a third-party system fires an event.

<Info>
  This guide assumes that you have [already set up the Make.com integration](/en/journey-messaging/make-com-setup) and that the connection between Make.com and DialogShift is in place.
</Info>

## Example scenario

In this guide we will build the following use case:

> As soon as a payment provider has processed a guest's payment, the guest should receive a confirmation message.

We will focus on the DialogShift side and assume that the rest of the Make scenario (e.g. the webhook from the payment provider) already exists.

## Step 1 — Create the external flow trigger in Journey Messaging

<Steps>
  <Step title="Pick or create a flow">
    Create a new flow or pick an existing one that should be started from Make.com.
  </Step>

  <Step title="Add an external flow trigger">
    At the top of the flow, on the trigger, choose **Add new external flow trigger**.
  </Step>

  <Step title="Name the trigger">
    Give the flow trigger a meaningful name — this name will later show up in Make.com. For our example: `Make: payment data processed`.
  </Step>

  <Step title="Configure actions and save the flow">
    Add the desired actions to the flow (e.g. sending a template) and save it.
  </Step>
</Steps>

The finished flow looks like this:

<img src="https://mintcdn.com/dialogshift/T5lDCwyF1LJDpXmK/images/make/ext_trigger_set.png?fit=max&auto=format&n=T5lDCwyF1LJDpXmK&q=85&s=4745f3c3bff4e354db3fb5e901742962" alt="External flow trigger in the flow editor, marked with EXT" width="1024" height="500" data-path="images/make/ext_trigger_set.png" />

The external trigger is marked with **EXT** in the flow editor. This flow runs as soon as Make.com sends the corresponding event.

<Tip>
  The same external trigger can be used for **multiple flows** — handy if a single Make scenario should start several JM flows at the same time. Just pick an existing external trigger when adding it.
</Tip>

## Step 2 — Send the trigger from Make.com

<Steps>
  <Step title="Create or open a scenario">
    Create a new scenario in Make.com or open the one that should trigger the DialogShift flow.
  </Step>

  <Step title="Add the DialogShift module">
    Click **+**, search for **DialogShift** and select the app.
  </Step>

  <Step title="Pick the action">
    Pick the action **Start DS Flow**.

    <Tip>
      If the connection to DialogShift does not yet exist, you can create it right here. Find the instructions in [Set up the Make.com integration](/en/journey-messaging/make-com-setup#step-3-—-create-a-connection-inside-make-com).
    </Tip>
  </Step>

  <Step title="Pick the flow trigger">
    Under **DS FlowTrigger** you will see all triggers you created in the flow editor — including `Make: payment data processed`.
  </Step>

  <Step title="Provide the booking ID">
    In the field **Booking ID of guest** enter the full booking ID. The flow will then start exclusively for the journeys that belong to this booking.

    <Warning>
      The booking ID is critical: it is the only way for Journey Messaging to know which journeys the instruction applies to.
    </Warning>

    In our example the booking data comes from the payment provider's webhook — we can reference the booking number from there with a single click. With a different data source you can of course populate the booking number in any other way.

    <img src="https://mintcdn.com/dialogshift/T5lDCwyF1LJDpXmK/images/make/start_flow.png?fit=max&auto=format&n=T5lDCwyF1LJDpXmK&q=85&s=b90942d3b4d0057ed8051a6ee8f11439" alt="Start DS Flow module in Make.com with the chosen flow trigger and booking ID" width="1024" height="693" data-path="images/make/start_flow.png" />
  </Step>

  <Step title="Save">
    Save the module — and you are done. As soon as the module is executed inside the Make scenario, the Journey flow will run.
  </Step>
</Steps>

## Advanced: Start a flow without a booking ID

In specific situations — e.g. a promotional message to all currently checked-in guests — you may want to start the flow for many bookings at once.

Without a booking ID, the module fails by default (visible in the Make scenario editor). You can instead start the flow for **all currently checked-in guests**:

<Steps>
  <Step title="Leave the booking ID empty">
    Leave the **Booking ID of guest** field blank.
  </Step>

  <Step title="Open Advanced settings">
    Expand the **Advanced settings** section in the module configuration.
  </Step>

  <Step title="Enable Trigger for all checked-in guests">
    Activate the option **Trigger for all checked-in guests**.
  </Step>
</Steps>

<Warning>
  "All checked-in guests" can potentially be a lot of guests — and that means a lot of messages. That is why this option must be enabled deliberately via the advanced settings. The booking-ID filter and the "all checked-in guests" option **cannot be combined**.
</Warning>

<Note>
  Because of delays in the Make scheduler, the filter cannot always be perfectly accurate: the check-in status is determined based on the moment the action runs.
</Note>

## Troubleshooting

<AccordionGroup>
  <Accordion title="The flow does not start">
    Checklist:

    * Is the flow **activated** in Journey Messaging?
    * Is the **API key** in the JM settings still valid?
    * Is the **booking ID** transmitted correctly from Make.com? (Visible in the Make scenario editor.)
    * Does the selected **DS FlowTrigger** match the external flow trigger in your DialogShift flow?
  </Accordion>

  <Accordion title="Error: booking ID is missing">
    Without a booking ID, the flow does not run by default. Either fill in the booking ID or deliberately enable **Trigger for all checked-in guests** in the Advanced settings — see the section above.
  </Accordion>
</AccordionGroup>