> ## 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.

# Triggering a Webhook

> How to use Webhooks with Zapier, Pabbly Connect, Make, or any other automation platform

export const GridImage = ({window, src, preview = false, img_width = 200, height = 300}) => {
  var host = preview ? '' : 'https://mintlify.s3-us-west-1.amazonaws.com/packages';
  return <div className="grid-image-bg mt-3 mb-3 flex align-items-center" style={{
    alignItems: 'center',
    justifyContent: 'center',
    position: 'relative',
    height,
    width: '100%'
  }}>

    <img src={`${host}${src}`} className={'m-0'} width={img_width} style={{
    zIndex: 2,
    width: '100%',
    maxWidth: img_width,
    border: '1px solid #ccc',
    borderRadius: 5,
    boxShadow: '5px 5px rgba(0,0,0,0.25);'
  }} />

    <div style={{
    transform: 'translateX(-50%)',
    left: '50%',
    top: 0,
    position: 'absolute',
    height: '100%',
    width: '100%',
    zIndex: 0,
    overflow: 'hidden',
    pointerEvents: 'none'
  }}>
      <img src={`${host}/images/grid-bg-trans.png`} className="m-0" />
    </div>
  </div>;
};

A Packages Webhook is just a URL that you can hit to start a package run.

That means you can start a package run just by visiting a URL in your browser — or by using an automation platform like Zapier, Pabbly Connect, or Make.

## Steps to trigger a Webhook

<Steps>
  <Step title="Head to the &#x22;Webhooks&#x22; page for the applicable package">
    Find the three dots next to the package you want to create a trigger for and click on "Webhooks".

    <GridImage src="/images/click_webhooks.png" img_width={200} />

    <div style={{fontSize: 12}}>You can find this on the <a href="https://packagesss.com/home/packages" target="_blank">packages page</a>.</div>
  </Step>

  <Step title="Copy the Webhook URL">
    Click the clipboard icon to copy the webhook URL.

    <GridImage src="/images/run-url.png" img_width={500} height={300} />
  </Step>

  <Step title="Paste it as a step into your Automation Platform">
    Some platforms call it webhooks, while others refer to it as an API call. Whatever the case, you'll need to paste the URL you copied in the previous step.

    All Packages webhooks start with the <code>run.packages.ai</code> domain.

    <GridImage src="/images/api-endpoint-pabbly.png" img_width={500} height={500} />

    <div style={{fontSize: 12}}>In this example were using Pabbly Connect.</div>
  </Step>

  <Step title="Add Parameters if Needed">
    Automation platforms like Zapier allow you to add "parameters" to your webhook. This can be useful if you need to pass data to your package.

    "Parameters" would essentially be the "inputs" of your package.

    <GridImage src="/images/api-parameters-2.png" img_width={600} height={300} />

    It is important to note that for the parameter label/name — you do not pass the human-readable name of the input like <code>Month</code> or <code>Year</code>. Instead, you pass the id of the input, i.e. <code>YrXrRtyG2-7C5REOMwidVUOKb</code>.

    This is done to prevent input name changes from breaking your webhooks.
  </Step>

  <Step title="Run the workflow">
    Wait for the workflow to run and check Packages to see if the webhook/run was triggered successfully.
  </Step>

  <Step title="Your webhook should have triggered a package run!">
    You did it! 🎉 your webhook works and you can repeat the process for other packages.
  </Step>
</Steps>

## Videos of the trigger process

Are you more of a visual learner? Check out our videos on how to trigger a Packages Webhook in other platforms.

### Trigger in Pabbly Connect

### Trigger in Zapier

### Trigger in Make