Option A: Using the Official Connector (Recommended)
The official Teams connector handles outbound notifications perfectly for your use case:
Process started notifications
User task created alerts
Process completion updates
Document sharing (available in Camunda 8.7+)
Option B: Custom Integration with Adaptive Cards
While the official connector doesn’t explicitly support Adaptive Cards in the current documentation, you have several options for more advanced scenarios:
Configure webhook endpoints to start processes or correlate messages to running instances
Implement authentication (HMAC, JWT, Basic Auth, or API Key)
For Custom Connectors:
Build a custom connector using the Connector SDK if you need specific Adaptive Card functionality
Create connector templates for reusable configurations
3. Spring Boot Integration Best Practices
For Spring Boot applications with Camunda 8:
Outbound Notifications:
// Use service tasks or job workers in your Spring Boot app
@Component
public class TeamsNotificationWorker {
@JobWorker(type = "send-teams-notification")
public void sendNotification(ActivatedJob job) {
// Call Teams API or use connector
// Map process variables to notification content
}
}
Inbound Webhooks:
Configure HTTP Webhook inbound connectors in your BPMN models
Use REST controllers in Spring Boot to handle external triggers:
@RestController
public class ProcessController {
@PostMapping("/start-process")
public ResponseEntity<?> startProcess(@RequestBody ProcessRequest request) {
// Start Camunda process instance
// Return response for Teams callback
}
}
Key Integration Patterns:
Process Events: Use outbound connectors on BPMN events (start, end, user tasks)
Task Lifecycle: Implement job workers for task creation/completion notifications
Bidirectional Flow: Combine inbound webhooks with outbound notifications
Message Correlation: Use message correlation for interactive scenarios
Start with the official Teams connector for outbound notifications
Use HTTP Webhook connector for inbound Teams interactions
Build custom connectors only if you need specific Adaptive Card features
Implement Spring Boot job workers for complex business logic
The combination of official connectors and webhook integration should cover most real-time collaboration scenarios. If you need more specific Adaptive Card functionality, consider building a custom connector using the SDK.
Would you like me to elaborate on any specific part of this integration approach?
Hi @HareeshKumarReddy, welcome to the forums! Some additional info that the bot missed:
with Camunda 8.8, there are new Teams capabilities coming. If you these are the features you are referring to, they are currently available as an alpha, and will be a preview release next month. Currently it is only available for SaaS customers.
if you want to send events like that through Teams, neither of the Teams integrations mentioned will do that. You would likely need to create a custom exporter (only available in Self-Managed) that pushes the data to a Teams channel.
Hope that helps, let me know if you have more questions!
You’re absolutely right - I should have mentioned the exciting new Camunda 8.8 Teams capabilities that are coming!
Camunda 8.8 Teams Integration (Alpha/Preview)
There are new Teams capabilities being introduced in Camunda 8.8 that provide much deeper integration:
Currently in Alpha for SaaS customers
Preview release expected next month
Designed for real-time process insight directly within Teams collaboration
This might be exactly what you’re looking for in terms of native Teams integration!
For Real-Time Process Events
You’re also correct that for sending detailed process lifecycle events (like process started, task created, etc.) to Teams channels, the current approaches have limitations:
Self-Managed Option:
Custom Exporter: Create a custom exporter that captures Zeebe events and pushes them to Teams channels
This gives you access to all process and task lifecycle events in real-time
Only available for Self-Managed deployments
Current SaaS Options:
Use the existing Teams connector for specific notification points in your process
Implement webhook patterns for bidirectional communication
Wait for the 8.8 preview features which may address your exact use case
Recommendation
Given your requirements for real-time process insights, I’d suggest:
If you’re on SaaS: Wait for the Camunda 8.8 Teams preview (coming next month) - this might be exactly what you need
If you’re on Self-Managed: Consider building a custom exporter for comprehensive event streaming to Teams
For immediate needs: Use the current Teams connector for key process milestones combined with webhook integration
The 8.8 Teams integration sounds like it’s specifically designed for your use case of real-time process collaboration within Teams!
Thanks for the correction and additional insights!
Available Solutions:
Recommendation:
Key Resources: