- Category: customer support
- Auth: API_KEY
- Composio-managed OAuth available? N/A
- Tools: 120
- Triggers: 11
- Slug:
PLAIN - Version: 20261101_00
Tools
Add Customer To Group
Add Customer To Group
Add Customer To Tenants
Add Customer To Tenants
Add Generated Reply
Add Generated Reply
Add Labels To Thread
Add Labels To Thread
Add Members to Tier
Add Members to Tier
Archive Label Type
Archive Label Type
Bulk Delete Thread Fields
Bulk Delete Thread Fields
Bulk Set Thread Fields
Bulk Set Thread Fields
Change Thread Assignment
Change Thread Assignment
PLAIN_CHANGE_THREAD_ASSIGNMENTAssign or unassign a thread’s primary assignee, or add or remove additional assignees. For AI-agent assignment, LIVE allows customer replies while SHADOW observes without sending customer replies.Input Parameters
Output
Create Attachment Download URL
Create Attachment Download URL
PLAIN_CREATE_ATTACHMENT_DOWNLOAD_URLCreate a sensitive three-minute URL and return its virus-scan result. Download or process the file only when attachmentVirusScanResult is CLEAN. Treat INFECTED as unsafe, FAILED or PENDING as not cleared, and null as unscanned; do not fetch or expose the file in any of those states. Do not log or share the URL.Input Parameters
Output
Create Attachment Upload Form
Create Attachment Upload Form
PLAIN_CREATE_ATTACHMENT_UPLOAD_FORMCreate a sensitive, two-hour presigned upload capability; no file is uploaded. Do not log or share uploadFormUrl or uploadFormData. Next, POST multipart/form-data directly to uploadFormUrl with every uploadFormData key/value as a form field and the exact binary file in the form field named file. After that upload succeeds, pass the returned attachment.id to a compatible message or note action.Input Parameters
Output
Create Autoresponder
Create Autoresponder
PLAIN_CREATE_AUTORESPONDERCreate an autoresponder that automatically sends outbound customer replies. Enabled autoresponders can send irreversible external messages when new threads match. Plain permits at most 25 autoresponders per workspace and delays up to 900 seconds.Input Parameters
Output
Create Customer Group
Create Customer Group
PLAIN_CREATE_CUSTOMER_GROUPCreates a new customer group in Plain for organizing and segmenting customers. Customer groups allow you to categorize customers (e.g., by pricing tier, feature access, or support level) and manage them more effectively in your support workflow. Each group has a unique key, display name, and visual color for easy identification. Use this when you need to create a new customer segment for organization or filtering purposes.Input Parameters
Output
Create Email/Slack Discussion
Create Email/Slack Discussion
PLAIN_CREATE_DISCUSSIONImmediately and irreversibly start an external EMAIL or SLACK discussion. EMAIL delivers the first message to every emailDetails.toAddresses recipient and optional ccAddresses recipient. SLACK posts it to the connected channel selected by slackDetails.connectedSlackChannelId. Live provider authorization requires threadDiscussion:create, although the current operation page omits it.Input Parameters
Output
Create Customer Or Thread Event
Create Customer Or Thread Event
Create Label Type
Create Label Type
Create Note
Create Note
PLAIN_CREATE_NOTECreate an internal note on an existing customer thread. Plain’s live API currently rejects customer-level notes without threadId even though the current GraphQL SDL marks that input nullable.Input Parameters
Output
Create Tier SLA
Create Tier SLA
Create SLA Policy
Create SLA Policy
Create Snippet
Create Snippet
Create Task
Create Task
PLAIN_CREATE_TASKCreate a task with optional company, tenant or account context and an optional assignee. Tenant and account IDs may be supplied together; a company ID cannot be combined with either.Input Parameters
Output
Create Thread
Create Thread
PLAIN_CREATE_THREADCreate a thread after obtaining a valid customer identifier. Creating a thread can trigger a configured autoresponder, which sends an external reply to the customer; that outbound message cannot be recalled.Input Parameters
Output
Create Thread Field Schema
Create Thread Field Schema
Create Tier
Create Tier
Delete Autoresponder
Delete Autoresponder
Delete Customer
Delete Customer
Delete Customer Group
Delete Customer Group
Delete Note
Delete Note
Delete Tier SLA
Delete Tier SLA
Delete SLA Policy
Delete SLA Policy
Delete Snippet
Delete Snippet
Delete Task
Delete Task
Delete Tenant
Delete Tenant
PLAIN_DELETE_TENANTDelete a tenant, unlink its customers, and remove its field values. Existing threads retain a reference to the tenant deletion record but are no longer routed through that tenant.Input Parameters
Output
Delete Tenant Field Value
Delete Tenant Field Value
Delete Tenant Field Schema
Delete Tenant Field Schema
Delete Thread
Delete Thread
Delete Thread Field Schema
Delete Thread Field Schema
Delete Tier
Delete Tier
Delete User
Delete User
Escalate Thread Or Select Path
Escalate Thread Or Select Path
Fetch Company
Fetch Company
Fetch Issues
Fetch Issues
PLAIN_FETCH_ISSUESFetches external issue tracker links (Jira, Linear, GitHub, etc.) associated with a customer’s threads. Returns a bounded, flattened snapshot of issue links across the customer’s threads, including thread context. With defaults, it examines up to 50 threads and 50 links per thread; results may be truncated at either limit.Input Parameters
Output
Fetch Tier
Fetch Tier
PLAIN_FETCH_TIERFetch a tier by ID. Set include_details=true to include memberships and SLA configuration, which require additional permissions.Input Parameters
Output
Get Autoresponder
Get Autoresponder
Get Customer By Email
Get Customer By Email
Get Customer By External ID
Get Customer By External ID
Get Customer By ID
Get Customer By ID
Get Customer Group
Get Customer Group
Get Customers
Get Customers
Get Email/Slack Discussion
Get Email/Slack Discussion
Get Knowledge Gap
Get Knowledge Gap
Get Label Type
Get Label Type
Get SLA Policy
Get SLA Policy
Get Snippet
Get Snippet
Get Task by ID or Ref
Get Task by ID or Ref
Get Tenant
Get Tenant
Get Thread By ID
Get Thread By ID
PLAIN_GET_THREAD_BY_IDFetch a thread by ID, including customer info, status, priority, labels, and assignments. If not found, the thread field in the GraphQL response is null.Input Parameters
Output
Get Thread By Reference
Get Thread By Reference
Get User By ID
Get User By ID
PLAIN_GET_USER_BY_IDFetch workspace user/team member by ID. Returns detailed information about a workspace team member including their name, email, status, and avatar. Note: This fetches workspace users (team members), not customers. Use GET_CUSTOMER_BY_ID for customer data.Input Parameters
Output
Import Thread
Import Thread
Import Thread Messages
Import Thread Messages
PLAIN_IMPORT_THREAD_MESSAGESImport up to 25 historical messages and return one result per input message. Reusing a message externalId is idempotent and returns NOOP. The batch is non-atomic: successful messages remain committed when others fail, with per-message results and a top-level bulk_partial_failure error. Attachments require previously uploaded IDs.Input Parameters
Output
List AI Feedback
List AI Feedback
List Autoresponders
List Autoresponders
List Customer Groups
List Customer Groups
List Deleted Threads
List Deleted Threads
List Email/Slack Discussions
List Email/Slack Discussions
List Generated Replies
List Generated Replies
List Knowledge Gaps
List Knowledge Gaps
List Label Types
List Label Types
List SLA Policies
List SLA Policies
List Snippets
List Snippets
List Tasks
List Tasks
List Tenant Field Schemas
List Tenant Field Schemas
List Tenants
List Tenants
List Thread Field Schemas
List Thread Field Schemas
List Threads (Deprecated)
List Threads (Deprecated)
PLAIN_LIST_THREADSDEPRECATED: Use PLAIN_PLAIN_QUERY_THREADS instead. Lists one page of threads (support conversations) in Plain. Returns thread summaries including ID, reference, title, status, and priority. Use this action to: - Get an overview of a page of threads in the system - Fetch threads with pagination for large datasets - Find threads by browsing through the list Pagination: Use ‘first’ for forward pagination (newest first) or ‘last’ for backward pagination (oldest last). For paginated results, use the cursors from pageInfo (endCursor/startCursor) with ‘after’/‘before’ parameters. If no pagination parameters are provided, returns the provider’s default first page.Input Parameters
Output
List Threads By External ID
List Threads By External ID
List Threads With Rich Filters
List Threads With Rich Filters
List Tiers
List Tiers
PLAIN_LIST_TIERSList tiers with cursor pagination. Set include_details=true to include memberships and SLA configuration, which require additional permissions.Input Parameters
Output
Mark Customer As Spam
Mark Customer As Spam
List Threads
List Threads
PLAIN_QUERY_THREADSRetrieve up to 50 threads from one page, optionally filtered by status. Omit the cursor for the first page and pass the returned end cursor to fetch the next page.Input Parameters
Output
Remove Customer From Group
Remove Customer From Group
PLAIN_REMOVE_CUSTOMER_FROM_GROUPRemoves a customer from one or more customer groups in Plain. Use this action to revoke customer group memberships. The customer must be a member of the specified group(s) - attempting to remove a customer from a group they’re not in will result in an error. Groups can be identified by their Plain internal ID (customerGroupId), unique key (customerGroupKey), or external ID (externalId). Common use cases: - Downgrade customer tier (e.g., remove from premium_tier group) - Remove customer from beta access groups - Clean up group memberships after customer status changesInput Parameters
Output
Remove Customer From Tenants
Remove Customer From Tenants
Remove Labels From Thread
Remove Labels From Thread
Remove Members from Tier
Remove Members from Tier
Reorder Autoresponders
Reorder Autoresponders
Reorder Thread Field Schemas
Reorder Thread Field Schemas
Run GraphQL Query
Run GraphQL Query
PLAIN_RUN_GRAPHQL_QUERYExecute an arbitrary GraphQL document against Plain without a safety gate; mutations can immediately and irreversibly change data. This tool cannot predeclare sufficient permissions for every operation and field. GraphQL errors without data raise an error; partial responses can include errors.Input Parameters
Output
Search Customers
Search Customers
Search Tenants
Search Tenants
Search Threads
Search Threads
Send Email/Slack Discussion Message
Send Email/Slack Discussion Message
PLAIN_SEND_DISCUSSION_MESSAGEImmediately and irreversibly deliver a message in an existing discussion. The discussion ID determines the external recipients and original EMAIL or SLACK channel; they cannot be reviewed or overridden here. Live provider authorization requires threadDiscussionMessage:create, although the current operation page omits it.Input Parameters
Output
Send Message
Send Message
PLAIN_SEND_MESSAGEImmediately and irreversibly deliver a message through an existing thread. The thread determines the delivery channel and primary recipient or channel; this action does not let the caller review or override them. Email threads can add CC and BCC recipients. By default Plain sends as the connected machine user, while impersonation can make the message appear from a customer or an allow-listed workspace user.Input Parameters
Output
Send New Email
Send New Email
PLAIN_SEND_NEW_EMAILImmediately and irreversibly send an external email to a customer. Plain uses the customer’s email as the primary recipient. The request can add CC and BCC recipients, send from a verified alternate support address, and attach the email to an existing thread; the delivery channel remains email.Input Parameters
Output
Set Customer Tenants
Set Customer Tenants
Transition Thread Status
Transition Thread Status
PLAIN_TRANSITION_THREAD_STATUSMove a thread to Todo, Snoozed, or Done.Input Parameters
Output
Unarchive Label Type
Unarchive Label Type
Unmark Customer As Spam
Unmark Customer As Spam
Update Autoresponder
Update Autoresponder
PLAIN_UPDATE_AUTORESPONDERUpdate an autoresponder that automatically sends outbound customer replies. Enabling or changing a matching autoresponder can cause irreversible external messages. Plain permits at most 25 autoresponders per workspace and delays up to 900 seconds.Input Parameters
Output
Update Company
Update Company
PLAIN_UPDATE_COMPANYUpserts (creates or updates) a company in Plain. Provide companyId to update by ID or companyDomainName to upsert by domain. When both identifiers are omitted, domainName is also used as companyDomainName for compatibility. Use this to create new companies, update existing company details (name, domain, contract value), or assign account owners.Input Parameters
Output
Update Company Tier
Update Company Tier
Update Generated Reply
Update Generated Reply
Update Label Type
Update Label Type
Update Note
Update Note
Update Tier SLA
Update Tier SLA
Update SLA Policy
Update SLA Policy
Update Snippet
Update Snippet
Update Task
Update Task
PLAIN_UPDATE_TASKUpdate selected fields on an existing task.Input Parameters
Output
Update Tenant Tier
Update Tenant Tier
Update Thread Title
Update Thread Title
Update Thread Attributes
Update Thread Attributes
Update Thread Field Schema
Update Thread Field Schema
Apply or Clear Thread SLA Policy
Apply or Clear Thread SLA Policy
Update Tier
Update Tier
Upsert Customer
Upsert Customer
Upsert Customer Group
Upsert Customer Group
Upsert Tenant
Upsert Tenant
Upsert Tenant Field
Upsert Tenant Field
PLAIN_UPSERT_TENANT_FIELDSet one typed custom field value for a tenant.Input Parameters
Output
Triggers
Customer Event
Customer Event
PLAIN_CUSTOMER_EVENTType: webhookFires when a customer in Plain is created, updated or deleted.event_type says which it was, created, updated or deleted, in the same vocabulary the config filters on — so a single subscription to all three can branch downstream without matching on Plain’s raw event names.Group membership changes are a separate slug, customer_group_membership_changed.Configuration
['created', 'deleted']. Choose from created, updated and deleted. Leave unset to fire for every kind.Payload
created, updated or deleted.Customer Group Changed
Customer Group Changed
Customer Group Membership Changed
Customer Group Membership Changed
PLAIN_CUSTOMER_GROUP_MEMBERSHIP_CHANGEDType: webhookFires when a customer is added to or removed from a customer group in Plain.Use it to re-segment a customer downstream the moment their grouping in Plain changes — move them onto a different plan’s onboarding, change who gets paged for their threads, sync the new segment into your CRM.change says which direction it was, added or removed, straight from Plain. Which group it was is the one that differs between customer.customer_group_memberships and previous_customer.customer_group_memberships, both of which carry the customer’s full membership list.Payload
Thread Created
Thread Created
Thread Custom Field Updated
Thread Custom Field Updated
PLAIN_THREAD_CUSTOM_FIELD_UPDATEDType: webhookFires when one of your own thread fields is set, changed or cleared on a Plain thread.Payload
type.type.Thread Message Received
Thread Message Received
PLAIN_THREAD_MESSAGE_RECEIVEDType: webhookFires when an inbound message arrives on a Plain thread.Covers email, in-app chat, Slack, Discord and Microsoft Teams, and each channel ships its own message shape, so read channel before reading message. For the replies your own team sends out, use the Thread Message Sent trigger instead.Configuration
['email', 'slack']. Leave unset to fire for every channel.Payload
message has.channel to know which shape you have.Thread Message Sent
Thread Message Sent
PLAIN_THREAD_MESSAGE_SENTType: webhookFires when your team sends a message out on a Plain thread.Covers email, in-app chat, Slack, Discord and Microsoft Teams, and each channel ships its own message shape, so read channel before reading message. Editing a Slack or Discord message afterwards does not fire it again, and for messages arriving from the customer use the Thread Message Received trigger instead.Configuration
['email', 'slack']. Leave unset to fire for every channel.Payload
message has.channel to know which shape you have.Thread Note Created
Thread Note Created
PLAIN_THREAD_NOTE_CREATEDType: webhookFires when an internal note is added to a thread in Plain.Carries no mentions: Plain only reports them on its separate mention event, which is PLAIN_THREAD_NOTE_MENTIONED. Subscribing to both slugs delivers every mentioning note twice, under two different event ids.Payload
Thread Note Mention Created
Thread Note Mention Created
PLAIN_THREAD_NOTE_MENTIONEDType: webhookFires when an internal note mentions a machine user in Plain.The only event that carries mentions. The raw <@mu_…> markup is not guaranteed in either note.text or note.markdown, so this slug — not scanning the note body — is how a consumer learns who was mentioned.Plain publishes such a note twice, here and as thread.note_created, so subscribing to both this and PLAIN_THREAD_NOTE_CREATED delivers it twice, under two different event ids.Payload
Thread Properties Updated
Thread Properties Updated
PLAIN_THREAD_PROPERTIES_UPDATEDType: webhookFires when a thread’s status, assignee, priority or labels change in Plain.Every event carries the thread’s new state alongside its state immediately before the change, and names which of the four properties changed. Assignment events also cover reassignment, so both sides can be populated.Configuration
['status', 'priority']. Choose from status, assignment, priority and labels. Leave unset to fire for all four.Payload
status, assignment, priority or labels.