I already opened a GitHub issue here: https://github.com/ComposioHQ/composio/issues/3702 I'm trying to create a Todoist trigger instance for

TODOIST_NEW_TASK_CREATED

using the TypeScript SDK. Environment: - Node.js: v22.23.1 - OS: macOS - SDK:

@composio/core@0.13.0

- Environment: local development - Auth: Composio-managed OAuth - Connected Todoist account status: ACTIVE What is not working: Creating the trigger with an empty

triggerConfig: {}

fails, even though the trigger schema marks config fields as optional. Steps: 1. Connect Todoist through Composio-managed OAuth. 2. Confirm the connected account is ACTIVE. 3. Call

composio.triggers.create(...)

for

TODOIST_NEW_TASK_CREATED

. 4. Pass

triggerConfig: {}

. 5. The request fails with 400. 6. Calling the REST endpoint directly fails the same way. Error:

TriggerInstance_PollingConfigInvalid: 'str' object has no attribute 'get'

I also tested: - empty config - config with interval - latest toolkit version - explicit Todoist toolkit version - without toolkit_versions - without user_id The same polling config error appears, so it looks specific to internal handling of this trigger rather than only the SDK wrapper.

Hi there, Thanks for the detailed report, and for opening the GitHub issue. Your analysis is right, this isn't caused by your configuration. For

TODOIST_NEW_TASK_CREATED

, both config fields are optional, so an empty

triggerConfig: {}

is valid. The failure is on our side, in the server-side polling logic for this specific trigger, which is why it happens regardless of the config, interval, toolkit version, or whether you go through the SDK or REST. The

'str' object has no attribute 'get'

error comes from how that handler reads Todoist's response. There's no config change you can make to get around it for now. We've confirmed it on our side and logged it internally, though I don't have a timeline to share yet. I'll keep the GitHub issue as the place to track it, and feel free to reply here if anything else comes up. This response was generated automatically by Composio's AI support agent. If it doesn't fully resolve your issue, or you'd like to speak with a person, just reply here and a member of our team will take a look.

@Abhishek i saw someone from the team picked up my issue on gh, any idea when a fix might be ready?

I don't have a fix timeline to share yet. The GitHub issue (#3702) is the best place to track this, since any progress or a fix will be posted there. This is a response from Composio's Support Agent. If it doesn't fully resolve your issue, feel free to reply here.