Export vPlan node
Category: Node
Version: 1.0
Last updated: November 5, 2025
Author: Any2Info
Description
The Export vPlan Node provides a direct and user-friendly way to send data from the Any2Info DataHub to the vPlan API.
It connects to all available vPlan API endpoints, including orders, activities, boards, resources, statuses, and custom entities.
This makes it possible to create, update, or delete almost any type of data stored in vPlan directly from within the Any2Info DataHub.
The node is continuously maintained to ensure compatibility with new and updated vPlan API endpoints.
Whenever vPlan releases new functionality, the Any2Info integration is reviewed and updated accordingly.
Property Options
Connection
Select
No
(Optional) Select an existing connector, such as an OAuth 2.0 or API key-based connection.
Advanced
Button
Yes
Opens the configuration window for entity mappings, operations, fields, and output behavior.
Entity library
Select
Yes
Defines which version of the entity model to use (e.g., Legacy or Latest).
Preload Entities
Checkbox
No
Preloads the list of vPlan entities to improve configuration performance. Recommended for large environments.
Update Policy
Select
No
Defines how updates are applied. The available option is "Full or Changes Only", which determines whether the node sends the entire payload or only changed fields.
Configuration Options
Entity
Select
Selects the vPlan entity type to export, such as Card, Order, Collection, Project, Activity, or Resource.
Operation
Select
Defines the export action, such as Create, Update, Update or Create, or Delete, depending on the selected entity.
Output
Tab
Displays the API response after the export operation. Useful for debugging and retrieving new IDs.
Column Mapping
Table
Maps incoming DataHub fields to the corresponding vPlan API fields required for the selected entity and operation.
Supported Operations
Create
Creates a new record in vPlan.
Update
Updates an existing record using its id or external_ref.
Update or Create
Updates a record if it exists; otherwise creates it automatically.
Delete
Deletes an existing entity in vPlan.
Tips & Best Practices
Validate incoming data (e.g., date formats, required fields) using a Query node before exporting.
Use Update or Create for system synchronizations to ensure stable incremental updates.
Keep
external_refstable and unique — this is the most reliable identifier for linking systems.Filter out unchanged or duplicate data before exporting to prevent unnecessary updates.
When exporting large datasets, use batching or delays to prevent vPlan rate limits.
When using Update Policy, prefer Changes Only to minimize payload size and avoid overwriting unchanged fields.
Errors & Troubleshooting
401 Unauthorized
Invalid or expired API key.
Verify your connection configuration.
404 Not Found
The specified entity or endpoint does not exist.
Check the entity name and library version.
400 Bad Request
Invalid request payload or missing fields.
Validate mappings and required fields.
Rate Limit Exceeded
Too many API requests.
Batch your export or reduce frequency.
Example Flow
Time Trigger
The flow starts on a scheduled interval.
Production Order Import (SQL)
Retrieves the latest production orders from the database.
Compare Node (New or Changed Detection)
Compares current results with previously stored results.
New: orders that did not exist before.
Changed: orders with modified fields.
Not Empty Check
Ensures only new or changed records continue.
Export to vPlan
Only new or updated production orders are sent to the Export vPlan Node to be created or updated in vPlan.
Changelog
1.0
November 19, 2025
Initial documentation version added.
Last updated