token value inside ics file is not getting populated, campaign triggered via REST API | Community
Skip to main content
November 5, 2018
Solved

token value inside ics file is not getting populated, campaign triggered via REST API

  • November 5, 2018
  • 1 reply
  • 2348 views

I am facing an issue here related to populating token value in ics file.

I have two tokens defined in my program

{{my.eventUrl}} - Text

{{my.icsInfo}} - Calendar File

Inside '{{my.icsInfo}}' configuration, in description field I have put the token {{my.eventUrl}}

ics description text :

Web Link : {{my.eventUrl}}

In the Campaign -> Flow -> Send Email, the Email Template contains both the tokens.

It's like, Email having `Event Join Url` and `Save to Calendar`(ics).

I am adding a lead to this Campaign through REST API.

POST /rest/v1/campaigns/{campaignId}/trigger.json

{"input": {"leads": [{"id": 1111111}],"tokens": [{"name": "{{my.eventUrl}}","value": "myevent.sampleurl/join"}]}}

Problem :

The Email received is having the token value populated as "myevent.sampleurl/join", but the same value is not getting populated inside ics file contained in the Email.

Token inside the Email is containing the old value assigned at the token creation time.

So any idea, how to populate this token's value inside the ics file, when Campaign is triggered via REST API ?

Do I need to pass {{my.icsInfo}} token as well along with {{my.eventUrl}} token ?

Thanks

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by SanfordWhiteman

Nesting and advanced token types don't work with the "runtime token" feature of the Trigger and Schedule Campaign API endpoints.

But I'd advise dropping the ICS token completely (it has no net advantage) and passing an Agical URL as a Text {{my.token}} instead.

For example:

http:​//ics.agical.io/?subject=Meet%20Sanjay&organizer=Sanjay%20Behera&reminder=45&location=Sanjay%27s%20Desk&dtstart=2018-11-26T15:00:00-04:00&dtend=2018-11-26T16:00:00-04:00&attach=http:​//myevent.example.com/join

The ICS is generated dynamically upon click (that was probably obvious) and has tons of customizations.

1 reply

SanfordWhiteman
SanfordWhitemanAccepted solution
New Participant
November 5, 2018

Nesting and advanced token types don't work with the "runtime token" feature of the Trigger and Schedule Campaign API endpoints.

But I'd advise dropping the ICS token completely (it has no net advantage) and passing an Agical URL as a Text {{my.token}} instead.

For example:

http:​//ics.agical.io/?subject=Meet%20Sanjay&organizer=Sanjay%20Behera&reminder=45&location=Sanjay%27s%20Desk&dtstart=2018-11-26T15:00:00-04:00&dtend=2018-11-26T16:00:00-04:00&attach=http:​//myevent.example.com/join

The ICS is generated dynamically upon click (that was probably obvious) and has tons of customizations.

November 5, 2018

Thanks Sanford for the information.

Have a Good Day !!!