Inbound Cloud Connect amazonaws com
Inbound Cloud Connect
Extended Cloud Connect is supported as an inbound. This allows the user to call the Cloud Connect from an external application, without an OutboundContact_ID.
Step 1:Download the maml provided and open in Studio Step 2: Get Schedule ID ( required to get Identifier ) Add Schedule with Target Audience and publish the campaign.To get Schedule id check the screenshots below
Step 3: Get identifier
Click on help -> Schedule’s Activity-> Enter Schedule Id->Get Schedule Activity->Copy Identifier. Check screenshots below
Identifier - 2321_456_636066115858063635 AccountID- 2321 (First part of Identifier before “_”) Step 4: Get Outbound Id for the cloud connect element Check in Program maml
Note: 1. Every time there is a change in JSCallbackHandler(cloud connect configuration), it is necessary to schedule cloud connect and get a new identifier. 2. Standard body is not supported at this time, must use JS. Step 5: Chrome plugin Postman Set Up to make http request 1st Use Case: Update field values in Studio from Postman Values in Studio before update
Replace the variables identifier, account id and outbound id with the values in Studio callback endpoint ##identifier##=2321_456_636066115858063635 ##accountid##=2321 ##outboundid##=278 http://studio.afw.mdl.io/api/OutboundApp/AppCallback?serviceTypeId=2019&identifier=##identifier## &accountId=##accountid##&outboundId=##outboundid## -> http://studio.afw.mdl.io/api/OutboundApp/AppCallback?serviceTypeId=2019&identifier=2321_456_ 636066115858063635&accountId=2321&outboundId=278
Body: It is necessary to add dedupe (or) email field while making a request. { "request": { "firstname":"Manasa24", "lastname":"Pradeep24", "email":"[email protected]" } }
After successful request, the request is parsed in JSCallBackHandler in Cloud Connect and the contact has been updated in Studio
2nd Use Case: Add contact to Studio from Postman Dedupe field is required to add a contact { "request": { "firstname":"Manasa24", "lastname":"Pradeep24", "email":"[email protected]" } }
After successful request, the request is parsed in JSCallBackHandler in Cloud Connect and the new contact is added to Studio
3rd Use case: Associate events to a contact from Postman
{ "request": { "eventid": "201915", "date": "2016-08-09T03:25:47", "eventoption":"Contact Added",
"dedup":"email::[email protected]", } } Note: 1. Dedupe is required to identify contact. Date specifies when the event has to be created. 2. The eventid, event option -> are studio event fields required to create event. After a successful request, the request is parsed in JSCallBackHandler ->Cloud Connect and the new event is associated with the contact in Studio. Once events are associated with a contact, an email or any outbound can be triggered to the specific contact.
Extended Cloud Connect is supported as an inbound. This allows the user to call the Cloud Connect from an external application, without an OutboundContact_ID.
Step 1:Download the maml provided and open in Studio Step 2: Get Schedule ID ( required to get Identifier ) Add Schedule with Target Audience and publish the campaign.To get Schedule id check the screenshots below
Step 3: Get identifier
Click on help -> Schedule’s Activity-> Enter Schedule Id->Get Schedule Activity->Copy Identifier. Check screenshots below
Identifier - 2321_456_636066115858063635 AccountID- 2321 (First part of Identifier before “_”) Step 4: Get Outbound Id for the cloud connect element Check in Program maml
Note: 1. Every time there is a change in JSCallbackHandler(cloud connect configuration), it is necessary to schedule cloud connect and get a new identifier. 2. Standard body is not supported at this time, must use JS. Step 5: Chrome plugin Postman Set Up to make http request 1st Use Case: Update field values in Studio from Postman Values in Studio before update
Replace the variables identifier, account id and outbound id with the values in Studio callback endpoint ##identifier##=2321_456_636066115858063635 ##accountid##=2321 ##outboundid##=278 http://studio.afw.mdl.io/api/OutboundApp/AppCallback?serviceTypeId=2019&identifier=##identifier## &accountId=##accountid##&outboundId=##outboundid## -> http://studio.afw.mdl.io/api/OutboundApp/AppCallback?serviceTypeId=2019&identifier=2321_456_ 636066115858063635&accountId=2321&outboundId=278
Body: It is necessary to add dedupe (or) email field while making a request. { "request": { "firstname":"Manasa24", "lastname":"Pradeep24", "email":"[email protected]" } }
After successful request, the request is parsed in JSCallBackHandler in Cloud Connect and the contact has been updated in Studio
2nd Use Case: Add contact to Studio from Postman Dedupe field is required to add a contact { "request": { "firstname":"Manasa24", "lastname":"Pradeep24", "email":"[email protected]" } }
After successful request, the request is parsed in JSCallBackHandler in Cloud Connect and the new contact is added to Studio
3rd Use case: Associate events to a contact from Postman
{ "request": { "eventid": "201915", "date": "2016-08-09T03:25:47", "eventoption":"Contact Added",
"dedup":"email::[email protected]", } } Note: 1. Dedupe is required to identify contact. Date specifies when the event has to be created. 2. The eventid, event option -> are studio event fields required to create event. After a successful request, the request is parsed in JSCallBackHandler ->Cloud Connect and the new event is associated with the contact in Studio. Once events are associated with a contact, an email or any outbound can be triggered to the specific contact.
