Reference

PLAIN_CUSTOMER_EVENT

Fires 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`.

PLAIN_CUSTOMER_GROUP_CHANGED

Fires when a customer group is created, edited or deleted in Plain.

PLAIN_CUSTOMER_GROUP_MEMBERSHIP_CHANGED

Fires 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.

PLAIN_THREAD_CREATED

Fires when a new support thread is opened in Plain.

PLAIN_THREAD_CUSTOM_FIELD_UPDATED

Fires when one of your own thread fields is set, changed or cleared on a Plain thread.

PLAIN_THREAD_MESSAGE_RECEIVED

Fires 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.

PLAIN_THREAD_MESSAGE_SENT

Fires 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.

PLAIN_THREAD_NOTE_CREATED

Fires 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.

PLAIN_THREAD_NOTE_MENTIONED

Fires 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.

PLAIN_THREAD_PROPERTIES_UPDATED

Fires 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.

PLAIN_THREAD_TENANT_UPDATED

Fires when a thread's tenant is set, changed or cleared in Plain. Plain also sends this event when a thread's tenant is reapplied without changing, in which case both sides hold the same tenant or both are null.

Run GraphQL Query

Execute custom GraphQL queries and mutations against the Plain API to retrieve complex data, perform advanced operations, or access features not available through standard actions.

Fetch Company

Retrieves complete company profile information including name, domain, contact details, and contract value by company ID. Use this when you need to access or verify comprehensive company data for business operations.

Update Company

Create or update company information in Plain using either a company ID or domain name, including details like company name, domain, contract value, and account owner assignments.

Add Customer To Group

Assign a customer to one or more customer groups to organize your contacts and enable targeted communication strategies. This helps you segment your audience for personalized outreach and better relationship management.

Create Customer Group

Creates a new customer group in Plain to organize and segment your customers by characteristics like pricing tier or support level. Use this to establish customer categories that help you manage support workflows and prioritize communication more effectively.

List Customer Groups

Retrieve all customer groups in your account with optional filtering and pagination to organize and manage customer segments. Use this to view your customer group structure and metadata at a glance.

Remove Customer From Group

Removes a customer from one or more customer groups in Plain, allowing you to revoke group memberships and adjust customer access levels. This helps you manage customer segmentation as their status or needs change.

Get Customer By Email

Retrieve a customer's profile information using their email address, allowing you to quickly access account details, contact preferences, and history without knowing their customer ID.

Upsert Customer

Creates a new customer record or updates an existing one to keep your customer information current and synchronized across your business systems.

Delete Customer

Removes a customer record from your system permanently using their customer ID. Use this when you need to eliminate outdated, duplicate, or unwanted customer entries to keep your customer database clean and accurate.

Get Customer By ID

Retrieve complete customer information and details by looking up their unique ID in your system. This lets you quickly access a customer's profile, contact information, and account history whenever you need it.

Get Customers

Retrieve a list of your customers with options to filter, sort, and paginate through the results to find specific customer information.

Fetch Issues

Retrieves all issue tracker links (from Jira, Linear, GitHub, etc.) connected to a customer's support threads, giving you a complete view of external issues tied to customer conversations.

Send Message

Sends a new message within an existing conversation thread to communicate with team members or clients. This helps you maintain organized communication by keeping related messages grouped together.

Create Thread

Start a new conversation thread with a customer to organize and track communications in one place. This helps you keep all related messages together for better context and follow-up.

List Threads

Retrieve a paginated list of threads, with optional filtering by status, to manage and organize your communication history.

Get Thread By ID

Retrieves detailed information about a specific conversation thread, including customer details, current status, priority level, labels, and who it's assigned to. Use this to access all relevant context about a customer interaction in one request.

List Threads (Deprecated)

Retrieves a list of all support conversations (threads) from Plain, including their ID, status, and priority information. Use this to get an overview of customer support activity and manage conversations across your support queue.

Update Thread

Rename or update a thread's title to keep your conversations organized and easier to find. This helps you maintain clear communication channels as your discussion topics evolve or when you need to reflect the current status or focus of a conversation.

Fetch Tier

Retrieves detailed information about a specific tier using its ID, allowing you to access tier metadata and settings whenever you need to reference or validate tier details.

List Tiers

Retrieve a paginated list of available tiers to see your pricing options and tier details. Use this when you need to browse or inventory all tiers in your system.

Delete User

Remove a user account from your system permanently by their ID. Use this when you need to deactivate team members, clients, or contacts who no longer need access.

Get User By ID

Retrieve detailed information about a team member in your workspace, including their name, email, status, and avatar. This is useful for accessing specific team member data to manage your workspace or integrate with other tools.