4.9.4
Core Forms 4.9.4 fixes integration delivery, retries, field mapping, and provider compatibility.
Fixed
- Unify action outcomes across submissions, paid fulfillment, testing, replay, and queued work; report transport/provider failures and missing handlers accurately.
- Connect background delivery and transient retries to eligible actions, with saved-submission requirements, execution leases, and ActiveCampaign/Kit checkpoints.
- Preserve unavailable integrations and validate field mappings; retain explicit unchecked settings.
- Correct Notion title/property mapping, Airtable value types and metadata, FluentCommunity membership APIs, and raw WhatsApp webhook responses.
- Replace the broken Sheets setup link with a maintained authenticated receiver and align integration descriptions with the implemented capabilities.
Integration setup
- Airtable tokens require schema.bases:read and data.records:write for the selected base. Notion connections require read and insert access to the shared database or data source. These permissions let Core Forms match the destination schema and send correctly typed values.
- Google Sheets has a maintained receiver with a shared-secret setting. Existing plain OK receivers remain supported; the new receiver must use the same secret as the form action.