Hub / Topics

Topics

Write-ups that cut across connectors rather than belonging to one. Each is grounded in what the shipped integrations actually do — which is also why there are only seven of them.

Published 7 Standard Grounded in shipped work

Published

Seven Topics

Two Ways to Build a Connector

One question about your platform — will it run your code inside the member's tenant? — decides who operates the integration, where credentials live, whether connector faults are independent or correlated, and whether shipping a fix means asking every member to upgrade. The taxonomy behind every connector on this hub, plus a four-question procedure for a platform that is not on it yet.

In-tenant · Salesforce, Dynamics Partial · Zendesk Gateway · Fin / Intercom Undecided · ServiceNow
Read the topic →

Deciding What to Accept Automatically

Three of the four shipped connectors can accept inbound cases without an agent, the fourth refuses to, and they disagree completely about when that is wise. Accepting stops the SLA clock and tells a partner an engineer is engaged — so a false acceptance is worse for them than an honest breach. Four shipping postures, and how to build a rule that asserts something actually true.

Accept everything · Zendesk Match existing work · Dynamics Verify entitlement · Salesforce Human commits · Fin / Intercom
Read the topic →

Moving Files Between Members

A file attached to a collaboration case is delivered into the receiving member's own file store — not parked on a portal. The sender never learns how the receiver stores files, which is exactly what makes the system extensible. How sending works, what the normalized receiving contract requires, the five decisions every receiving member makes, and the sharp edges around one-attempt delivery.

Live · normalized HTTPS push Sending · connector, SDK, or REST Pattern · endpoint fronting object storage Alpha · direct-to-storage delivery
Read the topic →

Agentic Usage with TSANet Connect

Working on Connect with an AI agent rather than by hand, whichever provider's agent it is. The four skills TSANet ships and how any assistant loads them, the assistant embedded in this hub and the recipe for the Copilot Studio agent behind it, what every provider's framework needs from the API — and the auth gap that separates hosted builders from code-first ones — plus a documented-only assessment of Copilot Studio with Claude.

Shipped · four agent skills Shipped · the hub assistant launcher Assessed · Copilot Studio Compared · Anthropic, Microsoft, OpenAI, Google
Read the topic →

End-to-End Encryption of Case Content

Case text that only the two members on the case can read: the sending connector encrypts and signs it, the receiving connector verifies and decrypts it, and the platform stores it without holding a key. The two API fields that carry it, how the first implementation, a proof of concept, encrypts and signs, where every connector stands (the SDK and the gateway engine now implement it too), and the platform behaviour that currently breaks the signature.

Live · manifest + encrypted on every environment PoC · Dynamics Not yet · SDK, Gateway Open · sanitizer rewrites ciphertext
Read the topic →

Hosting an SDK Integration in Your Own Cloud

The SDK is a library, so hosting an SDK solution means hosting whatever you wrapped around it, and everything that embeds it shares one runtime shape: a JDK 21 process, outbound HTTPS, a SQLite cache on local disk, secrets from the environment. The six things every cloud has to give that shape, how AWS, Azure and Google Cloud each satisfy or violate them, what TSANet has actually run on each, and the go-live list in the order it bites.

Run · the SDK demo on ECS Express Mode Run · the gateway engine on Azure Container Apps Written, not run · the demo on Container Apps Documented · Cloud Run
Read the topic →

Agent-to-Agent Support with TSANet

Support platforms now ship agents that can call outside tools and other companies' agents, over two open protocols. Neither protocol says who an outside agent belongs to, what agreement covers the exchange, or which partner agent handles a product. What the protocols and six platforms support today, where a neutral member organization fits, the direction TSANet is considering, and what an agent can already do with Connect. Nothing on the agent-to-agent side is built, and the page says so throughout.

Read · A2A 1.0.0 and MCP 2026-07-28 Compared · six platforms' agent tooling Proposed · MCP server, A2A extension, agent directory Live · the REST API, for any agent
Read the topic →

Not written yet

What Is on the List, and Why It Is Not Here

These appear as headings elsewhere on the hub. They are not written because nothing has been assessed behind them, and a topic page that summarises nothing would be worse than an empty slot.

CandidateWhat is missing
AI-native support platforms
Pylon · DevRev · Wolken · Agentforce · Zendesk AI · Now Assist
No platform assessment exists for any of them. Fin / Intercom is the only one that has been probed, and it has a connector page rather than a topic.
Email-to-case patternsNo connector implements one, so there is nothing to compare.
Swarming & case ownershipOwnership changes propagate on two connectors, but nothing has been written down about how teams actually use it.
SLA & escalation designPartly covered already — the acknowledgment-only SLA and the responded flag are in the API guidance and the acceptance topic. A standalone page needs more than that.
The bar for this section is that a topic compares things that exist. The published topics clear it because four or five platforms independently solved the same problem differently — that contrast is the content. Industry commentary without that grounding belongs somewhere else.

Contributing

Propose a Topic

The most useful proposals come from someone who has hit the same problem on two platforms and found the answers differ. If you have run into that, it is very likely worth a page — and you already have most of the material.