> For the complete documentation index, see [llms.txt](https://docs.novacura.com/flow-connect/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.novacura.com/flow-connect/working-with-connect/create-and-design/automations/executing-automations-externally/ifs-cloud.md).
# IFS Cloud
{% hint style="info" %}
Documentation covers IFS Cloud version 24R2
{% endhint %}
This page will describe the nuances of configuring different parts of IFS Cloud to execute Automations within your Flow Connect environment.\
\
This guide will provide an example for:
* Custom Event Actions (REST)
* Work Flows
## IFS Custom Event Action
To execute an automation, you must adhere to some specific requirements within IFS's Event Action screen.
1. The REST Endpoint must contain the Automation HTTP endpoint provided within the Automation configuration screen.
2. The Method should be "POST"
3. The Sender must be a configured REST Sender in IFS. (Default shown)
4. The Body must contain a JSON structure of any values you wish to send to your Automation. (Example provided below)
5. The Authentication must be "None".
6. Additional headers must be provided and are mandatory for Automations to execute:
1. x-api-key:``
2. Accept:`*/*`
```
//Example Header Value
//You must separate the header name and value with a colon.
//Any additional headers need to be separated with a comma.
//eg: "x-api-key" and "Accept" would be:
x-api-key:,Accept:*/*
```
```json
//Example of a Body you can use to send the customer Id and Name to the Automation
//Note: The available IFS values are provided in the event page.
{
"CustomerId":"&OLD:CustomerId",
"name":"&NEW:NAME"
}
```
{% hint style="warning" %}
The IFS Additional Header parameter field accepts multiple headers separated by a comma.
{% endhint %}
{% hint style="success" %}
You can now successfully trigger an automation directly from IFS Custom Events.
{% endhint %}
## IFS Workflow Designer
To Execute an automation from an IFS Workflow you can simply define the required headers as follows:
1. Define the Authentication Type as "None"
2. Set The URL to an Automation webhook
3. Set the desired Method (POST)
4. Add the required headers:
1. x-api-key: Automation access key
2. Accept: Default is `*/*` or `application/json`
3. Content-Type: `application/json` or `application/xml` depending on body format
5. Define any required Body, in this example, JSON format.
{% hint style="success" %}
You can now successfully trigger an automation directly from IFS workflows.
{% 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 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.novacura.com/flow-connect/working-with-connect/create-and-design/automations/executing-automations-externally/ifs-cloud.md?ask=&goal=
```
`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.