HTTP Provider

​

In workflows

This provider can be used in workflows.

As “step” to query data, example:

steps:
    - name: Query http
      provider: http
      config: "{{ provider.my_provider_name }}"
      with:
        url: {value}  
        method: {value}  
        headers: {value}  
        body: {value}  
        params: {value}  
        proxies: {value}  
        fail_on_error: {value}  
        verify: {value}  

As “action” to make changes or update data, example:

actions:
    - name: Query http
      provider: http
      config: "{{ provider.my_provider_name }}"
      with:
        url: {value}  
        method: {value}  
        headers: {value}  
        body: {value}  
        params: {value}  
        proxies: {value}  
        verify: {value}  

Check the following workflow examples:

• create-new-incident-grafana-incident.yaml
• db_disk_space_monitor.yml
• http_enrich.yml
• ifelse.yml
• incident-enrich.yaml
• permissions_example.yml
• send-message-telegram-with-htmlmd.yaml
• simple_http_request_ntfy.yml
• slack-workflow-trigger.yml
• telegram_basic.yml
• update-incident-grafana-incident.yaml
• update_workflows_from_http.yml
• webhook_example_foreach.yml

​

Connecting with the Provider

To connect to the provider, you can instantiate an instance of the HttpProvider class, providing a provider_id and a ProviderConfig object. Then you can call the query method to query the HTTP endpoint.

​

Notes

The code logs some debug information about the requests being sent, including the request headers, body, and query parameters. This information should not contain sensitive information, but it’s important to make sure of that before using this provider in production.

​

Useful Links

• requests library documentation