Follow

Parsing examples

 

Goal: "Join team" or "join" matchphrase and parse team from message

 (join && |parse('letters_numbers_latin') as this-team|) || (join team && |parse('letters_numbers_latin') as this-team|) 

 

Goal: Update someone's audience record to include their phone number asking them to email it to a character

|parse("phone_us") into audience.sender.account.phone|

 

Goal: Get someone's twitter ID from a Facebook comment

|parse("twitter_handle") into audience.sender.account.twitter|

 

Goal: Create a team using "create team" as a command phase.
create team |parse("team_names") as thisTeam|

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

  • Avatar
    Ben Byford

    where abouts are these phrases used? does one need to setup a varible first?

  • Avatar
    Robert Pratten

    Dynamic variables are used ad hoc and only last for one processing cycle.
    The parsing is entered in the matchphrase of a message trigger or API trigger.
    You can use the dynamic variables in conditions, logic actions and content actions

  • Avatar
    Ben Byford

    for example: how would one create an api trigger match and url which you could then exact the phone number from to send a messge back to?

  • Avatar
    Robert Pratten

    For that you'd use core attributes rather than variables.
    The matchphrase could be
    |parse('phone_us') into audience.sender.accounts.phone|

    And then the content is a reply to sender

  • Avatar
    Ben Byford

    sure, im unsure about what its parsing. i.e. which varible incoming? also is there a list of default like audience.sender.accounts.phone?

    this is what i have currently: unauth/tel sender_phone|parse('phone_number_intl') into audience.sender.accounts.phone|

    it triggers but doesnt pass the number over to the action message

  • Avatar
    Robert Pratten

    There are the parsing templates available https://conducttr.zendesk.com/hc/en-us/articles/204308805-Available-parsing-templates

    When you use a parsing template, Conducttr looks through the whole message and matches every instance. So if you have two phone numbers it would add both.

    In your example I would remove sender_phone although if its triggering that would indicate to me that it's grabbed the phone number.

    Can you raise a support ticket and include a screen grab of the Project Activity feed? This usually reveals what's going on.