If your platform has an HTTP / Webhook node, Vlozi works with no code. The whole API is one POST with a Bearer token.
n8n
1. Credentials → New → Header Auth
- Name:
Vlozi MCP - Header Name:
Authorization - Header Value:
Bearer ls_your_secret_key_here
2. Add an HTTP Request node:
| Field | Value |
|---|---|
| Method | POST |
| URL | https://mcp.vlozi.app/tools/blog.create_draft |
| Authentication | Predefined → Header Auth → Vlozi MCP |
| Send Body | JSON |
| Body | { "title": "{{ $json.title }}", "content": "{{ $json.body }}", "tags": ["from-n8n"] } |
The response's $json.data.post.id is the new post ID — pipe it into a follow-up node to publish.
Zapier
Action → Webhooks by Zapier → POST:
- URL:
https://mcp.vlozi.app/tools/blog.create_draft - Payload Type:
JSON - Headers:
Authorization:Bearer ls_your_secret_key_herecontent-type:application/jsonx-agent-id:zapier
- Data:
{ "title": "...", "content": "..." }(Zapier maps fields with{{ }})
A successful test returns { "data": { "post": { "id": "post_..." } } }.
Useful flow patterns
Auto-publish on a schedule
[Schedule trigger]
→ [LLM drafts post from changelog]
→ [HTTP POST /tools/blog.create_draft]
→ [HTTP POST /tools/blog.publish_post]Customer support knowledge bot
[Slack message webhook]
→ [HTTP POST /tools/brain.get_context — pass user's question as "topic"]
→ [LLM answers using returned context]
→ [Slack reply with cited sources]Cross-post on publish
[Vlozi webhook → blog.post.published]
→ [LLM rewrites for Twitter / LinkedIn / Threads]
→ [Buffer / Hypefury POST]Make.com follows the same pattern as Zapier — one HTTP module per tool call.