Action Hook As A trigger

Bit Integrations is a WordPress plugin that can help you automate and integrate your Action Hook with over 200+ popular platforms, including Zoho CRM, Zoho Sheet, Zoho Campaign, ActiveCampaign, Airtable, Agiled CRM, Dropbox, Copper CRM, Capsule CRM, HubSpot, Groundhogg, Google Drive, Google Sheet, Zoom, Zoho Recruit, Zoho Desk, Zoho Bigin, WooCommerce, WebHooks, Trello, Telegram, SendFox, Propovoice CRM, Moosend, and MailPoet. This can help you save time and effort, and improve your lead generation and customer management processes.

Action Hook Integration

First, Open your Bit Integration Dashboard and create an integration by clicking the “Create Integration” button.

Select the Action Hook you want to connect with Bit Integrations Actions.

Configure an Action Hook Using Kadence Blocks Form

Please select the “Hook” you wish to connect with Bit Integrations from the provided dropdown menu. For Example: “Kadence Blocks Form“ Next“

Once you’ve done that, simply click on the “Fetch” button.

Alright, let’s go to Kadence Blocks Form and submit your form. Once you’re done, just come back to the integration page, and you’ll see that your submitted form data has been successfully retrieved.

Now, search for the value you recently submitted, and then examine the values to be mapped while also establishing a primary key. A primary key serves as a unique identifier for your form.

To find your submitted value:

• Begin by clicking the + icon. This key action will guide you toward locating your submitted value.
• Look for a section or category labeled as “object.” There’s a strong possibility that your submitted value resides within this area.
• Carefully examine the contents within the “object” section.
• Once you pinpoint your specific submitted value, proceed to select it.

Choose your Unique Key:

• Navigate within the response to identify the specific form that requires a unique key assignment.
• Ensure the chosen key’s value remains constant and unchanging over time.
• Verify that the selected key unequivocally distinguishes each form entry from one another.
• In this specific instance, the form ID serves as a suitable unique key due to its inherent consistency and distinctiveness.

In some form builders, when you make a copy of a form, the original form and the duplicate form have the same form ID. In these cases, it’s a good idea to use the “PostID” as the unique identifier instead. Some form builders don’t have a “unique ID” or “PostID” feature. But don’t worry, there’s a solution! You can simply create a field and then hide it. Use this hidden field as a unique identifier. Now, set this unique identifier as the default value for the Unique Key. You have the freedom to set the default value however you like, but just remember that it needs to be unique. It’s a clever workaround that will do the trick.

Configure an Action Hook Using Custom Hook

Please select the “Hook” you wish to connect with Bit Integrations from the provided dropdown menu. For Example: “Custom Form“ Next“

Now, let’s enter your Hook! If you’re using Bit Form, simply use “bitform_submit_success” as the hook. If you need more hooks, you can find them on our “Trigger Hooks” page. It’s worth mentioning that these hooks are specifically designed for Bit Integrations. Then click on the “Fetch” Button.

Alright, let’s go to Bit Form and submit your form. Once you’re done, just come back to the integration page, and you’ll see that your submitted form data has been successfully retrieved.

Now, search for the value you recently submitted, and then examine the values to be mapped while also establishing a primary key. A primary key serves as a unique identifier for your form.

Find your submitted value:

• Begin by clicking the + icon. This key action will guide you toward locating your submitted value.
• Look for a section or category labeled as “object.” There’s a strong possibility that your submitted value resides within this area.
• Carefully examine the contents within the “object” section.
• Once you pinpoint your specific submitted value, proceed to select it.

Choose your Unique Key:

• Navigate within the response to identify the specific form that requires a unique key assignment.
• Ensure the chosen key’s value remains constant and unchanging over time.
• Verify that the selected key unequivocally distinguishes each form entry from one another.
• In this specific instance, the form ID serves as a suitable unique key due to its inherent consistency and distinctiveness.

In some form builders, when you make a copy of a form, the original form and the duplicate form have the same form ID. In these cases, it’s a good idea to use the “PostID” as the unique identifier instead. Some form builders don’t have a “unique ID” or “PostID” feature. But don’t worry, there’s a solution! You can simply create a field and then hide it. Use this hidden field as a unique identifier. Now, set this unique identifier as the default value for the Unique Key. You have the freedom to set the default value however you like, but just remember that it needs to be unique. It’s a clever workaround that will do the trick.