I already opened a GitHub issue here: https://github.com/ComposioHQ/composio/issues/3690 I'm trying to use the Firmao connector through the TypeScript SDK. Environment: - Node.js - OS: macOS - SDK:

@composio/core@0.10.0

- Environment: local development - Auth: Firmao Basic Auth credentials configured in Composio What is not working: The Firmao connector asks for: -

subdomain

-

basic_encoded

But when executing Firmao tools, the generated API endpoint appears to omit the Firmao organization id / subdomain. Firmao expects URLs like:

https://system.firmao.pl/{subdomain}/svc/v1/{object}

Steps: 1. Create/connect a Firmao account in Composio. 2. Provide a valid Firmao subdomain and Basic Auth value. 3. Execute a tool like

FIRMAO_LIST_TASKS

. 4. The tool fails / does not return expected data. 5. The same credentials work when calling Firmao directly with the correct URL containing the subdomain. Expected: Composio should include the configured Firmao subdomain in the constructed endpoint. Actual: The request appears to be built without the organization id / subdomain.

Hi there, Thanks for the detailed write-up and the GitHub issue, that helped a lot. You've actually found a real bug on our side, just with a slightly different root cause than it first looks. The subdomain isn't being dropped. Our Firmao connector does include it, but it hardcodes the host to

system.firmao.net

, so the request goes to

https://system.firmao.net/{subdomain}/svc/v1/...

. Your account looks like it lives on the Polish regional host

system.firmao.pl

, which the connector currently can't reach, and on top of that

FIRMAO_LIST_TASKS

returns an empty result instead of a clear error when the call fails, which is why it looks like a silent "no data." Can you confirm your Firmao account URL is on

system.firmao.pl

? Assuming so, there's unfortunately no setting to override the host today, so there isn't a clean self-serve workaround yet. We've confirmed this internally and logged it. I don't have a timeline to share, but reply here if anything changes on your end or you spot more detail and we'll keep it attached to this. 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.

i confirm my urls is .pl

Thanks for confirming, that matches what we found. Your account is on the Polish regional host

system.firmao.pl

, and our Firmao connector currently builds every request against

system.firmao.net

(the subdomain itself is included, it's the host that's fixed), so the calls can't reach your account. On top of that,

FIRMAO_LIST_TASKS

returns an empty result instead of a clear error when the request fails, which is why it looks like a silent "no data." There's no field to override the host today, so there isn't a clean self-serve workaround yet. We've confirmed this on our side and logged it internally alongside your GitHub issue. I don't have a timeline to share, but reply here if anything changes on your end and we'll keep it attached to this.

@Abhishek any info on this? I have a few clients who would like to use Firmao but can't

hey, sorry about the blocker. We're tracking this internally. Right now the Firmao API host is fixed in the connector and can't be changed when creating a connection. We're adding a connection-level host/region field so you can select the correct Firmao endpoint, such as

system.firmao.pl

, while connecting. I'll follow up here once that's available.