<?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 Connector SDK - Access webhook notification in Hybrid Trigger Poll in Workato Pros Discussion Board</title>
    <link>https://systematic.workato.com/t5/workato-pros-discussion-board/connector-sdk-access-webhook-notification-in-hybrid-trigger-poll/m-p/6179#M2726</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Is it possible to get the payload of a notification&amp;nbsp;that triggered the poll lambda in a hybrid trigger?&lt;/P&gt;&lt;P&gt;Example:&lt;/P&gt;&lt;LI-CODE lang="ruby"&gt;# poll lambda on my hybrid trigger
poll: lambda do |connection, input, closure, _eis, _eos, payload|
    # get data from notification to use in the polling process
    payload.dig('some field in my notification')
end&lt;/LI-CODE&gt;&lt;P&gt;The SDK reference (&lt;A href="https://docs.workato.com/developing-connectors/sdk/sdk-reference/triggers.html#poll" target="_blank" rel="noopener"&gt;https://docs.workato.com/developing-connectors/sdk/sdk-reference/triggers.html#poll&lt;/A&gt;) doesn't mention anything about it, but it feels like it would make perfect sense to be able to access data from the notification that triggered the poll in the first place.&lt;/P&gt;</description>
    <pubDate>Thu, 29 Feb 2024 21:09:51 GMT</pubDate>
    <dc:creator>jramirez</dc:creator>
    <dc:date>2024-02-29T21:09:51Z</dc:date>
    <item>
      <title>Connector SDK - Access webhook notification in Hybrid Trigger Poll</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/connector-sdk-access-webhook-notification-in-hybrid-trigger-poll/m-p/6179#M2726</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;Is it possible to get the payload of a notification&amp;nbsp;that triggered the poll lambda in a hybrid trigger?&lt;/P&gt;&lt;P&gt;Example:&lt;/P&gt;&lt;LI-CODE lang="ruby"&gt;# poll lambda on my hybrid trigger
poll: lambda do |connection, input, closure, _eis, _eos, payload|
    # get data from notification to use in the polling process
    payload.dig('some field in my notification')
end&lt;/LI-CODE&gt;&lt;P&gt;The SDK reference (&lt;A href="https://docs.workato.com/developing-connectors/sdk/sdk-reference/triggers.html#poll" target="_blank" rel="noopener"&gt;https://docs.workato.com/developing-connectors/sdk/sdk-reference/triggers.html#poll&lt;/A&gt;) doesn't mention anything about it, but it feels like it would make perfect sense to be able to access data from the notification that triggered the poll in the first place.&lt;/P&gt;</description>
      <pubDate>Thu, 29 Feb 2024 21:09:51 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/connector-sdk-access-webhook-notification-in-hybrid-trigger-poll/m-p/6179#M2726</guid>
      <dc:creator>jramirez</dc:creator>
      <dc:date>2024-02-29T21:09:51Z</dc:date>
    </item>
    <item>
      <title>Re: Connector SDK - Access webhook notification in Hybrid Trigger Poll</title>
      <link>https://systematic.workato.com/t5/workato-pros-discussion-board/connector-sdk-access-webhook-notification-in-hybrid-trigger-poll/m-p/6654#M2887</link>
      <description>&lt;P&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;After carefully reviewing your concern, further investigation may be necessary.&amp;nbsp;&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;If you want this matter addressed more, we suggest using your active Workato account to submit a ticket through our Support Portal.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Thank you&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 10 May 2024 11:58:15 GMT</pubDate>
      <guid>https://systematic.workato.com/t5/workato-pros-discussion-board/connector-sdk-access-webhook-notification-in-hybrid-trigger-poll/m-p/6654#M2887</guid>
      <dc:creator>julie-reyes</dc:creator>
      <dc:date>2024-05-10T11:58:15Z</dc:date>
    </item>
  </channel>
</rss>

