Plain icon

Plain

Interact with Plain API

Actions23

Thread → Create

AI-generated

Overview

This node interacts with the Plain API to manage "threads" related to customers. Specifically, the Create Thread operation allows users to create a new thread associated with a customer. Threads can represent conversations, support tickets, or any form of customer communication that requires tracking and management.

Typical use cases include:

  • Creating a new support ticket or conversation thread for a customer.
  • Logging an issue or inquiry from a customer with relevant metadata.
  • Organizing customer interactions by priority, labels, and assignment to team members.

For example, you might use this node to automatically create a new thread when a customer submits a form on your website, including details like the thread title, priority, and assigned user.

Properties

Name Meaning
Customer ID The unique identifier of the customer to whom the thread will be linked.
Title The title or subject of the thread.
Additional Fields Optional extra fields to customize the thread creation:
- Priority: Urgency level of the thread (Urgent, High, Normal, Low). Default is Normal.
- Text Content: Initial message or description text of the thread.
- External ID: Your own unique identifier for the thread.
- Labels: Tags or categories to attach to the thread.
- Assigned To User: Assign the thread to a specific user.
- Tenant ID / Tenant External ID: Associate the thread with a tenant.
- Thread Fields: Custom key-value fields of types String, Boolean, or Enum to set additional metadata on the thread.

Additional Details on Some Properties

  • Priority Options:

    • Urgent (0)
    • High (1)
    • Normal (2)
    • Low (3)

  • Labels: Loaded dynamically from available label types in the system.

  • Assigned To User: Selectable from existing users loaded dynamically.

  • Thread Fields: Custom fields allow setting structured data on the thread, supporting string, boolean, and enum types. Enum values are dynamically loaded based on the selected field.

Output

The output JSON object contains the created thread's details, including:

  • id: Unique thread identifier.
  • customer: Object with customer id and fullName.
  • title: Thread title.
  • status: Current status of the thread (e.g., TODO, SNOOZED, DONE).
  • createdAt and updatedAt: Timestamps in ISO8601 format.
  • Other optional fields depending on input, such as priority, labels, assigned user, external ID, tenant association, and custom thread fields.

No binary data output is produced by this operation.

Dependencies

  • Requires an active connection to the Plain API via an API key credential configured in n8n.
  • Uses GraphQL queries and mutations to interact with the Plain API.
  • Dynamic loading of options (users, labels, thread field schemas, enum values) depends on successful API requests.

Troubleshooting

  • Common Issues:

    • Missing required fields like Customer ID or Title will cause errors.
    • Invalid or unauthorized API credentials will prevent successful API calls.
    • Providing invalid values for custom thread fields or enums may result in API errors.
    • Network issues or API downtime can cause request failures.

  • Error Messages:

    • Errors returned from the API typically include a message describing the problem.
    • Field-specific validation errors are aggregated and shown in error messages.
    • If the API returns an error, the node throws an error with the message for easier debugging.

  • Resolution Tips:

    • Ensure all required properties are correctly filled.
    • Verify API credentials and permissions.
    • Check that referenced IDs (customer, user, labels) exist and are correct.
    • Review custom field values for type correctness.
    • Enable "Continue On Fail" in the node settings to handle errors gracefully during batch processing.

Links and References

If you need summaries for other operations or resources, feel free to ask!

Discussion