Skip to main content
allenp0001
allenp0001
Known Participant
February 16, 2021
Solved

Confirmation link in Email

I have a need to add a confirmation link for the email recipient to be able to click to confirm information in the email.

Has anyone done something like this?

    danny.verb
    danny.verbAnswer
    Employee
    February 16, 2021

    Since all requests to Appian must be authenticated this may not be possible. What you could look at doing, but I do not recommend, is creating a web API object which will make a Post call when clicked on. You can authenticate that web API by making an Appian service account which has very very restricted access to only the objects you need such as a specific data store, the web API object, and potentially any process models. Using bit.ly you can construct a URL with the API key in the header but mask the URL so it isn't shown to the user in the email. I discourage this because you are essentially making an API key public but if the confirmation link doesn't need any authentication anyway then you shouldn't have security concerns if you set up object security correctly.

    View in thread

    3 replies

    danny.verb
    danny.verb
    Employee
    February 16, 2021

    The easiest thing to do is have the process create a task for the user to verify and then you can have the task itself send an email to the user asking them to confirm information or you can use the task ID and a!urlfortask() to add a task URL to a different email.

      allenp0001
      allenp0001Author
      Known Participant
      February 16, 2021

      Thank you, but this would be for a non Appian user.

      danny.verb
      danny.verbAnswer
      Employee
      February 16, 2021

      Since all requests to Appian must be authenticated this may not be possible. What you could look at doing, but I do not recommend, is creating a web API object which will make a Post call when clicked on. You can authenticate that web API by making an Appian service account which has very very restricted access to only the objects you need such as a specific data store, the web API object, and potentially any process models. Using bit.ly you can construct a URL with the API key in the header but mask the URL so it isn't shown to the user in the email. I discourage this because you are essentially making an API key public but if the confirmation link doesn't need any authentication anyway then you shouldn't have security concerns if you set up object security correctly.

        Terms & ConditionsAccessibility statement