Skip to main content

75+ More Toolkits Get Typed Responses & Consistent Response Schema Wrapping

We’ve expanded typed response coverage to 75+ additional toolkits. In total, over 130 toolkits now return strongly typed response objects. Additionally, we’ve standardized response schema wrapping so that all action responses consistently nest their output under a top-level data field.
Breaking Change for latest VersionTwo breaking changes ship in this release:
  1. Newly typed toolkits — If your code depends on the old response_data structure for any of the 75+ newly typed toolkits listed below, you’ll need to update your code to work with the new typed response schemas.
  2. Consistent response wrapping — Actions that previously had data at the root level of their response schema now wrap the entire response under a data field. See the migration guide below.

Consistent Response Schema Wrapping

Previously, actions whose response schema already contained a data field at the root level would surface all fields (including data) alongside successful and error at the top level. Now, all action responses are uniformly wrapped: the full response object is nested inside a data field, with successful and error at the top level.

Affected: Toolkits with data in their response model (e.g., Pipedrive PIPEDRIVE_LIST_UPDATES_ABOUT_A_DEAL)

These actions had a data field in their original response schema. Previously, those fields were spread at the root level alongside successful and error. Now, they are nested under a top-level data field. Before:
After:
If your code accesses fields directly at the root level (e.g., result["data"]), update it to access them under result["data"]["data"] instead.

Not affected: Toolkits without data in their response model (e.g., GitHub GITHUB_GET_THE_LATEST_RELEASE)

These actions never had a data field in their original response schema, so their wrapping behavior is unchanged. The response fields are nested under data as before.
No migration needed for these toolkits.
abuselpdb, active_campaign, active_trail, adyntel, affinda, agentql, agenty, agiled, alpha_vantage, ambee, amcards, amplitude, anchor_browser, anthropic_administrator, api_bible, api_labz, apify, apipie_ai, apiverve, appcircle, asana, attio, bamboohr, beaconchain, beaconstac, benchmark_email, benzinga, better_proposals, better_stack, bigpicture_io, bitbucket, bitquery, blackbaud, boloforms, brightdata, browseai, browserless, byteforms, cal, calendarhero, callerapi, callingly, callpage, canvas, carbone, cardly, census_bureau, certifier, chaser, claid_ai, clearout, clickhouse, clicksend, close, cloudcart, cloudconvert, cloudinary, cloudlayer, codemagic, cody, coinbase, coinmarketcal, coinmarketcap, coinranking, connecteam, contentful_graphql, corrently, crowdin, cults, customerio, customgpt, databricks, datagma, datarobot, deepimage, deepseek, demio, dialmycalls, diffbot, dnsfilter, dock_certs, docsumo, documenso, documint, docupilot, docupost, docuseal, dotsimple, dovetail, dripcel, dromo, dropcontact, emailoctopus, emelia, endorsal, enigma, esignatures_io, esputnik, etermin, eversign, exa, faceup, fibery, figma, files_com, finage, findymail, fireberry, firecrawl, fireflies, firmao, flutterwave, fluxguard, folk, forcemanager, formbricks, freshdesk, gamma, gan_ai, getform, giphy, github, givebutter, gleap, goody, googlesheets, gosquared, groqcloud, gtmetrix, habitica, headout, helpwise, heygen, hookdeck, hotspotsystem, html_to_image, hunter, hyperbrowser, icypeas, imgbb, imgix, insighto_ai, instagram, instantly, intelliprint, intercom, ip2location, iqair_airvisual, jobnimbus, junglescout, kadoa, kaggle, kibana, klaviyo, klipfolio, ko_fi, laposta, leadfeeder, leiga, lemon_squeezy, lever, linear, listclean, lodgify, loops_so, mailcoach, mailerlite, mailersend, mails_so, mapulus, melo, memberspot, memberstack, metaads, metabase, minerstat, miro, mistral_ai, monday, moneybird, msg91, multionai, mx_toolbox, nango, needle, nextdns, omnisend, openai, openrouter, paradym, passcreator, pdfless, peopledatalabs, perigon, persistiq, phantombuster, piggy, pilvio, pinecone, pipedrive, placid, plain, plisio, polygon, postgrid, postgrid_verify, postman, prisma, productboard, promptmate_io, proofly, proxiedmail, pushbullet, rafflys, raisely, ramp, reddit, refiner, remarkety, remote_retrieval, remove_bg, reply, reply_io, resend, respond_io, retailed, retently, rocket_reach, rocketlane, rootly, satismeter, scrapfly, segment, semrush, sendbird, sendfox, sendlane, sendloop, shopify, shotstack, signaturely, simple_analytics, skyfire, slack, smtp2go, snowflake, snowflake_basic, sourcegraph, stannp, statuscake, stormglass_io, stripe, survey_monkey, svix, sympla, telnyx, teltel, textcortex, textrazor, thanks_io, tiktok, timelinesai, toggl, token_metrics, tomba, tripadvisor, tripadvisor_content_api, truvera, twelve_data, v0, vercel, verifiedemail, virustotal, wakatime, whatsapp, workday, wrike, writer, yelp, ynab, zoho, zoho_bigin, zoho_mail

75+ Newly Typed Response Toolkits

All outputs for these toolkits now return strongly typed objects with clear field documentation instead of generic response_data blobs. Combined with the 60+ toolkits typed in the previous release, over 130 toolkits now have typed responses.

Developer & DevOps

bitquery, docusign, hookdeck, metabase, neon, parsera, postgrid, sentry, servicenow

Communication & Collaboration

dailybot, dialpad, gleap, gong, googlemeet, retellai, smtp2go

CRM & Business

bamboohr, coupa, forcemanager, lever, mixpanel, monday, okta, peopledatalabs, pipedrive, productboard, workday

Marketing & Analytics

amplitude, datagma, diffbot, lemlist, mailerlite, posthog, remarkety, resend, retently, sendgrid

AI & Automation

bolna, multionai

Media & Entertainment

giphy, soundcloud, spotify, spotlightr

Real Estate & Location

acculynx, apaleo, foursquare, foursquare_v1, foursquare_v2, hotspotsystem

E-commerce & Payments

moneybird, open_sea, plisio, zoho_inventory

Education & Learning

blackboard, canvas, d2lbrightspace, habitica

Project Management

pagerduty, shortcut, taskade, wrike, workspace

Productivity & Personal

borneo, box, cal, etermin, formdesk, google_admin, junglescout, klipfolio, onepage, strava, typefully, wakatime, zenrows, zoho, zoho_mail

Other

semanticscholar

Webhook Subscriptions API & Connection Expiry Events

A new API for managing webhook configurations with event filtering, HMAC signature verification, and support for platform lifecycle events. This replaces the legacy project-level webhook settings with a more flexible, subscription-based model.

Summary


API Overview

See the Webhook Subscriptions API Reference for complete details.

Endpoints

Key Capabilities

  • Event filtering: Subscribe only to events you need
  • HMAC-SHA256 signatures: Every webhook includes a cryptographic signature for verification
  • Secret rotation: Rotate signing secrets on demand

Creating a Subscription

Response:
The secret is only returned once at creation time or when rotated. Store it securely for signature verification.

Notes

  • 1 subscription per project: Currently limited to one webhook subscription per project. This will be expanded in future releases.
  • HTTPS required: Webhook URLs must use HTTPS in production environments.

New Event: composio.connected_account.expired

A new platform event that notifies you when an OAuth2 connected account’s authentication expires and cannot be automatically refreshed.
This event is only available in V3 format. We strongly recommend using V3 for all new integrations to access the latest features and follow standard webhook practices.

Use Cases

  • Prompt users to re-authenticate before workflows fail
  • Track connection health across your user base
  • Automate re-connection flows
  • Build proactive notification systems

Subscribing to Connection Expiry Events

Payload Structure

The composio.connected_account.expired event follows the V3 envelope format:
The data object matches the response from GET /api/v3/connected_accounts/{id}, making it easy to process with existing code and SDK types.

Verifying Webhook Signatures

All webhooks include an HMAC signature in the webhook-signature header. Use the SDK’s built-in verification functions or see the Triggers documentation for implementation details.

Available Event Types

Query available events and their version compatibility:

Deprecations

Deprecated Endpoints

The following legacy endpoints are deprecated and will be removed in a future release:

Deprecated Fields in Project Response


Backward Compatibility

No immediate action required. Your existing webhook configurations will continue to work.

What We’ve Done For You

  • Automatic migration: We’ve created a webhook subscription for all existing projects that had webhook URLs configured, with composio.trigger.message enabled by default
  • Same payload format: If you were using V1, V2, or V3 triggers, they continue with the same format

What Continues to Work

  • Legacy webhook endpoints (deprecated but functional)
  • Existing project webhook configurations
  • All existing trigger payload formats (V1, V2, V3)
  • Signature verification with your existing secret

Payload Version Comparison