# Import vPlan

**Category:** ERP

**Version:** 1.0

**Last updated:** November 5, 2025

**Author:** Any2Info

***

### Description

The **Import vPlan Node** provides a user-friendly integration with the vPlan API directly inside the Any2Info DataHub.

It allows retrieving entities such as orders, collections, projects, and activities.

The node communicates with all available **vPlan API endpoints**, including orders, activities, boards, resources, and custom entities.

The integration is actively maintained to ensure full compatibility with the latest API versions and features released by vPlan.

***

### Property Options

| Setting              | Type    | Required | Description                                                                              |
| -------------------- | ------- | -------- | ---------------------------------------------------------------------------------------- |
| **Connection**       | Select  | Yes      | Select the vPlan connector containing your API key or OAuth token.                       |
| **Advanced**         | Button  | Yes      | Opens the configuration window to select entities, fields, filters, and output behavior. |
| **Entity library**   | Select  | Yes      | Defines which version of the entity model to use (e.g., *Legacy* or *Latest*).           |
| **Page Size**        | Numeric | No       | Number of records to fetch per request (default: 1000).                                  |
| **Include Archived** | Boolean | No       | When enabled, archived entities are also retrieved.                                      |

***

### Configuration Options

| Setting     | Type        | Required | Description                                                                                            |
| ----------- | ----------- | -------- | ------------------------------------------------------------------------------------------------------ |
| **Entity**  | Select      | Yes      | Defines which vPlan entity to import (e.g., *Order*, *Activity*, *Collection*, *Project*, *Resource*). |
| **Columns** | Select      | Yes      | Defines the selected columns to import for the chosen entity.                                          |
| **Filter**  | Filter icon | No       | Opens the filter dialog for column-based filtering. Filters appear in the Filters tab.                 |

***

#### Filtering

Filtering allows you to narrow down the data returned by the **Import vPlan Node**.

Each filter consists of:

| Field         | Description                                                                                 |
| ------------- | ------------------------------------------------------------------------------------------- |
| **Target**    | Field or column to filter on.                                                               |
| **Condition** | Comparison operator (e.g., *Equals*, *Not Equals*, *Contains*, *Starts With*, *Ends With*). |
| **Value**     | The value used in the comparison. Supports static values and expressions.                   |

Example:

```
Target: board_id
Condition: Equals
Value: aa6fb2a3-bfd5-4aef-b423-5c73f5e2b0cd

```

Multiple filters can be combined.

***

### Execution Flow

Typical usage:

* A **Daily Trigger** activates the flow.
* The **Import from vPlan Node** retrieves selected vPlan entities.
* A **Query** node filters or transforms data.
* The processed data is sent to downstream systems (e.g., ERP, Exact).

<figure><img src="/files/5FEjUnwGOkR38bkeqsvB" alt=""><figcaption></figcaption></figure>

***

### Input / Output

| Direction  | Type  | Description                                                          |
| ---------- | ----- | -------------------------------------------------------------------- |
| **Input**  | Table | Used only when executing dynamically (e.g., for-each-row filtering). |
| **Output** | Table | Returns retrieved vPlan entities and column values.                  |

***

### Tips & Best Practices

* Use filters to limit dataset size and improve performance.
* Enable **Include Archived** only when historical data is required.
* Combine with a **Query** or **Transform** node for enrichment or restructuring.
* Keep Page Size high (e.g., 1000) to minimize API requests for large imports.

***

### Errors & Troubleshooting

| Error Message           | Meaning                                | Solution                                 |
| ----------------------- | -------------------------------------- | ---------------------------------------- |
| **401 Unauthorized**    | Invalid API credentials.               | Check the vPlan connector configuration. |
| **404 Not Found**       | Selected entity does not exist.        | Verify entity name and library version.  |
| **400 Bad Request**     | Invalid request parameters or filters. | Validate fields and filter values.       |
| **Rate Limit Exceeded** | Too many API calls.                    | Reduce Page Size or throttle requests.   |

***

### Changelog

| Version | Date              | Change                               |
| ------- | ----------------- | ------------------------------------ |
| **1.0** | November 19, 2025 | Initial documentation version added. |


---

# Agent Instructions: 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://academy.any2info.com/any2info-academy/no-code-platform/data-studio/data-hubs/toolbox/import-and-export/erp/import-vplan.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.