> For the complete documentation index, see [llms.txt](https://docs.rampwin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rampwin.com/automation-workflow/technical.md).

# Technical

**Call REST API**: Integrate with external systems by calling REST APIs. Likewise sending information to the Rest API using the Push To CRM action type, you can also call/add the API of a 3rd party software or platform when needed using the automation for the particular Trigger.

<figure><img src="/files/DPHPArGECko8yqXnr6Ow" alt=""><figcaption></figcaption></figure>

Then, according to your requirements and the platform's compatibility, add the REST API details. For instance,

* Type for URL as POST, GET, PUT, and DELETE.
* Input Header Key(s) and Value(s).
* Select Data Type as URL Encoded, JSON, or FORM.
* Then, add the JSON Data using the parameter fields, and once done, click **Add**.

**Eval**: Execute custom scripts or code snippets for advanced processing.

<figure><img src="/files/hggRfgjSUjxUDGmDPuUN" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.rampwin.com/automation-workflow/technical.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.