Webhooks are a widely supported method used to allow multiple applications to interact with each other, using HTTP POST requests to pass callbacks between them. For more information, see Wikipedia's page on webhooks. Common uses for webhooks include sending notifications by email or SMS, posting messages to social media, automatically writing records to a spreadsheet, and updating enterprise databases.
In QuickCapture, you can set up and activate webhooks when a record is submitted. For example, after a successful submission of information to the feature layer, you can call the webhook and trigger another action, such as sending a notification email, appending the record to a spreadsheet, and sending an alert.
Your workplace may have its own webhook provider, but a wide variety of third-party workflow services are available, such as Make, Microsoft Power Automate, Zapier, and tray.io. You can use all of these to incorporate QuickCapture as a trigger for a greater automated process. In particular, Make has a QuickCapture module, allowing you to integrate QuickCapture into your webhook workflow with minimum difficulty and without the need to configure the webhook in the QuickCapture designer or to input a payload URL.
There are many ways you can use QuickCapture as a trigger in your workflows. To get started, Make has templates that you can use to include attachments in your email notifications, add records to spreadsheets, and create calendar items. To learn more, see the Automate workflows with Integromat video.
Note:
The default QuickCapture module in Make is built for projects hosted in ArcGIS Online. To use Make with projects hosted in ArcGIS Enterprise, you must set up a custom connection. For more information, see Connecting Integromat to an ArcGIS Enterprise instance.
You can configure a webhook in the QuickCapture designer by choosing the Webhooks menu item 
. When creating a webhook, provide the following parameters:
- Name—Set the name of the webhook (unique within the project).
- Target feature layer—Select a single feature layer. The payload is sent to the configured webhook URL each time a record is submitted to this layer.
- Webhook URL—Specify where the project information is sent. An external webhook provider must provide this.
- Event data—Choose what information is included in the payload, including project details, information of the user, portal and submitted record, and response from the server.
- Status—Determine whether this webhook is enabled when the project is saved.
For an example of a webhook payload, see FAQ for project authors.