This template runs on a schedule. JavaScript or an HTTP request lists contacts created since the last run, with your 17hats API key in that node, then normalizes name and email. Mailchimp adds or updates each subscriber in the audience you choose. If 17hats can post, start from a webhook instead of the schedule.
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
The scenario starts on the interval you set, for example every 15 minutes.
JavaScript or an HTTP request lists new contacts from the 17hats API. Put the 17hats API key in that node.
JavaScript maps 17hats name and email into Mailchimp merge fields.
Mailchimp adds or updates each contact in the selected audience.
Put the 17hats API key in the JavaScript or HTTP node that calls 17hats. Confirm the list-contacts path against 17hats’s current API docs.
Add a Mailchimp connection. Choose the audience. Map email and merge fields from JavaScript, then add or update the subscriber.
Start on a schedule. Track last-sync time so you only send new contacts.
FAQ
More templates
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.
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.
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.
