Overview
This node integrates with Microsoft Dataverse to manage entity records within Dataverse tables. Specifically, the "Create" operation for the "Entity Record" resource allows users to create new records in a specified Dataverse entity table by providing field values.
Common scenarios where this node is beneficial include:
- Automating the creation of customer accounts, contacts, or opportunity records in Dataverse from external data sources.
- Integrating form submissions or other application data flows directly into Dataverse entities.
- Populating Dataverse tables as part of larger workflows involving CRM or business process automation.
For example, you could use this node to create a new contact record in the "contacts" table by specifying the contact's name, email, and phone number fields.
Properties
| Name | Meaning |
|---|---|
| Entity Table Name | The logical name of the Dataverse entity table where the record will be created (e.g., accounts, contacts, opportunities). This is required. |
| Fields to Send | A collection of fields and their corresponding values to set on the new record. Each entry includes: - Field Name: The name of the field to set. - Field Value: The value to assign to that field. Multiple fields can be added. |
Output
The output is an array of JSON objects representing the newly created entity records returned from Dataverse. Each output item contains:
json: The full JSON response from the Dataverse API for the created record, which typically includes the record's unique identifier and any default or computed fields returned by the service.pairedItem: Metadata linking the output item back to the input item index.
No binary data is produced by this operation.
Dependencies
- Requires an active connection to Microsoft Dataverse via an API key credential or OAuth token configured in n8n.
- The node uses the Microsoft Dataverse REST API endpoints to perform operations.
- Proper permissions are needed on the Dataverse environment to create records in the specified entity table.
Troubleshooting
- Missing or incorrect Entity Table Name: Ensure the logical name of the entity table is correct and exists in your Dataverse environment.
- Invalid field names or values: Field names must match those defined in the Dataverse schema. Values should conform to expected data types.
- Authentication errors: Verify that the API credentials are valid and have sufficient permissions.
- API request failures: Network issues or API limits may cause errors; check connectivity and Dataverse service status.
- Error messages typically include HTTP error codes and messages from Dataverse. Review these messages to identify issues such as unauthorized access, invalid requests, or quota exceeded.
To resolve errors, verify all input parameters, ensure proper authentication, and consult Dataverse API documentation for specific error codes.