How to connect Booqable and Mailhook
Create a New Scenario to Connect Booqable and Mailhook
In the workspace, click the “Create New Scenario” button.

Add the First Step
Add the first node – a trigger that will initiate the scenario when it receives the required event. Triggers can be scheduled, called by a Booqable, triggered by another scenario, or executed manually (for testing purposes). In most cases, Booqable or Mailhook will be your first step. To do this, click "Choose an app," find Booqable or Mailhook, and select the appropriate trigger to start the scenario.

Add the Booqable Node
Select the Booqable node from the app selection panel on the right.


Booqable

Configure the Booqable
Click on the Booqable node to configure it. You can modify the Booqable URL and choose between DEV and PROD versions. You can also copy it for use in further automations.
Add the Mailhook Node
Next, click the plus (+) icon on the Booqable node, select Mailhook from the list of available apps, and choose the action you need from the list of nodes within Mailhook.


Booqable
⚙
Mailhook

Authenticate Mailhook
Now, click the Mailhook node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Mailhook settings. Authentication allows you to use Mailhook through Latenode.
Configure the Booqable and Mailhook Nodes
Next, configure the nodes by filling in the required parameters according to your logic. Fields marked with a red asterisk (*) are mandatory.
Set Up the Booqable and Mailhook Integration
Use various Latenode nodes to transform data and enhance your integration:
- Branching: Create multiple branches within the scenario to handle complex logic.
- Merging: Combine different node branches into one, passing data through it.
- Plug n Play Nodes: Use nodes that don’t require account credentials.
- Ask AI: Use the GPT-powered option to add AI capabilities to any node.
- Wait: Set waiting times, either for intervals or until specific dates.
- Sub-scenarios (Nodules): Create sub-scenarios that are encapsulated in a single node.
- Iteration: Process arrays of data when needed.
- Code: Write custom code or ask our AI assistant to do it for you.

JavaScript
⚙
AI Anthropic Claude 3
⚙
Mailhook
Trigger on Webhook
⚙

Booqable
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring Booqable, Mailhook, and any additional nodes, don’t forget to save the scenario and click "Deploy." Activating the scenario ensures it will run automatically whenever the trigger node receives input or a condition is met. By default, all newly created scenarios are deactivated.
Test the Scenario
Run the scenario by clicking “Run once” and triggering an event to check if the Booqable and Mailhook integration works as expected. Depending on your setup, data should flow between Booqable and Mailhook (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect Booqable and Mailhook
Booqable + Mailhook + Slack: When a new rental order is created in Booqable, Mailhook receives the order details. Mailhook then triggers a message to be sent to a specified Slack channel, notifying the team of the new booking.
Booqable + Mailhook + Google Sheets: When a new rental order is created in Booqable, Mailhook receives the booking details. The Mailhook trigger then sends this data to Google Sheets, where a new row is added to log the booking information for reporting purposes.
Booqable and Mailhook integration alternatives

About Booqable
Automate equipment rental workflows with Booqable in Latenode. Create flows to update inventory, trigger notifications, or manage customer data based on rental events. Sync data across platforms, like accounting or CRM, without manual updates. Use Latenode's visual editor and flexible logic to streamline booking processes and reporting.
Similar apps
Related categories
About Mailhook
Use Mailhook in Latenode to instantly capture incoming emails and parse their contents into usable data. Trigger workflows on specific email events, like form submissions or order confirmations. Route parsed data to other apps, databases, or AI models for advanced processing. Automate email handling without code and scale as needed.
Similar apps
Related categories
See how Latenode works
FAQ Booqable and Mailhook
How can I connect my Booqable account to Mailhook using Latenode?
To connect your Booqable account to Mailhook on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select Booqable and click on "Connect".
- Authenticate your Booqable and Mailhook accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I send order confirmations from Booqable via Mailhook?
Yes, you can! Latenode enables automated workflows to send custom order confirmations from Booqable through Mailhook, ensuring prompt and personalized customer communication.
What types of tasks can I perform by integrating Booqable with Mailhook?
Integrating Booqable with Mailhook allows you to perform various tasks, including:
- Automatically sending email updates when new products are added to Booqable.
- Triggering personalized email campaigns based on rental order status changes.
- Sending SMS notifications via Mailhook for upcoming rental return reminders.
- Creating customer segments in Mailhook based on Booqable rental history.
- Updating Mailhook subscriber lists with new Booqable customer information.
What Booqable data can I access within Latenode workflows?
Latenode gives access to customers, rentals, products, and availability details, enabling powerful, data-driven automations.
Are there any limitations to the Booqable and Mailhook integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex Booqable queries with multiple filters may require custom JavaScript.
- Mailhook's API rate limits may affect high-volume notification workflows.
- Advanced Booqable product options might need custom data mapping.