Sending a Webhook
After initial setup, the extension popup will open to the Send page, selecting the first action where your current URL matches with the action’s URL RegEx pattern. From this page, you can modify the form as needed and send a webhook to FlexDeploy.- Select a different action in the dropdown, if the action wasn’t automatically set correctly.
- Update the webhook URL as needed.
-
Enter values for any properties not already filled in.
- For single item properties, simply enter the correct value in the input field.
- For list data properties, select whichever option(s) in the dropdown you would like sent with the payload. Additionally, you can type a new option and click Enter to add and select a new option.
- If the webhook Function requires authentication, configure the User API Token and Encryption Key in the browser extension Settings page. The extension uses the Encryption Key to decrypt the stored API Token before sending the webhook request.
- The Encryption Key is retained when the browser extension popup is closed and reopened. However, it is cleared when the browser is restarted. After restarting the browser, you will be prompted to enter the same Encryption Key on the extension’s opening page to continue using the stored API Token.
for a valid response or a :Failed: with the error message for a failed response. You can check the console logs for more details after a failed response.
Check the incoming webhook messages page in your FlexDeploy instance to see how the webhook was received and processed.
Creating/Updating an Action
From the Actions menu, you can create and configure your own actions which will define the content being sent to FlexDeploy. Each action will be linked to some webhook URL defined by you, so you could have different actions for each webhook function you want to run in FlexDeploy.Action Details
Name | Description |
|---|---|
Name | Name to identify your action |
Base Action | Technology template to use, which will add some technology-specific properties to the action and set a URL match pattern. Currently, base actions are available for Oracle APEX, ORDS, OIC, OPA, OBIEE, OTBI, OAC, Azure Power BI, Oracle Visual Builder, and Salesforce. |
Webhook URL | URL to send to FlexDeploy. This will be in the format <FlexDeploy base URL>/flexdeploy/webhooks/v1/<webhook function URI>. The value here will be concatenated to the base URL configured in the extension settings. |
URL Match Pattern | A regular expression to determine when the extension should default to this action when the popup is opened. For help generating an expression, see regex101: build, test, and debug regex. Example: ./apex/f. for an APEX action |
Properties | Define any additional information you want to send along with your webhook. See more details in the table below. |
Properties
Name | Description |
|---|---|
Name | Name for your property. |
Data Type | Options are single item or list data. All values are sent as string. |
Default Value Type | Literal - Literal text Selector - A CSS selector to derive the property’s value from page content. |
Default Value | The literal text or selector to be used for finding the default value. |
Subfield | Optionally, provide a subfield for the value for each list item. (applicable when using a selector for calculating the default value) |