Custom events are events that you define.
They are used to handle things that happen
outside the conversation with the end-user.
For example,
the end-user clicked a button,
a certain amount of time has passed,
available inventory has changed during the conversation,
and so on.

You can invoke these events using either
[fulfillment](https://docs.cloud.google.com/dialogflow/docs/fulfillment-overview)
or
[the API](https://docs.cloud.google.com/dialogflow/docs/api-overview).

## Invoke events with the API

The request for a
[`Sessions`](https://docs.cloud.google.com/dialogflow/docs/reference/common-types#sessions)
type `detectIntent` call contains a `queryInput.event` field,
which is used to invoke events.
The type of this field is a `EventInput`,
and it contains fields for the event name,
[optional parameters](https://docs.cloud.google.com/dialogflow/docs/events-overview#param),
and the language code.

When you provide an event to a detect intent call,
you do not provide other data, like an end-user expression.
The call's sole purpose is to invoke an event and trigger an intent.

## Invoke events with fulfillment

You can invoke events via
[fulfillment](https://docs.cloud.google.com/dialogflow/docs/fulfillment-overview)
by setting the `followupEventInput` field of the
[`WebhookResponse`](https://docs.cloud.google.com/dialogflow/docs/reference/common-types#webhookresponse).
You can optionally set the `followupEventInput.parameters` field to provide
[parameters](https://docs.cloud.google.com/dialogflow/docs/events-overview#param)
to the intent.

For example:

    {
      "followupEventInput": {
        "name": "event-name",
        "parameters": {
          "parameter-name-1": "parameter-value-1",
          "parameter-name-2": "parameter-value-2"
        },
        "languageCode": "en-US"
      }
    }

When the `followupEventInput` parameter is set for a `WebhookResponse`,
Dialogflow ignores the `fulfillmentText`, `fulfillmentMessages`,
and `payload` fields.
In addition, the `followupEventInput.languageCode` field is a required field,
but Dialogflow ignores this field,
because the language was already defined
in the originating detect intent request.

When Dialogflow receives a webhook response that includes an event,
it immediately triggers the corresponding intent in which it was
[defined](https://docs.cloud.google.com/dialogflow/docs/events-overview#config).

The following flow describes the steps:

1. The end-user types or speaks an expression.
2. Dialogflow matches the end-user expression to **Intent-1**, which is configured for fulfillment.
3. Dialogflow sends a webhook request to your server.
4. Your server responds with a webhook response that includes a followup event.
5. Instead of responding to the user for the **Intent-1** match, Dialogflow triggers **Intent-2**, which is configured for the event.
6. Dialogflow proceeds as though the end-user initiated the match for **Intent-2** and handles required parameters and fulfillment as dictated by the configuration of **Intent-2**.

## Chaining intent matches with webhook response events

It is possible to chain intent matches with webhook response events.
In the flow described above,
**Intent-2** could also be configured for fulfillment.
If your server's webhook response supplies another event,
Dialogflow proceeds to match **Intent-3** (configured for the event)
without responding to the end-user for **Intent-2**.

Dialogflow does not respond to the end-user until the chain has ended.
When chaining intents in such a way,
each webhook response must be sent within
[timeout restrictions](https://docs.cloud.google.com/dialogflow/docs/fulfillment-how#webhook_response).

> [!NOTE]
> **Note:** You can chain *at most* 3 intent matches in this way.