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

# Event Actions

> Checkout event action references and delivery configuration.

Event Actions sends checkout lifecycle events to external systems, currently through webhook actions.

<Info>
  Find this module in **Shopify Stores** > **Edit Checkout** > **Integrations**.
</Info>

## How it works

Use this module for custom client webhooks. Marketing integrations such as Omnisend should be configured in Marketing Integrations.

## Settings reference

<AccordionGroup>
  <Accordion title="Configured event actions">
    **You will set:** Action list

    The list of active checkout event actions for the store.
  </Accordion>

  <Accordion title="Checkout event">
    **You will set:** Event selector

    The customer or checkout lifecycle moment that triggers the action, such as page load, email filled, phone filled, payment button click, cart abandoned, payment success, or order complete.
  </Accordion>

  <Accordion title="Action type">
    **You will set:** Action selector

    What Paysight should do when the event fires. Customer-facing setup currently supports webhooks.
  </Accordion>

  <Accordion title="Webhook URL">
    **You will set:** URL field

    The endpoint Paysight should call when the selected event fires.
  </Accordion>

  <Accordion title="Headers JSON">
    **You will set:** JSON text field

    Optional request headers for the webhook, such as authentication headers.
  </Accordion>

  <Accordion title="Event ID">
    **You will set:** Read-only value

    Reference ID for an existing configured action. This is shown for support and troubleshooting.
  </Accordion>
</AccordionGroup>

## Examples

<Tabs>
  <Tab title="Order-complete webhook">
    Create an action for order complete with the client webhook URL and required authentication headers.
  </Tab>

  <Tab title="Abandoned cart webhook">
    Create an action for cart abandoned when the client owns a custom abandonment flow.
  </Tab>

  <Tab title="Authenticated webhook">
    Add headers JSON when the receiving system requires a token or API key.
  </Tab>
</Tabs>

## Before saving

* Validate the webhook URL and headers JSON.
* Do not duplicate Omnisend mappings managed in Marketing Integrations.
* Test the receiving endpoint with a checkout event before launch.

## Related modules

<CardGroup cols={2}>
  <Card title="Marketing Integrations" icon="arrow-right" href="/guides/shopify-store-editor/marketing-integrations">
    Connect checkout events to Omnisend automations.
  </Card>

  <Card title="Pixels" icon="arrow-right" href="/guides/shopify-store-editor/pixels">
    Manage conversion pixels, URL matching, default behavior, and event filters.
  </Card>

  <Card title="Store Operations" icon="arrow-right" href="/guides/shopify-store-editor/store-operations">
    Control Shopify order sync and batching behavior.
  </Card>
</CardGroup>