> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/connectors/areas/business-systems/infor-m3/infor-m3-rest/configuring-infor-m3-rest-connector.md).

# Configuring Infor M3 REST connector

* In the **Novacura Flow Studio**, under the **Environment** tab, you will find **Connectors**. Click on it and press **Add** to create a new record. 

<figure><img src="/files/a8b2gXGSXE6kzUdZ9tUe" alt=""><figcaption><p>Adding a new connector</p></figcaption></figure>

* Provide a **Name** and choose the **Infor M3 REST API** from the **Type** drop-down. Drill down the **Configuration** and provide the API Endpoint **URL** as well as tenant/M3 in **Additional Path** to indicate the Infor M3 CloudSuite environment. \
  Example: \
  URL: <https://mingle-ionapi.eu1.inforcloudsuite.com\\>
  Additional Path: Tenantexample\_TST/M3
* Define **Force style for errors**. The default option will be Empty Record. By setting **Force style for errors**, you can dictate how an error response from Infor M3 REST should be interpreted in Flow.

  * Empty Record - Flow will return an empty record in case of an error message returned from Infor M3.&#x20;
  * Nil Record - Flow will return a Nil record in case of an error message returned from Infor M3.

  <figure><img src="/files/O1glFTqh3dvKkx7eijAQ" alt="" width="557"><figcaption><p>Connector Settings</p></figcaption></figure>

{% hint style="info" %}
**Force style for errors** option is only available starting from Flow Studio version [6.15.10](/release-information/flow/6.15/studio/6.15.10.md) & Flow service pack [6.15.12](/release-information/flow/6.15/server/6.15.12.md)
{% endhint %}

* Click on **Setup auth**. Tick on **Use OAuth2** and **Load from ionapi-file** to fetch all the editable credentials automatically via the downloaded file. Repeat the same procedure on **Runtime** tab.

<figure><img src="/files/3ZGlEBkJoCfe0OFjyCW7" alt=""><figcaption><p>Edditing Token details</p></figcaption></figure>

* Under **Advanced** tab, specify if the invoked API will be personal. In other words, you can either create a Novacura Flow User Id as M3 User ID or assign a property to a Novacura Flow User Id which value will correspond to a M3 User Id.\
  \
  That function only works when either '**GRID-Administrator**' or '**GRID-RunAsM3User**' IFS (Infor Federation Services) Security Role is assigned to a M3 User ID used as Service Account!

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

* After the credentials are successfully imported, click **Save** and then **Save** again on the Connector to save the changes. You should be able now to use the connector!&#x20;


---

# 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:

```
GET https://help.novacuraflow.com/connectors/areas/business-systems/infor-m3/infor-m3-rest/configuring-infor-m3-rest-connector.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.