Custom Connectors in Application Integration

Google Cloud Integration Services
,
1

Hi I have few doubts about Application Integrations Custom Connectors

a. Whether the custom connectors support event based integrations & bi-directional flows. How will the custom connector events be tracked is not fully clear. Though for out-of-box connectors event subscriptions is mentioned as way to track - e.g new tickets in jira etc. - refer links Custom connectors  |  Integration Connectors  |  Google Cloud and Event subscriptions  |  Integration Connectors  |  Google Cloud but its not clear how will this be supported for connectors being built by partners/developers that are event based and not API based say for HR App new employee addition may require an update in payroll system

b. Are there any guidelines on how one can develop the custom connectors logic what may the tech-stack for implementation etc.

c. How will the scalability, timeout issues with app/services that custom connector connects to be handled.

Any pointers are appreciated.

thanks,
Aakash

2

Hi @aakashsharmaa5,

Just wanted to acknowledge your question—still no responses yet, but we’ll make sure it gets noticed and invite others to help out.

3

Custom connectors in Application Integrations can support event-based and bi-directional flows, but event tracking depends on the connector’s implementation—partners/developers need to design how events (like a new employee in HR) trigger updates in other systems. Google provides general guidelines for building custom connectors, but the tech stack and logic are flexible, often using REST APIs, webhooks, or SDKs. Scalability and timeout handling must also be managed within the connector logic, using retries, batching, or asynchronous processing, since the platform relies on the connector’s design to handle load and service limits.

1 Like