Differences

This shows you the differences between two versions of the page.

--- transformations:incomingwebhooks [2025/02/18 17:40] – created shell craigt
+++ transformations:incomingwebhooks [2026/09/21 09:22] (current) – Initial article published roberto
@@ Line 5: / Line 5: @@
 \\
 =====Description=====
-This action receives incoming webhook requests from EasyMorph Gateway.
+This action receives incoming webhook requests from [[gateway:start|EasyMorph Gateway]], importing the incoming message (HTTP Request) and processing it. It brings over to the running workflow the requests’ information – request body, headers, URL parameters and other metadata.
 \\
-=====Use cases=====
-\\
 =====Action settings=====
+^Setting ^Description ^
+|Connector<sup>*</sup> |Select an existing Webhook endpoint connector or create a new one.|
+|Command |Select the command this action will perform. Options:\\ //Receive// (see below for more details)|
+<sup>*</sup> Setting can be specified using a [[:parameters|parameter]].
-\\
+====Receive====
-=====Examples=====
-\\
+Description: Fetches messages that are in the webhook endpoint’s queue.
-=====See also=====
+^Setting ^Description ^
+|Fetch up to //x// messages at once |Select the number of messages that should be fetched up at once, from 1 to 10. Note: if the number of queued messages is higher than 10, and the Webhook endpoint is configured to process incoming messages with a task, EasyMorph Hub will trigger the task as many times as necessary to process all the messages waiting in the queue.|
+|Don’t delete messages from queue |Allows retrieving sample messages from the queue without removing them from it. This checkbox is only applicable when designing workflows in EasyMorph Desktop - if a workflow fails, the messages are still preserved in the queue and can be re-retrieved after the workflow is fixed.|
+|Columns |Select the columns types that should appear in the messages received. There are 4 types: //Request body, Headers, URL Parameters, Metadata and technical information//. See below for details of each type.|
+===Columns===
+^Column Type ^Description ^
+|Request body |Data sent by client in message. Column name: Request-Body. The way to receive the request body needs to be specified. Options: //Receive as column value//, //Save to file + add column with file path//<sup>*</sup>.|
+|Headers |Message headers, includes the following columns: accept, accept-encoding, accept-language, Host, priority, sec-ch-ua, sec-ch-ua-mobile, sec-ch-ua-platform, sec-fetch-dest, sec-fetch-mode, sec-fetch-site, sec-fetch-user, upgrade-insecure-requests, User-Agent, X-Forwarded-For, x-forwarded-port, x-forwarded-proto|
+|URL Parameters |Parameters included in the Webhook endpoint URL. Each parameter appears as a new column in the received messages table, with its name as the column header and its value in the first row.|
+|Metadata and technical information |Additional message information. Includes the following columns: Request-Path, Request-Method, ID, Received|
+<sup>*</sup> Setting can be specified using a [[:parameters|parameter]] or the first value of a column.
+\\
+=====Community Examples=====
+  * [[https://community.easymorph.com/t/3712|How to build real-time Salesforce integrations using EasyMorph Gateway]]
+  * [[https://community.easymorph.com/t/5277/1|How to handle Tableau Cloud or Server webhooks with EasyMorph Server]]
+\\
+=====See also=====
+  * [[gateway:start|EasyMorph Gateway]]