In this article

1 Overview
- 1.1 Snap Type
- 1.2 Prerequisites
- 1.3 Support for Ultra Pipelines
- 1.4 Limitations and Known Issues
2 Snap Views
3 Snap Settings
- 3.1 Example
4 Snap Pack History

Overview

You can use this Snap to create an Eloqua object of a specified type by invoking an Eloqua REST API Create endpoint.

Snap Type

The Eloqua Create Snap is a Write-type Snap.

Prerequisites

None.

Support for Ultra Pipelines

Works in Ultra Pipelines.

Limitations and Known Issues

None.

Snap Views

Type	Format	Number of Views	Examples of Upstream and Downstream Snaps	Description

Type

Format

Number of Views

Examples of Upstream and Downstream Snaps

Description

Input

Document

Min: 1
Max: 1

JSON Generator

The Snap invokes the Eloqua endpoint for the given object type once for each input document, using the document as the content sent to the endpoint. Check the Eloqua API documentation to understand the required and supported fields specific to the object type. Note that the Eloqua documentation is not very complete/accurate in this respect.

Output

Document

Min: 1
Max: 1

Mapper

The Snap produces one document in the view for each successful call to the Eloqua endpoint.

Error

Error handling is a generic way to handle errors without losing data or failing the Snap execution. You can handle the errors that the Snap might encounter while running the Pipeline by choosing one of the following options from the When errors occur list under the Views tab:

Stop Pipeline Execution: Stops the current pipeline execution when the Snap encounters an error.
Discard Error Data and Continue: Ignores the error, discards that record, and continues with the remaining records.
Route Error Data to Error View: Routes the error data to an error view without stopping the Snap execution.

Learn more about Error handling in Pipelines.

Snap Settings

Field Name	Field Type	Field Dependency	Description
Label Default Value: Eloqua Create Example: Create Accounts	String	N/A	Required. The name for the Snap. You can modify this to be more specific, especially if you have more than one of the same Snap in your pipeline.
Core object type Default value: Accounts Example: Contacts	Dropdown list	N/A	Required. The type of core object to create. The options available include: Accounts Accounts 2.0 Account Fields Account Fields 2.0 Campaigns Campaigns 2.0 Contacts Contacts 2.0 Contact Fields Contact Fields 2.0 Contact Lists Contact Lists 2.0 Contact Segments Contact Segments 2.0 Content Sections Content Sections 2.0 Custom Object Data Custom Object Metadata Custom Object Metadata 2.0 Emails Emails 2.0 Email Folders Email Folders 2.0 Email Footers Email Footers 2.0 Email Groups Email Groups 2.0 Email Headers Email Headers 2.0 External Activities 2.0 External Assets 2.0 External Asset Types 2.0 Forms Forms 2.0 Form Submission Data Images 2.0 Imported Files 2.0 Landing Pages Landing Pages 2.0 Microsites Microsites 2.0 Option Lists Option Lists 2.0 All types without a specified version number are version 1.0.
Custom Object Metadata ID Default Value: None Example: 7	Integer/Expression	Appears when Custom Object Data* is selected in Core object type dropdown.*	Specify the ID of the metadata that must be associated with the Custom Object Data.
Pass through Default Value: Deselected	Checkbox	N/A	Select this checkbox to enable the Snap to pass the input document to the output view under the key `original`.
	Dropdown list	N/A

Example

Sample Input Document

{
  "emailAddress": "s.smith@Snaplogic.com",
  "firstName": "Somebody",
  "lastName": "Smith",
  "title": "Sr. Software Engineer",
  "accountName": "SnapLogic",
  "businessPhone": "123-456-7890",
  "mobilePhone": "987-654-3210",
  "address1": "929 Pearl St",
  "address2": "Suite 200",
  "city": "Boulder",
  "province": "CO",
  "postalCode": "80302",
  "country": "USA",
  "fieldValues": [
    {
      "id": "100017",
      "value": "Sir"
    },
    {
      "id": "100043",
      "value": "Developer"
    }
  ]
}

Sample Output Document

{
  "type": "Contact",
  "currentStatus": "Awaiting action",
  "id": "49",
  "createdAt": "1450313715",
  "depth": "complete",
  "name": "s.smith@Snaplogic.com",
  "updatedAt": "1450313715",
  "accountName": "SnapLogic",
  "address1": "929 Pearl St",
  "address2": "Suite 200",
  "businessPhone": "123-456-7890",
  "city": "Boulder",
  "country": "USA",
  "emailAddress": "s.smith@Snaplogic.com",
  "emailFormatPreference": "unspecified",
  "fieldValues": [
    {
      "type": "FieldValue",
      "id": "100005"
    },
    {
      "type": "FieldValue",
      "id": "100017",
      "value": "Sir"
    },
    ...
    {
      "type": "FieldValue",
      "id": "100043",
      "value": "Developer"
    }
    ...
  ],
  "firstName": "Somebody",
  "isBounceback": "false",
  "isSubscribed": "true",
  "lastName": "Smith",
  "mobilePhone": "987-654-3210",
  "postalCode": "80302",
  "province": "CO",
  "subscriptionDate": "1450313715",
  "title": "Sr. Software Engineer"
}

SnapLogic Documentation

Eloqua Create

Overview

Snap Type

Prerequisites

Support for Ultra Pipelines

Limitations and Known Issues

Snap Views

Snap Settings

Example

Sample Input Document

Sample Output Document

Sample Error Document

Snap Pack History

Eloqua Create

Overview

Snap Type

Prerequisites

Support for Ultra Pipelines

Limitations and Known Issues

Snap Views

Snap Settings

Example

Sample Input Document

Sample Output Document

Sample Error Document

Snap Pack History .css-qfgm9d{width:100%;height:100%;position:relative;min-height:100px;}.css-15e2tvc{position:absolute;left:50%;top:50%;margin-left:-13px;margin-top:-13px;z-index:100;}

Snap Pack History