Appearance
Front
undefined
| Detail | Value |
|---|---|
| Category | Support |
| Base URL | https://api2.frontapp.com |
| Authentication | Bearer Token |
| Endpoints | 7 |
| Connector key | front |
Using Front in a workflow
- Go to Connections and click New Connection.
- Pick Front 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 | List Conversations |
GET | Send Message |
GET | List Contacts |
GET | Add Comment |
GET | List Inboxes |
GET | List Tags |
GET | List Teammates |
Each endpoint is documented in full below. Use the outline on the right to jump to one.
GET
List Conversations
| Detail | Value |
|---|---|
| Operation ID | list_conversations_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Front connection from the Connection dropdown.
- In the Operation dropdown, select
list_conversations_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 Front API reference.
GET
Send Message
| Detail | Value |
|---|---|
| Operation ID | send_message_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Front connection from the Connection dropdown.
- In the Operation dropdown, select
send_message_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 Front API reference.
GET
List Contacts
| Detail | Value |
|---|---|
| Operation ID | list_contacts_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Front connection from the Connection dropdown.
- In the Operation dropdown, select
list_contacts_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 Front API reference.
GET
Add Comment
| Detail | Value |
|---|---|
| Operation ID | add_comment_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Front connection from the Connection dropdown.
- In the Operation dropdown, select
add_comment_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 Front API reference.
GET
List Inboxes
| Detail | Value |
|---|---|
| Operation ID | list_inboxes_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Front connection from the Connection dropdown.
- In the Operation dropdown, select
list_inboxes_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 Front API reference.
GET
List Tags
| Detail | Value |
|---|---|
| Operation ID | list_tags_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Front connection from the Connection dropdown.
- In the Operation dropdown, select
list_tags_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 Front API reference.
GET
List Teammates
| Detail | Value |
|---|---|
| Operation ID | list_teammates_6 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Front connection from the Connection dropdown.
- In the Operation dropdown, select
list_teammates_6. - 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 Front API reference.