# Using the ion-webhooks Component

The `ion-webhooks` component requires you to configure 3 settings:

1. Connection
2. Webhook Receiver Name
3. Actions

## Connection

This configuration setting determines the connection that the flow will use to connect to ION. Refer to this [page](https://manual.firstresonance.io/api/api-keys) on how to retrieve api keys. New connections can be added and previously saved connections are available to select. 

<figure><img src="https://3615148728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LkRqYp6lJhwxjYdzYG8%2Fuploads%2FdZG0GiHRbAr9CegrCKMq%2Fimage.png?alt=media&#x26;token=cd15399f-bd25-4bad-ba1a-4cd5871ce8b9" alt=""><figcaption></figcaption></figure>

## Webhook Receiver Name

This component will setup a webhook receiver in ION and the name is used to identify the receiver. You may provide any name but using the same name as the flow is a good practice to follow.

## Actions

You can configure the ion-webhooks component to be triggered from one or more action. An action consists of a resource (Issues, Parts, Procedures, Runs, etc) and the event type (create, update, delete).&#x20;

For example, if you want the flow to be triggered whenever a purchase order line is create or updated you would add the following actions to the configuration:

<figure><img src="https://3615148728-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LkRqYp6lJhwxjYdzYG8%2Fuploads%2Fho36Ug7bF0P8VpJNXlOs%2Fimage.png?alt=media&#x26;token=f59b71bf-15f7-498f-8fe4-ff8f53bbd427" alt=""><figcaption></figcaption></figure>