Use Rename fields on a Webhook connection when your receiver expects different JSON names.
This changes names and nesting only. It does not convert HTML to CMS blocks, upload images or create database records.
Set the mapping
Open Integrations → Webhook, find the connection and open Rename fields. Enter a JSON object, then press Save field names.
The left side is the destination path. The right side is the Spron source path:
{
"data.title": "article.title",
"data.bodyHtml": "article.content_html",
"data.spronId": "article.id",
"eventId": "delivery_id"
}
That produces a body shaped like this:
{
"data": {
"title": "Article title",
"bodyHtml": "<p>Article body</p>",
"spronId": "article-id"
},
"eventId": "delivery-id"
}
Keep the fields your receiver needs
A mapping replaces the standard message body. Fields you do not include are not sent in that body. Keep the article ID, delivery ID and any other values your receiver needs.
The signature covers the body actually sent, including your renamed fields. Verify it before parsing as usual.
Leave the mapping empty to restore the standard payload.
When not to rename
Do not use this to send an article straight to an arbitrary CMS REST endpoint. The receiver still needs authentication, signature checks, create-or-update behaviour, image handling and a valid response.
Use standard fields with the Spron receiver packages. They expect the normal message structure. For Zapier, match fields in your Zap action instead.