On this Page

Snap type:

Write


Description:

This Snap invokes an Eloqua REST API Update endpoint to modify an Eloqua object of a specified type.

  • Expected input: 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. This document must include a field called "id" which identifies an Eloqua object of the specified object type. Any fields not specified in the document will not be modified in the object. Check the Eloqua API documentation to understand the other required and supported fields specific to the object type. Note that the Eloqua documentation is not very complete/accurate in this respect. 
  • Expected output: The Snap outputs exactly one document for each object successfully updated. This document is produced by the Eloqua endpoint. It describes the updated object in its entirety, including both modified and unmodified fields.


Prerequisites:

[None]


Support and limitations:

Works in Ultra Task Pipelines.

Account: 

This Snap uses account references created on the Accounts page of SnapLogic Manager to handle access to this endpoint. See Eloqua Account for more information.

Views:


InputThis Snap has exactly one document input view. The Eloqua endpoint is invoked once for each input document.
OutputThis Snap has exactly one document output view and produces one document in the view for each successful call to the Eloqua endpoint.
ErrorThis Snap has at most one document error view and produces zero or more documents in the view.


Settings

Label


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


Required. The type of core object to update. 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 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 Assets 2.0
  • External Asset Types 2.0
  • Forms
  • Forms 2.0
  • Images 2.0
  • Imported Files 2.0
  • Landing Pages
  • Landing Pages 2.0
  • Microsites
  • Microsites 2.0
  • Option Lists
  • Option Lists 2.0
  • System Users
  • System Users 2.0


All types without a specified version number are version 1.0.

Example: Contacts
Default value: Accounts


Pass through

Select this checkbox to enable the Snap to pass the input document to the output view under the key original.

Default value: Deselected


Examples

Sample Input Document


{
  "id": "49",
  "emailAddress": "s.smith@Snaplogic.com",
  "salesPerson": "Bob B",
  "fieldValues": [
    {
      "id": "100017",
      "value": "Mr."
    }
  ]
}


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": "Mr."
    },
    ...
    {
      "type": "FieldValue",
      "id": "100043",
      "value": "Developer"
    }
    ...
  ],
  "firstName": "Somebody",
  "isBounceback": "false",
  "isSubscribed": "true",
  "lastName": "Smith",
  "mobilePhone": "987-654-3210",
  "postalCode": "80302",
  "province": "CO",
  "salesPerson": "Bob B",
  "subscriptionDate": "1450313715",
  "title": "Sr. Software Engineer"
}

Sample Error Document


{
  "reason": "Object Not Found (id: 49)",
  "status_code": 404,
  "original": {
    "id": "49",
    ...
  },
  "error": "The PUT request failed",
  "url": "https://secure.p02.eloqua.com/API/REST/2.0/data/contact/49"
}

Snap Pack History