HELPSCOUT n8n INTEGRATION: AUTOMATE HELPSCOUT WITH N8N

This action retrieves multiple thread records from a HelpScout conversation, perfect for accessing complete conversation histories or building custom conversation views.

Key parameters:

• Credential to connect with: Select your HelpScout OAuth2 credentials. Required.
• Resource: Set to "Thread".
• Operation: Set to "Get Many".
• Conversation ID: Optionally specify a conversation ID to fetch threads from that specific conversation.
• Return All: Toggle to retrieve all threads without limit.
• Limit: Maximum number of threads to fetch when "Return All" is disabled (default: 50).

Use cases: Export complete conversation histories for compliance archiving, build custom conversation views with full thread data, or analyze response times by examining thread timestamps.

Add new threads to existing conversations in HelpScout. This action allows you to programmatically add replies, notes, or other thread types to conversations, enabling automated responses and internal annotations.

Key parameters:

• Credential to connect with: Your HelpScout credentials. Required.
• Resource: Set to "Thread".
• Operation: Set to "Create".
• Conversation ID: The ID of the conversation to add the thread to. Required.
• Type: Select the thread type (reply, note, forward, etc.) from the dropdown. Required.
• Text: The content of the thread message.
• Additional Fields: Add optional properties like author, created date, or custom fields.
• Attachments: Attach files to the thread.

Use cases: Automatically add internal notes when certain conditions are met in a conversation, send automated reply threads based on keyword detection, or append system-generated updates to conversations from external monitoring tools.

Retrieve multiple mailboxes from your HelpScout account in a single request. Ideal for building mailbox selectors, generating reports across all support channels, or synchronizing mailbox data.

Key parameters:

• Credential to connect with: Your HelpScout authentication. Required.
• Resource: Set to "Mailbox".
• Operation: Set to "Get Many".
• Return All: Toggle to retrieve all mailboxes without limit.
• Limit: Maximum number of mailboxes to fetch when "Return All" is disabled (default: 50).

Use cases: Build a dynamic dropdown of mailboxes for a custom ticketing interface, generate cross-mailbox reports for support volume analysis, or sync mailbox configurations with external documentation systems.

Retrieve details about a specific mailbox in your HelpScout account. This action is useful for workflows that need mailbox configuration data or for dynamic routing based on mailbox properties.

Key parameters:

• Credential to connect with: Your HelpScout credentials. Required.
• Resource: Set to "Mailbox".
• Operation: Set to "Get".
• Mailbox ID: The unique identifier of the mailbox to retrieve. Required.

Use cases: Fetch mailbox settings to validate configuration in automated checks, retrieve mailbox details for dynamic conversation routing, or pull mailbox information for reporting and analytics dashboards.

Keep your customer data current by automatically updating customer records in HelpScout. This action ensures your support team always has the latest customer information at their fingertips.

Key parameters:

• Credential to connect with: Your HelpScout authentication. Required.
• Resource: Set to "Customer".
• Operation: Set to "Update".
• Customer ID: The unique identifier of the customer to update. Required.
• Update Fields: Dynamic section where you specify which properties to modify (name, email, phone, company, etc.).

Use cases: Automatically update customer profiles when they modify their account settings, sync customer tier or subscription status from your billing system, or add tags or notes to customer profiles based on support interaction history.

This action allows you to access and manipulate customer properties in HelpScout, giving you fine-grained control over customer metadata and custom fields.

Key parameters:

• Credential to connect with: Your HelpScout OAuth2 credentials. Required.
• Resource: Set to "Customer".
• Operation: Set to "Properties" to work with customer property data.

Use cases: Retrieve custom field values for conditional workflow logic, access customer metadata for personalized automation rules, or work with extended customer properties not covered by standard fields.

This action retrieves multiple customer records from HelpScout in a single operation, perfect for bulk data operations, analytics, or synchronization workflows.

Key parameters:

• Credential to connect with: Select your HelpScout credentials. Required.
• Resource: Set to "Customer".
• Operation: Set to "Get Many".
• Return All: Toggle to retrieve all customers without pagination.
• Limit: Maximum number of customers to fetch when "Return All" is disabled (default: 50).
• Options: Add additional filters or configuration properties.

Use cases: Export your entire customer database to a data warehouse for analysis, build a daily report of customers added in the last 24 hours, or sync customer lists between HelpScout and your HubSpot CRM.

Retrieve detailed information about a specific customer from HelpScout. This action is crucial for workflows that need customer context before taking action, like personalized responses or routing decisions.

Key parameters:

• Credential to connect with: Your HelpScout OAuth2 credentials. Required.
• Resource: Set to "Customer".
• Operation: Set to "Get".
• Customer ID: The unique identifier of the customer to retrieve. Required.

Use cases: Fetch customer details to personalize automated responses, check customer history before escalating conversations, or retrieve customer data to sync with external CRM systems.

This action creates new customer records in HelpScout, allowing you to build your customer database automatically from various sources like sign-up forms, e-commerce platforms, or CRM systems.

Key parameters:

• Credential to connect with: Your HelpScout authentication. Required.
• Resource: Set to "Customer".
• Operation: Set to "Create".
• Resolve Data: Enable to automatically process returned data for use in subsequent nodes.
• Additional Fields: Add optional properties like name, company, job title, or custom fields.
• Address: Add one or more physical addresses associated with the customer.
• Chat Handles: Include chat platform identifiers (Slack, Twitter, etc.).
• Emails: Add multiple email addresses linked to the customer profile.

Use cases: Automatically create customer profiles when new users register on your platform, sync customer data from your WooCommerce store to HelpScout, or build customer records from CRM contacts for unified support context.

Need to retrieve multiple conversations at once? This action fetches batches of conversation records from HelpScout, ideal for bulk operations, reporting, or data synchronization workflows.

Key parameters:

• Credential to connect with: Your HelpScout OAuth2 credentials. Required.
• Resource: Set to "Conversation".
• Operation: Set to "Get Many" for batch retrieval.
• Return All: Toggle to fetch all matching conversations without limit.
• Limit: When "Return All" is disabled, set the maximum number of conversations to retrieve (default: 50).
• Options: Add optional filtering properties for more granular control.

Use cases: Export recent conversations to a Google Sheet for weekly support metrics, batch process conversations to identify unanswered tickets older than 24 hours, or sync all open conversations to an external analytics platform.

This action retrieves the complete details of a specific conversation from HelpScout. It's essential when you need to access conversation data for reporting, synchronization with other systems, or conditional workflow logic based on conversation properties.

Key parameters:

• Credential to connect with: Select your HelpScout account credentials from the dropdown. This is required.
• Resource: Set to "Conversation" to target conversation data.
• Operation: Set to "Get" to retrieve a single record.
• Conversation ID: A required text field where you enter the unique identifier of the conversation you want to fetch.

Use cases: Retrieve conversation details to populate a custom dashboard or reporting system, check conversation status before performing conditional actions in your workflow, or pull conversation data to sync with your CRM or data warehouse.

This action permanently removes a conversation from your HelpScout account. Use it carefully for cleanup operations or compliance-related data removal workflows.

Key parameters:

• Credential to connect with: Select your authenticated HelpScout credentials. Required.
• Resource: Set to "Conversation".
• Operation: Set to "Delete".
• Conversation ID: The unique identifier of the conversation to delete. Required.

Use cases: Automatically remove test conversations created during development, implement GDPR compliance workflows to delete customer data upon request, or clean up spam or duplicate conversations identified by automated filters.

This action allows you to programmatically create new conversations in HelpScout, making it perfect for automatically generating support tickets from external sources like web forms, chatbots, or other applications in your tech stack.

Key parameters:

• Mailbox Name or ID: Specify which mailbox the conversation will be created in. You can use either the human-readable name or the unique identifier. This is required.
• Status: Set the initial status of the conversation (active, pending, closed, etc.) via a dropdown menu.
• Subject: Define the subject line for the conversation as a text input.
• Type: Categorize the conversation type for proper routing and organization.
• Resolve Data: Toggle to process and resolve any dynamic data during execution.
• Additional Fields: Add optional properties like tags, custom fields, or assignee information.

Use cases: Automatically create support conversations when a user submits a contact form on your website, generate tickets from incoming emails processed through a custom filter, or create conversations from Discord messages that mention specific keywords.