How do I connect Flint to Lodol?

Authenticate Flint once from your workspace and every action and trigger it supports becomes available to drop into a workflow. There is no glue code to write or maintain.

All integrations

Flint

Website BuildersMarketing Automation

Build and update landing pages with Flint's AI agent. Describe a change in plain English - add an About page, update every mention of the old price, rewrite the hero - and the agent reads your site and makes it. Or hand it a template page you already designed and a list of records, and it generates an on-brand page for each one: case studies, location pages, comparison pages, up to ten per step. Every task comes back with a preview link and an editor link for each page it touched, plus the live URL when you asked it to publish; nothing reaches your visitors unless you turn publishing on. Setup is two copies from one page: create an API key in your Flint team settings at https://app.tryflint.com/app/team and copy the Site ID listed there. That site is then used by every step, so no step ever asks for it again. Because Flint's agent works in the background, the Get task step waits for it and returns the finished pages, so a two-step workflow is all you need.

Get Started Browse all integrations

3 actions

Actions

Steps your workflow can run in Flint.

Create taskTell Flint's agent what to change on your site, in plain English, and it goes and does it - add a page, rewrite a section, update the pricing everywhere it appears. Returns a Task ID straight away; the work carries on in the background.

Generate pagesTurn a list of records into a set of on-brand pages, all built from one template page you already designed in Flint. Give it the template and one entry per page - a customer, a product, a city - and Flint writes each page's copy from the context you supply. Up to ten pages per step.

Get taskFollow a task and collect what it produced: every page created, modified or deleted, each with a preview link, an edit link and, when the task published, its live URL. Waits for the task to finish by default, so a Create task or Generate pages step followed by this one is a complete workflow. A task that fails comes back with its reason rather than erroring, so you can branch on it.