Google Gemini connector unable to save the input content
- Dominant language
- TypeScript
- Stars
- 111
- Forks
- 109
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 20
Description
### Describe the Bug with repro steps
Hello,
With the google gemini "generate content" connector type I am unable to see in graph view what I am writting in the "CONTENT" part, while I am able to see it in the code view.
However, when I run a test, the connector is acting as if the content in "parts:[ { "text" :}] was empty. And everytime I click on the connector in graph view it becom empty, even if I just add content in graph or code view.
The code view with "CONTENT" being the query I wrote to google gemini :
```json
"inputs": {
"host": {
"connection": {
"name": "@parameters('$connections')['googlegemini']['connectionId']"
}
},
"method": "post",
"body": {
"contents": [
{
"parts": [
{
"text": "CONTENT"
}
]
}
]
},
"path": "/v1beta/models/gemini-pro:generateContent"
}
}
},
```
It is supposed to work because other parts of my workflow are using google gemini connector, I added the content the same way and I am not facing any issue.
### What type of Logic App Is this happening in?
Consumption (Portal)
### Which operating system are you using?
Windows
### Did you refer to the TSG before filing this issue? https://aka.ms/lauxtsg
Yes
### Workflow JSON
```json
"inputs": {
"host": {
"connection": {
"name": "@parameters('$connections')['googlegemini']['connectionId']"
}
},
"method": "post",
"body": {
"contents": [
{
"parts": [
{
"text": "CONTENT"
}
]
}
]
},
"path": "/v1beta/models/gemini-pro:generateContent"
}
}
},
```
### Screenshots or Videos
_No response_
### Browser
Chrome.
### Additional context
_No response_
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the issue in the Google Gemini "generate content" connector using the graph view and code view, then inspect how the CONTENT value in the workflow JSON is loaded and saved. The fix is complete when the text remains visible after reopening the connector and is included in the request when a test runs.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100