Skip to content

Commit 7464f50

Browse files
Improve titles
1 parent 4515a85 commit 7464f50

File tree

1 file changed

+8
-12
lines changed
  • docs/actions-and-automations/setup-backend/webhook/port-execution-agent

1 file changed

+8
-12
lines changed

docs/actions-and-automations/setup-backend/webhook/port-execution-agent/usage.md

Lines changed: 8 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -4,13 +4,7 @@ sidebar_position: 2
44

55
# Usage
66

7-
When using the execution agent, in the `url` field you need to provide a URL to a service (for example, a REST API) that will accept the invocation event.
8-
9-
- The service can be a private service running inside your private network;
10-
- Or, it can be a public accessible service from the public internet (**note** in this scenario, the execution agent needs corresponding outbound network rules that will allow it to contact the public service).
11-
12-
:::note
13-
**IMPORTANT**: To make use of the **Port execution agent**, you need to configure:
7+
To make use of the **Port execution agent**, you need to configure:
148

159
<!-- TODO: add back the URLs here for changelog destination -->
1610

@@ -22,15 +16,17 @@ For example:
2216
```json showLineNumbers
2317
{ "type": "WEBHOOK", "agent": true, "url": "URL_TO_API_INSIDE_YOUR_NETWORK" }
2418
```
25-
:::
2619

27-
Well Done! **Port Agent** is now running in your environment and will trigger any webhook that you've configured (for self-service actions, or changes in the software catalog).
20+
When using the execution agent, in the `url` field you need to provide a URL to a service (for example, a REST API) that will accept the invocation event.
21+
22+
- The service can be a private service running inside your private network;
23+
- Or, it can be a public accessible service from the public internet (**note** in this scenario, the execution agent needs corresponding outbound network rules that will allow it to contact the public service).
2824

29-
When a new invocation is detected, the agent will pull it from your Kafka topic and forward it to the internal API in your private network.
25+
Once configured, the Port Agent will run in your environment and trigger webhooks for self-service actions or software catalog changes.
3026

31-
![Port Execution Agent Logs](/img/self-service-actions/port-execution-agent/portAgentLogs.png)
27+
When a new invocation is detected, the agent pulls it from your Kafka topic and forwards it to the internal API in your private network.
3228

33-
## Configuration
29+
![Port Execution Agent Logs](/img/self-service-actions/port-execution-agent/portAgentLogs.png)
3430

3531
:::info Advanced configuration
3632
For a complete list of all available configuration parameters and their descriptions, see the [Port Agent Helm chart README](https://github.com/port-labs/helm-charts/tree/main/charts/port-agent).

0 commit comments

Comments
 (0)