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 runs campaigns as Asana projects — each task is a content piece with custom fields for Content Type, Channel, Priority, and Due Date. You need a weekly status report that goes beyond “X tasks completed”: you want insight into velocity trends, bottleneck stages, and content mix analysis. This job pulls all tasks from a campaign project, analyzes the pipeline state, and sends it to Mave for a strategic status report. Flow: AsanaGET /projects/{id}/tasks → Aggregate by status/custom fields → Mavera POST /api/v1/mave/chat → Campaign status report
Code
Example Output
Error Handling
Rate limits (429)
Rate limits (429)
Free plans allow ~150 req/min. The code reads the
Retry-After header and waits. For large projects, use opt_fields to minimize response size and reduce call count.Custom fields not returned
Custom fields not returned
Custom fields only appear if you include them in
opt_fields. If a custom field name doesn’t match, check the exact name via GET /projects/{gid}/custom_field_settings.Task pagination
Task pagination
Projects with 100+ tasks require pagination. The code follows
next_page.offset automatically. Very large projects (1000+) should filter by modified_since to reduce data.Section membership
Section membership
Tasks can belong to multiple sections (if multi-homed). The code uses the first membership. For accurate pipeline views, filter by the primary project.