Third-Party Integration Activities

[Vaughan-mci]

Feature Request

Problem Overview

Currently there is a limited number of activities for integration with third-party services, for example integration with a service that is authenticated with AWS Cognito, clean hand-off to AWS Steps and callback to Elsa, integration with Slack for approval workflows, etc.

Proposed Solution

The roadmap describes a marketplace for these kind of activities in the medium to long term.

As a short-term alternative would there be value in a sub project where these kind of activities can be added to the project and could possibly used as a starting point to gauge the level of interest in building a marketplace.

This could be managed in a similar fashion as Apache Camel integrations which are managed as separate components outside the core ESB.

Elsa 3.0 has implemented modules which starts the journey but wouldn't mind a middle ground that attempts to grow the level of integration.

[glime-ai]

Based on the context provided, it seems like you are suggesting the creation of a subproject for Elsa Workflows where community members can contribute activities for integration with third-party services. This is indeed a valuable suggestion and aligns with the direction the Elsa team is considering, as indicated by the discussions on their GitHub issues page and the roadmap.

The roadmap already mentions the plan for a marketplace for "hot" deployable workflow packages, which could include such integrations. Additionally, the GitHub issue discussions suggest that the team is open to community contributions and is considering a collaborative environment where users from various industries can contribute modules, similar to your suggestion.

As a short-term solution, starting a subproject for community-contributed activities could be a great way to begin building this ecosystem and gauge interest. It would also provide immediate value to users who need these integrations. The team at Elsa seems to encourage this kind of community-driven development, as indicated by their responses to related issues.

To move forward with your proposal, you might want to open a discussion on the Elsa GitHub repository or their community channels like Discord to gather feedback and establish a collaborative approach for this subproject.

This comment was generated by Glime.

[sNakiex]

You can always use the elsa nuget packages and create your own activities. You could then use the dropin functionality to add your activity to elsa. See PR 4471 for a bit more information about the DropIn functionality.