Actions15
Overview
This node interacts with Oracle Eloqua's REST API to create custom object data entries. It allows users to specify a parent custom object by its ID and add various optional fields and custom fields to the new custom object data instance. This is useful for automating the creation of detailed custom data records within Eloqua, such as adding new customer-related data or other custom entities tied to a parent object.
Use Case Examples
- Creating a new custom object data entry for a specific custom object parent ID with additional descriptive fields and custom field values.
- Automating the insertion of custom data records in Eloqua for marketing or CRM purposes.
Properties
| Name | Meaning |
|---|---|
| Authentication | The authentication method to use for the API request (Basic Authentication or OAuth2). |
| Parent ID | The ID of the parent custom object to which the custom object data belongs. This is required. |
| Additional Fields | Optional additional fields for the custom object data, such as current status, name, description, source template ID, contact ID, unique code, record status, and mapping status. |
| Custom custom Object Fields | Custom fields to set specific field values for the custom object data. Each field requires a field ID and a value. |
Output
JSON
id- The unique identifier of the created custom object data entry.fieldValues- The custom field values set on the custom object data.name- The name of the custom object data entry, if provided.description- The description of the custom object data entry, if provided.currentStatus- The current status of the custom object data entry, if provided.sourceTemplateId- The source template ID used to create the asset, if provided.contactId- The contact ID associated with the custom object data, if provided.uniqueCode- The unique code associated with the custom object data, if provided.customObjectRecordStatus- The record status of the custom object data, if provided.isMapped- Indicates if the custom object data is mapped to a custom object, if provided.
Dependencies
- Oracle Eloqua REST API
Troubleshooting
- Ensure the Parent ID is valid and exists in Eloqua, as the API endpoint requires it to create the custom object data instance.
- Verify that the authentication credentials (Basic Auth or OAuth2) are correctly configured and have sufficient permissions to create custom object data.
- If the API returns errors related to field IDs or values, confirm that the custom field IDs used exist and the values conform to expected formats.
- Network or API rate limiting issues may cause request failures; handle errors and consider retry logic or rate limiting in workflows.
Links
- Oracle Eloqua REST API - Create Custom Object Data Instance - Official documentation for creating custom object data instances via the Eloqua REST API.