Latenode
Webhook
JavaScript
Flodesk

Automatically add HoneyBook inquiries to a Flodesk email list

This template takes each new HoneyBook inquiry, reads email and name in JavaScript, and creates or updates the subscriber in Flodesk.

Point the HoneyBook inquiry webhook at Latenode. Connect Flodesk and put the Flodesk API key on that connection. If you pull inquiries over HTTP instead of a webhook, store the HoneyBook API key in the JavaScript node.

Updated Sep 16, 2026Est. run: 6sEst. cost: $0.0003
How Latenode estimates time and cost

Latenode bills workflow runtime in CPU seconds. The first 10,000 CPU seconds are free each month, then usage follows pay-as-you-go CPU-second pricing. Plug-and-Play (PnP) AI nodes are billed separately—each PnP token is $1 USD, charged pay-as-you-go at vendor cost plus a small processing fee, with no API keys required.

Full pricing — how CPU seconds work →

Workflow preview

What this template does

  • Adds Flodesk subscribers when a HoneyBook inquiry lands
  • Reads email and name in JavaScript
  • Creates or updates the Flodesk profile on email
  • Keeps the Flodesk API key on the Flodesk connection

How it works

1
Trigger

Receive the inquiry

The scenario starts when HoneyBook posts a new inquiry to your webhook URL.

2
Logic

Read the contact

JavaScript pulls email, name, and inquiry details from the payload.

3
Action

Add to Flodesk

Flodesk creates or updates the subscriber and adds them to the segment you choose.

Setup guide

1

Add a webhook trigger

Add a webhook trigger and copy its URL. In HoneyBook, send new-inquiry notifications to that URL.

2

Connect Flodesk

Add a Flodesk connection and paste your Flodesk API key there.

3

Map and subscribe

In JavaScript, read email and name, then create or update the Flodesk subscriber. Add the person to the segment you use for new inquiries. Send a test inquiry and confirm Flodesk shows the contact.

Requirements

A HoneyBook account that can send an inquiry webhook
A Flodesk account and API key stored on the Flodesk connection
Agreement on which payload fields are email and name

FAQ

Common questions about this template

Each run uses credits on your Latenode plan. We charge for processing time (1 credit = 30 seconds). Your actual cost depends on your plan and how long the run takes. See pricing plans for plans and how credits work.
Contact support →

More templates

You might also like

Browse all templates →

Site monitor to RSS

This template runs on a schedule, opens each URL in a headless browser, and compares visible text to the last snapshot in Latenode Database. When the change crosses your threshold, JavaScript builds RSS XML and Google Drive saves the feed file. Connect Google Drive. Keep snapshots in Latenode Database keyed by URL.

9s$0.0006

Sync Cognito Forms leads to ActiveCampaign with smart tagging

This template receives Cognito Forms submissions on a Latenode webhook, maps the payload, then creates or updates the contact in ActiveCampaign and applies a tag. Paste the webhook URL into Cognito Forms. Connect ActiveCampaign and put the API URL and key on that connection. Map email so matches update the same person.

13s$0.0008

Automatically translate new Discord messages using Google Cloud Translate

This template watches a Discord channel for new messages, translates the text with Google Cloud Translate, and posts the translation back to Discord. Connect a Discord bot and Google Cloud Translate. Put the Translate API key on the Google Cloud Translate connection. Point the trigger at the channel you want to translate and pick the target language.

8s$0.0005