Community — TSANet Connect Developer Hub

Routing

What Goes Where

If you want to…	Go to
Report a bug or request a feature in a shipped connector	That connector's issue tracker — see below
Get API credentials, a Beta account, or early access	membership@tsanet.org
Arrange attachment enablement or a pilot instance	membership@tsanet.org
Tell us which connector to build next	Wish List
Report something wrong or missing on this hub	membership@tsanet.org or Q&A
Ask the community how to do something	Q&A
Show what you built	Show and tell

The short version: anything about a specific shipped connector goes to that connector's repository, where the maintainers and the history already are. Anything involving credentials or account changes goes to membership — a discussion thread is public, and credentials never should be. Everything else has a discussion category below.

Open today

Connector Issue Trackers

Each shipped connector is developed in the open, with a public issue tracker. This is the fastest route for anything specific: a bug, a behaviour that surprised you, a feature you need. The history is there too, so it is worth searching before filing — most surprising behaviours have been hit before.

Connector	Repository	Use it for
Salesforce	tsanetgit/SFDC_App	Managed package, flows, Apex, LWC
Zendesk	tsanetgit/Zendesk_App	ZAF app, ZIS bundle, field actions
Dynamics	tsanetgit/MS_Power_App	Solution, plugins, Power Automate flows
Connect SDK	tsanetgit/Connect_SDK	Java client, console app, attachment receiver

Fin / Intercom, the Connect Gateway and ServiceNow have no public tracker — the first two are private repositories during early access, with access granted at onboarding, and the third is not built. Route all three through membership.

What makes a report easy to act on

Which environment. Beta and Production behave differently often enough that it is the first question anyone will ask.
The case token, if there is one. It keys everything on the platform side and turns a description into something reproducible.
What you expected versus what happened. Several behaviours look like bugs and are not — a Connect case that cannot be closed while OPEN, Intercom returning 200 on fields it silently ignores, ServiceNow journal fields that read back empty. The API guidance and the connector pages cover the ones we know about.
Whether it is reproducible. A one-off during a deploy window is a different problem from something that happens every time.

Open now

Discussion Categories

Discussion runs in the tsanetgit organisation Discussions — one shared space for every TSANet repository, no separate accounts, no separate platform; a GitHub account is all it takes. The space is young: an empty category is an invitation, not a dead room, and early questions shape what the maintainers write next.

Q&Aanswerable

How do I do this? Auth, process forms, lifecycle transitions, webhook delivery. Answers can be marked, so the next person with the same question finds it.

Troubleshootinganswerable

Something is not working. Silent failures, signature mismatches, a sync that stopped. Distinct from Q&A because the useful answer is usually a diagnosis rather than an explanation.

Show and tell

What you built. Custom integrations, translation services, platform findings — including the unflattering ones, which are usually the most useful.

Wish List

Which connector should exist next, and what platform your team actually runs on. This is the one that most directly changes what gets built.

Membershipanswerable

Onboarding, pilot instances and early-access programmes. Anything involving actual credentials still goes to membership@tsanet.org — threads here are public.

Technology Committee

Ideas and proposals, in both directions. Changes you want to the API or the connectors: gaps, papercuts, and behaviour that surprised you enough to be worth changing rather than documenting. And requests for member input from the TSANet Technology Committee: connector roadmaps, feature proposals, and platform-wide behaviour questions such as note formatting and inline images.

Announcements

Maintainer posts only: connector releases, API changes, and the deprecation dates worth knowing about in advance.

Browse the discussions

This site

Corrections Are the Most Valuable Thing You Can Send

Much of what is on this hub was assembled from connector source, platform specifications and live probes rather than from a maintained document. That makes it useful and it also makes it fallible — and some of it is already known to be inconsistent at the source.

If a page contradicts what you observe in production, the page is more likely wrong than you are. Send it.
If two things on this hub disagree with each other, that is worth reporting even without knowing which is right.
If a documented gotcha no longer reproduces, that is just as useful — behaviours get fixed and pages go stale.

Every page states what it was verified against, and when. Start there when judging whether to trust something.
Where two sources genuinely disagree, pages say so rather than picking one quietly — the webhook retry policy is the current example.
Assessments carry evidence tags: documented means somebody read it, not that anybody saw it work.

Send a correction Or raise it in Q&A