> ## Documentation Index
> Fetch the complete documentation index at: https://composio-preview.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Jan 7, 2026

> Latest updates and announcements

## Consistent Error Response Structure

Tool execution errors now return a standardized response format across all failure types. Previously, the `data` field was empty on errors—now it always includes `status_code` and `message`, matching the structure of successful responses.

## What Changed

All error responses from tool execution now include:

* `data.status_code`: HTTP status code (or `null` for non-HTTP errors)
* `data.message`: Detailed error message
* `error`: Same detailed message at the top level

## Before vs After

**Previous error response:**

```json theme={null}
{
  "data": {},
  "successfull": false,
  "error": "404 Client Error: Not Found for url: ...",
}
```

**New error response:**

```json theme={null}
{
  "data": {
      "http_error": "404 Client Error: Not Found for url: ...",
      "status_code": 404,
      "message": "Resource not found: The requested item does not exist"
  },
  "successfull": false,
  "error": "Resource not found: The requested item does not exist",
}
```

## Why This Matters

* **Easier parsing**: Agents and code can reliably access error details from `data.message` without special-casing empty `data` objects
* **Better debugging**: Detailed error messages replace generic HTTP error strings
* **Consistent schema**: Same response shape whether the tool succeeds or fails

***

## Union Types Preserved in Tool Schemas

Tool schemas now use standard JSON Schema `anyOf` for union types, providing accurate type information for LLMs and code generators.

## What Changed

Two changes affect how types appear in request/response schemas:

| Change | Scope | Description |
| - | - | - |
| **Nullable fields** | **All toolkits** | Fields that accept `null` now use `anyOf: [{type}, {type: "null"}]` instead of `type` + `nullable: true` |
| **Multi-type fields** | 157 toolkits | Fields accepting multiple value types (e.g., `string \| number`) preserve the full `anyOf` array instead of flattening to the first type |

> [accordion] Toolkits with multi-type union fields (157 total)
>
> **CRM & Sales:** active\_campaign, apollo, attio, autobound, capsule\_crm, firmao, forcemanager, gong, hubspot, instantly, intercom, kommo, leadfeeder, lever, magnetic, pipedrive, pipeline\_crm, salesforce, salesforce\_service\_cloud, zoominfo
>
> **Marketing & Email:** active\_trail, beamer, delighted, dripcel, enginemailer, mailerlite, moosend, mopinion, sendspark, toneden
>
> **Communication & Collaboration:** chmeetings, discord, helpdesk, helpwise, missive, slack, textit
>
> **Productivity & Project Management:** basecamp, clicksend, clientary, dart, fibery, monday, notion, onedesk, productboard, rocketlane, todoist
>
> **Developer Tools & APIs:** algolia, anonyflow, api\_ninjas, api\_sports, apify, appdrag, backendless, browserless, bubble, cloudconvert, cloudinary, cloudlayer, convertapi, databricks, datadog, datarobot, deepseek, deployhq, digital\_ocean, docmosis, docugenerate, encodian, gitea, gitlab, globalping, groqcloud, hookdeck, hyperbrowser, imgbb, imgix, kibana, neutrino, npm, openai, openrouter, parsera, parseur, phantombuster, pinecone, prismic, procfu, replicate, scrape\_do, serpapi, shotstack, snowflake, supabase, tavily, v0, vercel, writer, zenrows
>
> **E-commerce & Payments:** brex, btcpay\_server, coupa, flutterwave, gift\_up, lemon\_squeezy, quaderno, ramp, shopify, stripe, zoho\_invoice
>
> **HR & Recruiting:** ashby, bamboohr, recruitee
>
> **Data & Analytics:** amplitude, census\_bureau, college\_football\_data, currencyscoop, diffbot, ip2location, mixpanel, nasa, rosette\_text\_analytics, securitytrails, textrazor, twelve\_data
>
> **Documents & Files:** carbone, doc\_certs, documenso, dropbox, excel, files\_com, grist, pdf\_co, share\_point
>
> **Design & Media:** canva, canvas, claid\_ai, deepimage, heygen, metatextai
>
> **Customer Support:** freshdesk, retently, servicem8, sevdesk, storeganise
>
> **Calendar & Scheduling:** calendly, deadline\_funnel, etermin, googlecalendar
>
> **Social Media:** facebook, instagram, reddit
>
> **Location & Maps:** addresszen, geoapify, google\_maps, mapbox
>
> **Email Verification & Validation:** clearout, icypeas, neverbounce, zerobounce
>
> **Other Integrations:** bitwarden, canny, cardly, castingwords, confluence, formdesk, getform, habitica, headout, highergov, jira, keen\_io, landbot, moonclerk, one\_drive, outlook, googlesheets, resend, ritekit, sms\_alert, tapfiliate, thanks\_io, uptimerobot

## Before vs After

For example, the `GOOGLECALENDAR_GET_CURRENT_DATE_TIME` request schema changes: **Previous (only a single type):**

```json theme={null}
{
  "timezone": {
    "default": 0,
    "description": "Timezone specification...",
    "title": "Timezone",
    "type": "string"
  }
}
```

**Now (Union types preserved):**

```json theme={null}
{
  "timezone": {
    "anyOf": [
      { "type": "string" },
      { "type": "number" }
    ],
    "default": 0,
    "description": "Timezone specification...",
    "title": "Timezone"
  }
}
```

Similarly, nullable fields like `page_token` in `GOOGLECALENDAR_LIST_CALENDARS`:

**Previous:**

```json theme={null}
{
  "page_token": {
    "default": null,
    "description": "Token for the page of results to return...",
    "nullable": true,
    "title": "Page Token",
    "type": "string"
  }
}
```

**Now:**

```json theme={null}
{
  "page_token": {
    "anyOf": [
      { "type": "string" },
      { "type": "null" }
    ],
    "default": null,
    "description": "Token for the page of results to return...",
    "title": "Page Token"
  }
}
```

## Why This Matters

* **Accurate schemas**: LLMs and code generators see the full set of allowed types
* **Better validation**: Input validation can now correctly accept all valid types, not just the first one
