<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Using Workato for automating processes that require email approval in Workato Pros Discussion Board</title>
    <link>https://systematic.workato.com/t5/workato-pros-discussion-board/using-workato-for-automating-processes-that-require-email/m-p/8366#M3500</link>
    <description>&lt;P&gt;Even if you used the API platform I think you'd need to encode the access token into the URL to call the endpoint, so security kinda goes out the window.&lt;/P&gt;&lt;P&gt;I can't think really think of a way to protect the endpoint, but you can at least verify the email_id against a list of known IDs to ensure the call is coming from an email recipient before routing to the next recipe/process.&lt;/P&gt;&lt;P&gt;I could be missing something so if you have ideas on how to secure the endpoint using the API platform, please share!&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 20 Dec 2024 18:35:45 GMT</pubDate>
    <dc:creator>gary1</dc:creator>
    <dc:date>2024-12-20T18:35:45Z</dc:date>
    <item>
      <title>Using Workato for automating processes that require email approval</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/using-workato-for-automating-processes-that-require-email/m-p/8339#M3485</link>
      <description>&lt;DIV&gt;I use Workato Embedded to build automated Customer Reference Request processes for my customers. Each process/recipe has a step that uses Gmail or Outlook to send an email to the requested customer asking if they'd be willing to take a reference call. I'd like to have it so the customer who receives the email can either approve or reject the request, and based on that response, execute the appropriate next steps in the workflow.&lt;/DIV&gt;&lt;DIV&gt;&amp;nbsp;&lt;/DIV&gt;&lt;DIV&gt;Is there a way to build this type of workflow in Workato, to listen for a reply to a previously sent email and take action on it? I imagine that the first email would have to be structured in some way so that we know what responses to listen for, like "Yes" or "No", or have buttons in the email with the response choices? Any advice on how others have handled this is appreciated.&lt;/DIV&gt;</description>
      <pubDate>Wed, 18 Dec 2024 03:06:37 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/using-workato-for-automating-processes-that-require-email/m-p/8339#M3485</guid>
      <dc:creator>jeffernst</dc:creator>
      <dc:date>2024-12-18T03:06:37Z</dc:date>
    </item>
    <item>
      <title>Re: Using Workato for automating processes that require email approval</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/using-workato-for-automating-processes-that-require-email/m-p/8354#M3494</link>
      <description>&lt;P data-unlink="true"&gt;Hi Jeffer,&lt;BR /&gt;&lt;BR /&gt;The response to an email can be unsure as when the user will perform an action to the email.&lt;BR /&gt;You can have to follow asynchronous approach.&lt;BR /&gt;&lt;BR /&gt;1. 1st Recipe will send an email with option yes/no which could be a workato API[https://docs.workato.com/api-mgmt/api-endpoints.html#setting-up-and-managing-api-endpoints&amp;nbsp;] and should be able to capture somewhere in the DB that the email has been sent. Like emailaddress, mail sent, response received[Yes/No].&lt;BR /&gt;2. 2nd receipe would listen to the request and update the db with response.&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 20 Dec 2024 09:04:06 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/using-workato-for-automating-processes-that-require-email/m-p/8354#M3494</guid>
      <dc:creator>Prudvi</dc:creator>
      <dc:date>2024-12-20T09:04:06Z</dc:date>
    </item>
    <item>
      <title>Re: Using Workato for automating processes that require email approval</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/using-workato-for-automating-processes-that-require-email/m-p/8358#M3495</link>
      <description>&lt;P&gt;&lt;a href="https://systematic.workato.com/t5/user/viewprofilepage/user-id/11321"&gt;@Prudvi&lt;/a&gt;&amp;nbsp;Thanks for your reply. Can you provide more details on what you mean by: "&lt;SPAN&gt;email with option yes/no which could be a workato API". I looked at the docs page you linked to but I don't understand how these APIs would be put to use in this use case. I have my own API that updates my objects and I have a Status field to track that the email has been sent, responded to, etc.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 20 Dec 2024 12:06:32 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/using-workato-for-automating-processes-that-require-email/m-p/8358#M3495</guid>
      <dc:creator>jeffernst</dc:creator>
      <dc:date>2024-12-20T12:06:32Z</dc:date>
    </item>
    <item>
      <title>Re: Using Workato for automating processes that require email approval</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/using-workato-for-automating-processes-that-require-email/m-p/8360#M3496</link>
      <description>&lt;P&gt;Hi Jeffer,&lt;BR /&gt;&lt;BR /&gt;Consider the following mail message :&lt;/P&gt;&lt;P&gt;"Hi Name,&lt;BR /&gt;Your specific message.&lt;BR /&gt;Would you like to refer : &lt;A href="http://www.api.com/response?accept=Yes" target="_self"&gt;Yes&lt;/A&gt; or &lt;A href="http://www.api.com/response?accept=No" target="_self"&gt;No.&lt;/A&gt;&lt;BR /&gt;If you hover over the link, you can insert your API."&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Prudvi&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 20 Dec 2024 12:26:18 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/using-workato-for-automating-processes-that-require-email/m-p/8360#M3496</guid>
      <dc:creator>Prudvi</dc:creator>
      <dc:date>2024-12-20T12:26:18Z</dc:date>
    </item>
    <item>
      <title>Re: Using Workato for automating processes that require email approval</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/using-workato-for-automating-processes-that-require-email/m-p/8363#M3497</link>
      <description>&lt;P&gt;&lt;a href="https://systematic.workato.com/t5/user/viewprofilepage/user-id/11321"&gt;@Prudvi&lt;/a&gt;&amp;nbsp;This is exactly what I want to do. How do I set up the link so that hovering over it calls my api? I can't tell from that doc page where I would start.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Dec 2024 12:47:32 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/using-workato-for-automating-processes-that-require-email/m-p/8363#M3497</guid>
      <dc:creator>jeffernst</dc:creator>
      <dc:date>2024-12-20T12:47:32Z</dc:date>
    </item>
    <item>
      <title>Re: Using Workato for automating processes that require email approval</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/using-workato-for-automating-processes-that-require-email/m-p/8364#M3498</link>
      <description>&lt;P&gt;You could also do this with a Webhook recipe. It's a bit easier to set up compared to the API platform.&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Create a new recipe with a "Webhook" trigger&lt;/LI&gt;&lt;LI&gt;Name the event "get_user_response"&lt;/LI&gt;&lt;LI&gt;Adding an event name will generate a webhook URL, like&amp;nbsp;&lt;SPAN&gt;&lt;A href="https://webhooks.workato.com/webhooks/rest/big-long-uuid-here/get_user_response" target="_blank"&gt;https://webhooks.workato.com/webhooks/rest/big-long-uuid-here/get_user_response&lt;/A&gt;&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;Set the request type to "GET"&lt;/LI&gt;&lt;LI&gt;Set a query param for "user_response" -- this will represent the YES or NO from the email&lt;/LI&gt;&lt;LI&gt;Set another query param for "email_id" -- this is really important because when you receive their response, you need enough context to identify its origin. This means when you&amp;nbsp;&lt;EM&gt;send&lt;/EM&gt; them the email, you need to encode an ID in the link so the webhook can send it back to identify the origin of the response. Otherwise you'd get a bunch of "yes" and "no" responses without having the context of their origin. The ID doesn't need to be an ID in the traditional sense, but something that let's you differentiate one response from the next&lt;/LI&gt;&lt;LI&gt;Add a logger as step to and add the "user_response" data pill from the trigger&lt;/LI&gt;&lt;LI&gt;Add another logger with "email_id" data pill&lt;/LI&gt;&lt;LI&gt;Turn on the recipe or run a test&lt;/LI&gt;&lt;LI&gt;Open a web browser or terminal and call the webhook URL with the user_response and email_id params, like this: h&lt;SPAN&gt;ttps://webhooks.workato.com/webhooks/rest/big-long-uuid-here/get_user_response?user_response=yes&amp;amp;email_id=12345&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;The recipe should trigger, parse the params, and step 2 logger should read "yes", and step 3 logger should read "12345". Your browser will show a simple JSON response from the webhook. This can't be controlled (to my knowledge)&lt;/LI&gt;&lt;LI&gt;Assuming this all worked, you can now update the links in the emails to the webhook URL with different user_response and email_id values. Build out the recipe to do what's needed based on their response.&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;It's also possible to do this via the API platform, and the benefit&amp;nbsp;&lt;EM&gt;might&lt;/EM&gt; be that you can control the response to the browser, but I'm honestly not sure about that. Hope this helps.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Dec 2024 17:32:52 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/using-workato-for-automating-processes-that-require-email/m-p/8364#M3498</guid>
      <dc:creator>gary1</dc:creator>
      <dc:date>2024-12-20T17:32:52Z</dc:date>
    </item>
    <item>
      <title>Re: Using Workato for automating processes that require email approval</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/using-workato-for-automating-processes-that-require-email/m-p/8365#M3499</link>
      <description>&lt;P&gt;Thanks&amp;nbsp;&lt;a href="https://systematic.workato.com/t5/user/viewprofilepage/user-id/1188"&gt;@gary1&lt;/a&gt;&amp;nbsp;for clear explanation The only reason for API was for security.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Dec 2024 17:42:06 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/using-workato-for-automating-processes-that-require-email/m-p/8365#M3499</guid>
      <dc:creator>Prudvi</dc:creator>
      <dc:date>2024-12-20T17:42:06Z</dc:date>
    </item>
    <item>
      <title>Re: Using Workato for automating processes that require email approval</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/using-workato-for-automating-processes-that-require-email/m-p/8366#M3500</link>
      <description>&lt;P&gt;Even if you used the API platform I think you'd need to encode the access token into the URL to call the endpoint, so security kinda goes out the window.&lt;/P&gt;&lt;P&gt;I can't think really think of a way to protect the endpoint, but you can at least verify the email_id against a list of known IDs to ensure the call is coming from an email recipient before routing to the next recipe/process.&lt;/P&gt;&lt;P&gt;I could be missing something so if you have ideas on how to secure the endpoint using the API platform, please share!&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 20 Dec 2024 18:35:45 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/using-workato-for-automating-processes-that-require-email/m-p/8366#M3500</guid>
      <dc:creator>gary1</dc:creator>
      <dc:date>2024-12-20T18:35:45Z</dc:date>
    </item>
    <item>
      <title>Re: Using Workato for automating processes that require email approval</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/using-workato-for-automating-processes-that-require-email/m-p/8367#M3501</link>
      <description>&lt;P&gt;&lt;a href="https://systematic.workato.com/t5/user/viewprofilepage/user-id/1188"&gt;@gary1&lt;/a&gt;&amp;nbsp; This is awesome. Do you happen to have a sample recipe you could share that has the webhook configured as you described?&lt;/P&gt;</description>
      <pubDate>Sun, 22 Dec 2024 12:51:46 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/using-workato-for-automating-processes-that-require-email/m-p/8367#M3501</guid>
      <dc:creator>jeffernst</dc:creator>
      <dc:date>2024-12-22T12:51:46Z</dc:date>
    </item>
  </channel>
</rss>

