Appearance
Groq
undefined
| Detail | Value |
|---|---|
| Category | AI |
| Base URL | https://api.groq.com/openai/v1 |
| Authentication | Bearer Token |
| Endpoints | 6 |
| Connector key | groq |
Using Groq in a workflow
- Go to Connections and click New Connection.
- Pick Groq from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
GET | Chat Completions |
GET | Completions |
GET | Models |
GET | Transcriptions |
GET | Translations |
GET | Embeddings |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET
Chat Completions
| Detail | Value |
|---|---|
| Operation ID | chat_completions_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Groq connection from the Connection dropdown.
- In the Operation dropdown, select
chat_completions_0. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Groq API reference.
GET
Completions
| Detail | Value |
|---|---|
| Operation ID | completions_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Groq connection from the Connection dropdown.
- In the Operation dropdown, select
completions_1. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Groq API reference.
GET
Models
| Detail | Value |
|---|---|
| Operation ID | models_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Groq connection from the Connection dropdown.
- In the Operation dropdown, select
models_2. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Groq API reference.
GET
Transcriptions
| Detail | Value |
|---|---|
| Operation ID | transcriptions_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Groq connection from the Connection dropdown.
- In the Operation dropdown, select
transcriptions_3. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Groq API reference.
GET
Translations
| Detail | Value |
|---|---|
| Operation ID | translations_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Groq connection from the Connection dropdown.
- In the Operation dropdown, select
translations_4. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Groq API reference.
GET
Embeddings
| Detail | Value |
|---|---|
| Operation ID | embeddings_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Groq connection from the Connection dropdown.
- In the Operation dropdown, select
embeddings_5. - Fill in the parameter fields that appear. Use
{{...}}to reference upstream values.
What it returns
The API Call node writes the response to the workflow context:
{
status: 200,
success: true,
data: { ...response body from the API... },
latencyMs: 142
}Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Groq API reference.