Gladly

Adds a topic tag to an existing conversation in Gladly to help categorize and organize customer support interactions.

This integration allows you to attach topic tags to conversations in Gladly, your customer service platform. Topics help organize conversations by category (like “billing,” “technical support,” or “returns”) making it easier for agents to prioritize, route, and report on customer interactions.

Parameters

• topic_id (String): The unique identifier of the topic you want to add to the conversation. This must be an existing topic ID from your Gladly account. Example: “Hj8DYP-lQ1WWHvLyY1El4g”.
• conversationId (String): The unique identifier of the conversation you want to tag. This is the Gladly conversation ID where the topic will be added. Example: “5aUMcV_4SpazlCirWL-YIw”.

Output

When successful, this integration returns an empty response, confirming that the topic has been successfully added to the conversation. The topic will then appear in the conversation’s topic list within Gladly.

Example Output:

{}

Creates a new task in Gladly customer service platform and assigns it to a specific inbox with a due date.

This integration creates a task in your Gladly customer service platform, allowing you to assign follow-up work to specific team inboxes. Tasks help ensure important customer issues don’t fall through the cracks by setting clear descriptions, due dates, and assignees. The task will be linked to a customer’s email address for easy reference.

Parameters

• inbox_id (String): The unique identifier of the Gladly inbox where the task should be assigned. This determines which team or agent will receive the task. Example: “UAEF51f6QTuEaEhh8GSRFg”.
• task_due_date (String (ISO 8601 datetime)): When the task should be completed, formatted as an ISO 8601 timestamp with timezone. Example: “2026-03-16T12:00:00.125Z”.
• customer_email (String (email)): The email address of the customer this task relates to. Example: “sarah.mitchell@example.com”.
• task_description (String): A clear description of what needs to be done for this task. Example: “Follow up on shipping delay and provide tracking update”.

Output

Returns a status object indicating whether the task was successfully created. The response includes a success boolean flag and a descriptive message. When the task creation fails, additional response details are provided with error information, such as invalid inbox IDs or missing required fields.

Example Output (Success):

{
  "message": "task is created",
  "success": true
}

Example Output (Failure):

{
  "message": "task is not created",
  "success": false,
  "response": {
    "errors": [{
      "attr": "assignee.inboxId",
      "code": "invalid",
      "detail": "assignee.inboxId does not exist"
    }]
  }
}