elsa-workflows / elsa-workflows/elsa-core

Http Flow

Open
#5,076 3 comments 0 reactions 0 assignees View on GitHub
elsa 3 triaged
Dominant language
C#
Stars
7.9k
Forks
1.5k
Avg merge
15h 22m
Merged PRs (30d)
114

Description

I am trying to make Http Post Endpoint With Body That i can reuse in my custom activity , there are no documentation about this type of flows ,
is this applicable ?
and if it is
what is the wrong about this
![image](https://github.com/elsa-workflows/elsa-core/assets/163500282/cc4e9d05-824a-46ea-9389-d6c771edd49b)
![image](https://github.com/elsa-workflows/elsa-core/assets/163500282/e3e6d111-aae6-4185-bba9-e3a8715c3d95)

even when i try the designer part
![image](https://github.com/elsa-workflows/elsa-core/assets/163500282/94d5ad7b-94ed-426b-99e6-c4216381effa)
![image](https://github.com/elsa-workflows/elsa-core/assets/163500282/4839ac06-bdfe-4461-b1ba-a388bbefb365)

(I Add Input Variable from Input/Output Screen with the type (primitives->object) *wish could put custom type*
and after i put it in parsed content so i can use it later as i tried in my code version ,
then as soon as i add the next activity everything disconnects and shows multiple errors

Contributor guide

Open the contributing guide

Research direction

Start with the issue's screenshots and the described custom activity flow: an HTTP POST endpoint with a body, an Input/Output object variable, and parsed content. Reproduce the designer behavior by adding the next activity and record the resulting errors and disconnected nodes. Done means the flow remains connected and the request body can be reused, or the missing documentation and unsupported custom-type behavior are clearly identified.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
api, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.