Bit Integrations can pass submitted form fields from WordPress to another service. Before setting it up, check that it supports your form plugin and the destination you want to use. Connector availability and licence requirements vary.
Choose the trigger and destination
Check the current Bit Integrations interface for your exact form plugin, trigger and destination. Some connectors or actions require a paid licence. Confirm the required fields before building the form.
Map only the fields you need
Match names, email addresses and enquiry fields to the destination’s expected format. Consider optional fields, empty values, number formats and dropdown values. Keep consent and marketing permissions separate from a request for a quote or information.
Keep credentials on the WordPress side
Configure the integration through its authorised WordPress interface. Do not put CRM API keys or webhook secrets into a static page, browser script or public form field. Review which administrators can change the connection.
Use a test destination first
Send a controlled test through the source form, then through the embedded version. Verify that exactly one record arrives with the expected field values. Test a missing optional field and an invalid required field. A validation error should not trigger a successful downstream workflow.
Check failure handling
Find out where the form plugin and integration record failures, whether retries are available, and how duplicates are handled. Form success, email delivery and CRM creation are separate events: test each instead of treating a thank-you page as proof of all three.
Finish with the visitor journey
Once the integration is working, confirm the parent-page redirect and any follow-up email. Document the form, mapping, destination and person responsible for monitoring failures.