Push Data
The Push Data (Post Settings) feature forwards each submission to a third-party URL in real time, connecting CRMs, marketing systems, webhooks and other services.
Available since 03.00.00 with rich customization options.
Enable
When enabled, every submission pushes data to the target address as configured below.
Push Type / Form Method
- POST: submit data as a form POST (most common).
- GET: submit data as query strings.
Post URL
The server address receiving the data (your CRM endpoint, webhook URL, etc.), for example:
https://api.example.com/forms/receiveQuery String
Additional query parameters for GET-style pushes.
Wait Text
The wait message shown on the form page while pushing (e.g. "Submitting, please wait…").
App Verify / Verify Url
If the target endpoint requires authentication, configure the verification identifier and URL here.
Request Headers
Customize the HTTP headers of the push request to simulate a normal browser or satisfy the receiver:
| Setting | Description |
|---|---|
| Accept Language | Accept-Language header |
| Accept Encoding | Accept-Encoding header |
| Accept | Accept header |
| User Agent | User-Agent header |
Pushed Data Format
The payload contains all field values of the submission (field Name → submitted value pairs); the receiving end parses them by field name.
Example
After a lead is submitted on the DNN site, it is pushed automatically to the CRM's lead-capture endpoint — the sales team never copies data manually. Common integrations: Zapier / Make webhooks, custom APIs, WeCom/DingTalk bots.
External Form vs Push Data
| Feature | Data direction |
|---|---|
| External Form | Form data from external sites into DNN |
| Push Data | DNN submissions out to third-party systems |
Next Steps
- External Form — the reverse integration
- Submission Records — data storage