> For the complete documentation index, see [llms.txt](https://academy.any2info.com/any2info-academy/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://academy.any2info.com/any2info-academy/no-code-platform/data-studio/data-hubs/toolbox/import-and-export/erp/export-to-afas-profit.md).

# Export to AFAS Profit

**Category:** ERP

**Version:** 1.0

**Last updated:** May 28, 2026

**Author:** Any2Info

***

### Description

The **Export To AFAS Profit** node allows you to send data from your data flow to AFAS Profit.\
It uses **Update Connectors** to create or update records within AFAS.

AFAS Profit uses **Update Connectors** to process incoming data.\
Within this node, you configure how your data is structured and sent to AFAS.

The process works as follows:

1. Select a valid **Connection** to AFAS Profit
2. Open **Advanced** and configure:
   * Select the entity (Update Connector)
   * Field mappings between your input data and AFAS fields
3. Execute the node to send the data to AFAS
4. AFAS processes the request and returns a response

***

### Configuration Options

| Setting       | Required | Description                                                                                                       |
| ------------- | -------- | ----------------------------------------------------------------------------------------------------------------- |
| Connection    | Yes      | Select the connection to your AFAS Profit environment.                                                            |
| Advanced      | Yes      | Opens the mapping configuration where you define how input data is mapped to the AFAS Update Connector structure. |
| JSON response | No       | When enabled, includes the full JSON response from AFAS in the output of the node.                                |

***

### AFAS Connectors

AFAS Profit works with two types of connectors:

\*\* Update Connectors \*\*

* Used to **create or update data** in AFAS Profit
* Can be configured in AFAS to include specific fields

\*\* Get Connectors \*\*

* Used to retrieve data from AFAS Profit
* Not used in this export node, but relevant for import scenarios

***

### JSON Response

When the **JSON response** option is enabled:

* The full response from AFAS is added to the output table
* This includes detailed information about the processed request
* Useful for retrieving:
  * Generated IDs
  * Results of nested (child) records

You can use a query node (SQLite with JSON functions) to extract values such as IDs from nested structures in the response.

***

### Tips & Best Practices

* Ensure the selected Update Connector is correctly configured in AFAS Profit
* Carefully map all required fields in the **Advanced** configuration
* Enable **JSON response** when you need to extract additional information from the response

***

### Changelog

| Version | Date         | Change                               |
| ------- | ------------ | ------------------------------------ |
| 1.0     | May 28, 2026 | Initial documentation version added. |


---

# 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://academy.any2info.com/any2info-academy/no-code-platform/data-studio/data-hubs/toolbox/import-and-export/erp/export-to-afas-profit.md?ask=<question>&goal=<user_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.