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

# Overview

> What is a Packages Webhook?

Webhooks in Packages allow you to start a package run outside of Packages. This means you can do things like:

* Start a package run at the begin, middle or end of a Zapier, Pabbly Connect, or Make workflow. *(works with all automation platforms.)*
* Start a package run within an application.
* ... and lots of other possibilities!

Packages Webhooks are just URLs, so anywhere you can visit a URL, you can trigger a package run.

In this part of the documentation we'll go over how to create a webhook, and then how to trigger it.

## Creating a Webhook

<CardGroup cols={2}>
  <Card title="Creating a Webhook" icon="plus" href="/webhooks/create">
    Create your first webhook in Packages
  </Card>
</CardGroup>

## Triggering a Webhook

<CardGroup cols={2}>
  <Card title="Trigger a Webhook outside of Packages" icon="repeat" href="/webhooks/trigger">
    Using Webhooks with Zapier, Pabbly Connect, Make, or any other automation platform
  </Card>
</CardGroup>

## Frequently Asked Questions

<AccordionGroup>
  <Accordion title="What are the costs associated with webhooks?">
    A webhook run has consumes the same number of credits as a normal package run.
  </Accordion>

  <Accordion title="What automation platforms do Packages Webhooks work with?">
    Our webhooks work with all the major automation platforms like Zapier, Pabbly Connect, Make, Albato and more.

    Some platforms refer to webhooks as "webhooks" and others as "API".
  </Accordion>
</AccordionGroup>