Other actions

Describe object

Get Describe object metadata.

Describe Object

List of expected config fields

List contains default object types and custom object types.

Supported default object types:

  • Companies

  • Leads

  • Named accounts

  • Opportunities

  • Opportunity roles

  • Salespersons.

List custom objects

Action returns a list of custom objects available in the destination instance, along with additional metadata about the objects.

Upsert objects

Action upsert objects by unique criteria.

Upsert Objects

List config fields

Object type

Supported standard objects:

  • Companies

  • Leads

  • Named accounts

  • Opportunities

  • Opportunity roles

  • Sales persons.

Also supports custom object types.

Criteria

Field used for object upsertion.

If a field is missed in the input body, an error is thrown.

Example of usage

Upsert of one object:

  • Object Type Companies

  • Criteria externalCompanyId

  • Input messsage:

{ "values" : {
 "externalCompanyId": "19UYA31581L000000",
 "company": "Example"
  }
}

Upsert of multiple objects:

  • Object Type Companies

  • Criteria externalCompanyId

  • Input messsage:

{ "values" : [
{
 "externalCompanyId": "19UYA31581L000001",
 "company": "Example 1"
},
{
 "externalCompanyId": "19UYA31581L000002",
 "company": "Example 2"
},
{
 "externalCompanyId": "19UYA31581L000003",
 "company": "Example 3"
}
]}

Limitations

The maximum number of upserted objects in one message is 300.

Delete object by unique criteria

Deletes an object using unique criteria.

Delete Object By Unique Criteria

List config fields

Object type

List contains default object types and custom object types.

Supported default object types:

  • Companies

  • Leads

  • Named accounts

  • Opportunities

  • Opportunity roles

  • Salespersons.

Unique criteria

This menu is needed to choose the field(s) for unique criteria. All object types support the following lookup criteria:

Unique criteria:

  • Marketo ID

  • Dedupe fields.

Except for Leads where only Marketo ID is supported.

Expected input metadata

Input metadata depends on object type and unique criteria.

Expected output metadata

Output metadata is calculated for defined object types dynamically according to Marketo documentation. If an object is not found, the action returns an empty object.

For instance, for object type Companies it is:

json { "type": "object", "properties": { "result": { "type": "array", "items": { "type": "object", "properties": { "status": { "type": "string", "required": true }, "id": { "type": "string", "required": true }, "seq": { "type": "string", "required": true } } } } } }