AI SEO blog for Lovable
Blogent ships an official workspace skill for Lovable. The ZIP contains the database migration, a protected Edge Function, image storage, a typed frontend adapter and tests, so running one command inside the project sets up publishing end to end.
How to connect Blogent to Lovable
Lovable autopublishing
Install the official Blogent workspace skill for Lovable. The ZIP includes the database migration, protected Edge Function, image storage, frontend adapter, and tests.
-
Download the integration ZIP. In Lovable open Settings → Skills → Add → Upload ZIP and upload it.
-
Run
/blogent-integrationin the target project. When Lovable opens Add API Key, enter the generated secret shown below. -
Copy the verified Edge Function URL into Blogent with X-Blogent-Token, then test existing inventory and creation/update of the same real article.
Actions and stable identities
- Shopify, HubSpot, Webflow and Framer use the connected native publisher. WordPress, OpenCart, Strapi and Lovable use the installed Blogent connector; v0 and Replit adapt it to the existing app. Wix, Make, n8n and custom endpoints implement the synchronous contract; Zapier, Albato and ApiX-Drive use completion callbacks.
inventory: sendcursor: nullandlimit; return{articles: [snapshot], next_cursor: string|null}. Repeat the returned cursor until null.read: sendtargetand/orcontent_id; return{article_snapshot: snapshot}. Explicit nativetargetis authoritative. Blogent’s logicalcontent_idmay differ from the native identity.- Each snapshot contains
identity, title, alias, date, article, target, revision, urlsand optional image/author metadata.articlemaps locales to full title, alias, HTML, preview and SEO fields. Unknown original dates may be null and unavailable URLs may be an empty map. create: send the article payload, a uniqueoperation_id, logicalcontent_id, empty target and null expected revision. Return{posted:true,target,revision,urls}after complete publication.update: send existing native target IDs and the latestexpected_revision. Preserve original IDs, URLs/aliases, publication date, author and assets. Compare the revision atomically before applying changes.
Blogent supports inventory, authenticated read, create and in-place update. Final receipts include native target IDs and revision; queued workflows complete through authenticated callbacks.
Webhook tester
Run inventory, create, read and update on one real test article. Queued integrations wait for their completion callbacks.
What you get after connecting Lovable
- One ZIP covers the whole stack: migration, Edge Function, image storage, frontend adapter and tests.
- The connection secret is generated locally in your browser and entered through Lovable’s own Add API Key form, so it never travels through a chat message.
- The Edge Function is protected by the
X-Blogent-Tokenheader carrying that same secret. - Images are stored by your project rather than linked from a temporary URL.
- Blogent reads existing native articles and updates them with revision checks while preserving original IDs, URLs, dates, authors and assets.
Requirements and compatibility
- Platform
- A Lovable project you can add a workspace skill to.
- Install
- Settings → Skills → Add → Upload ZIP, then run
/blogent-integrationin the target project. - Secret
- A 48-character connection secret, generated in your browser and entered through Lovable’s Add API Key form.
- Connection
- The verified Edge Function URL plus the
X-Blogent-Tokenheader, entered in Blogent. - Verification
- The connection test inventories existing content, creates one real article, reads its authenticated snapshot and updates the same native IDs. No public-page crawl is required.
Frequently asked questions about the Lovable integration
What exactly does the skill install?
The database migration, a protected Edge Function, image storage, a typed frontend adapter and tests.
Where do I put the connection secret?
Only into Lovable’s Add API Key form when it opens. The same value then goes into Blogent as the X-Blogent-Token header. Do not paste it into chat.
Is the secret generated on your servers?
No. It is generated locally in your browser.
Do I need to build the blog frontend myself?
The package includes a typed frontend adapter, so the stored articles can be read by your app without writing the data layer from scratch.