> 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/import-from-afas-profit.md).

# Import from AFAS Profit

**Category:** ERP

**Version:** 1.0

**Last updated:** May 28, 2026

**Author:** Any2Info

***

### Description

The **Import From AFAS Profit** node allows you to retrieve data from AFAS Profit into your data flow.\
It uses AFAS Get Connectors to access data entities.

AFAS Profit exposes data through **Connectors**. Within this node, you configure which data you want to retrieve via the Advanced settings.

The process works as follows:

1. Select a valid **Connection** to AFAS Profit
2. Open **Advanced** and choose:
   * The entity (Get Connector)
   * The fields (columns) you want to retrieve
3. Optionally configure the **Page Size**
4. The node retrieves the data and outputs it into your flow

***

### Configuration Options

| Setting    | Required | Description                                                                                                                 |
| ---------- | -------- | --------------------------------------------------------------------------------------------------------------------------- |
| Connection | Yes      | Select the connection to your AFAS Profit environment.                                                                      |
| Advanced   | Yes      | Opens a configuration screen where you select the **Get Connector (entity)** and the fields (columns) you want to retrieve. |
| Page Size  | No       | Defines how many records are retrieved per request.                                                                         |

***

### AFAS Connectors

AFAS Profit works with two types of connectors:

\*\* Get Connectors \*\*

* Used to **retrieve data** from AFAS Profit
* Expose predefined datasets (entities) such as employees, invoices, or projects
* Can be configured in AFAS to include specific fields

\*\* Update Connectors \*\*

* Used to **create or update data** in AFAS Profit
* Not used in the Import From AFAS Profit node, but relevant for export or update scenarios

***

### Tips & Best Practices

* Available connectors and fields depend on your AFAS Profit configuration
* Access rights in AFAS determine which data can be retrieved
* Only select the fields you actually need in the **Advanced** configuration
* Use a reasonable **Page Size** to balance performance and memory usage
* Ensure the selected Get Connector is properly configured in AFAS Profit

### 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/import-from-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.