Documentation Index
Fetch the complete documentation index at: https://docs.mavera.io/llms.txt
Use this file to discover all available pages before exploring further.
Scenario
Your marketing team maintains a Notion content calendar database with columns like Title, Status, Content Type, Target Persona, and Publish Date. Planned pieces sit in “Idea” or “Outlined” status with no draft. This job queries the database for upcoming content, then calls Mavera’s Generate endpoint for each piece — producing first drafts at scale that match your existing brand voice. Flow: NotionPOST /databases/{id}/query (filter: status = “Planned”) → For each row → Mavera POST /api/v1/generations (with brand_voice_id) → Draft content attached back as Notion page
Code
Example Output
Error Handling
Database not shared with integration
Database not shared with integration
Property name mismatch
Property name mismatch
Notion property names are case-sensitive. If
Status is actually status or Content Status in your database, the filter returns zero results. Use GET /databases/{id} to inspect property names.Rate limit (3 req/sec)
Rate limit (3 req/sec)
The loop includes a 500ms delay. For calendars with 50+ pieces, add exponential backoff on 429 or batch into runs of 10.
Block content limit
Block content limit
Notion limits
rich_text content to 2000 characters per block. The code chunks long paragraphs. Append requests are limited to 100 blocks per call.