> For the complete documentation index, see [llms.txt](https://docs.docontrol.io/docontrol-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docontrol.io/docontrol-user-guide/workflows/define-workflow-settings/action-settings/utilities.md).
# Utilities
You can implement an outgoing action to send [HTTP requests](#http-request-action) or[ DoControl API ](/docontrol-user-guide/workflows/define-workflow-settings/action-settings/utilities/docontrol-api-action.md)commands to other systems.
You can send an HTTP request to another system, endpoint or service. Alternatively, DoControl provides predefined HTTP request actions for these specific apps:
* [Jira](/docontrol-user-guide/workflows/define-workflow-settings/action-settings/utilities/jira-actions.md) - Create issues in Jira
* [Datadog](/docontrol-user-guide/workflows/define-workflow-settings/action-settings/utilities/datadog-actions.md) - Create incidents or send logs to Datadog
* [VirusTotal](/docontrol-user-guide/workflows/define-workflow-settings/action-settings/utilities/virustotal-actions.md) - Check for malicious files or IP addresses in VirusTotal using your own VirusTotal enterprise plan (recommended) or the public API
{% hint style="info" %}
For best practices on adding API calls to workflows, see [DoControl videos](/docontrol-user-guide/help/videos.md#add-api-calls-to-workflows).
{% endhint %}
## HTTP request
You can send an HTTP request to another system, endpoint or service.
1. From the **Actions** left pane, select **Utilities > HTTP request.** Drag the action to the canvas, and connect it to the previous action.
2. Click the action to open its settings.
3. Complete the fields for the HTTP vanilla request.
{% hint style="info" %}
* You can click and use [dynamic fields](/docontrol-user-guide/workflows/define-workflow-settings/action-settings.md#dynamic-data) from the workflow, including adding an API key from the **Secret** tab as a header value.
* **Body**: you can enter the request in plain text or JSON format.
* **Timeout** (required): the maximum time for the workflow to wait for an HTTP response from the server. Default timeout is 30 seconds, maximum is 60 seconds.
{% endhint %}
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.docontrol.io/docontrol-user-guide/workflows/define-workflow-settings/action-settings/utilities.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
