Typed Responses Across Toolkits
We’ve updated many toolkits so their outputs are now strongly typed objects instead of a genericresponse_data blob, meaning tools like Outlook, HubSpot, Notion, etc. now return well-shaped, documented fields you can rely on directly in your code and agents. These improvements apply to the latest toolkit versions—see our toolkit versioning docs for how versions are managed.
Why This Matters
- Better developer experience for direct execute: clear fields and types
- Improved agent performance: flatter output shapes with explicit fields reduce nesting and invalid params
- Clearer docs and type safety: richer metadata for IDEs and autocomplete
Impacted Toolkits (57 total)
Impacted Toolkits (57 total)
Communication & Collaboration
discordbot, microsoft_teams, slack, zoomCRM & Sales
apollo, attio, hubspot, instantly, intercom, kommo, salesforceProductivity & Docs
coda, confluence, googledocs, googletasks, notion, todoistMarketing & Social Media
facebook, instagram, klaviyo, linkedin, metaads, reddit, tiktokE-commerce & Payments
brex, quickbooks, ramp, shopify, square, stripe, xeroProject Management
clickup, linearDesign & Creative
canva, figmaData & Analytics
ahrefs, airtable, apify, exa, pplx, serpapi, tavilyEmail & Calendar
calendly, outlookStorage & Files
one_driveWeb Tools
firecrawl, fireflies, google_maps, google_search_consoleAI & Media
elevenlabs, heygen, lmnt, mem0Customer Support
freshdesk, zendeskVideo & Content
youtubeBefore vs After
Previous (generic, version20251202_00):
20251209_00):
dashboard.composio.dev → Toolkits → List Messages (or the relevant tool).
Migration Notes
- Breaking change for consumers on the
latestversion who post-process the old nestedresponse_datashape: outputs are now flattened and explicitly typed. - New and modified fields include richer descriptions and examples; some legacy placeholders were removed.
- Re-fetch schemas for your tool/version to see the typed definitions. Use the toolkit view in
dashboard.composio.devfor authoritative field details.
Removal of label query parameter from connected accounts API
Thelabel query parameter has been removed from the GET /api/v3/connected_accounts endpoint.
What’s changing?
Thelabel query parameter is no longer supported when listing connected accounts. This parameter was previously accepted but had no functional behavior since label ingestion was removed in an earlier update.
Impact
None - This is a cleanup change. Thelabel query parameter was not performing any filtering since the underlying label ingestion functionality was already removed. If your code was passing this parameter, it was being silently ignored.
Migration
No action required. If your code was passing thelabel query parameter, you can safely remove it from your API calls.
Enhanced Security Masking for Sensitive Fields
We’ve improved the security masking forREDACTED fields in the following APIs:
What’s Changed: Sensitive fields are now partially masked, revealing only the first 4 characters to help with debugging while maintaining security.
Example:
Disabling Masking
If you need to disable masking for your use case, you have two options:- Via UI: Navigate to Project Settings → Configuration tab and update the masking settings
- Via API: Use the Patch Project Config API