Actions57
- Agents Actions
- Public Answer Actions
- Answer Management Actions
- Communications Actions
- Customers Actions
- Conversations Actions
- Get Conversations
- Get Conversation
- Patch Conversation
- Create Item
- Get Item
- Delete Item
- Get Media
- Get Voice Transcript
- Create Customer Item
- Delete Customer Item
- Get Conversation Items
- Add Topic To Conversation
- Delete Topic From Conversation
- Add Note To Conversation
- Get Note From Conversation
- Reply To Message
- Redact Content
- Export Actions
- Freeform Topics Actions
- Message Automation Actions
- Proactive Conversations Actions
- Tasks Actions
- User Identity Actions
- Topics Actions
- Webhooks Actions
- Payloads Actions
Overview
The "Find Customers" operation in the Customers resource allows you to search for customer profiles using specific identifiers such as email address, external customer ID, or phone number. This node is useful when you need to retrieve customer information from a system that integrates with Gladly's API, enabling workflows like verifying customer details, personalizing communications, or syncing customer data across platforms.
Practical examples include:
- Searching for a customer by their email before creating a new support ticket.
- Looking up a customer profile using an external system’s customer ID to enrich data.
- Finding a customer by phone number during a call center interaction.
Properties
| Name | Meaning |
|---|---|
| Customer email address to search on. | |
| External Customer Id | Customer ID in your system of record for Customer Profiles linked to a Lookup Adaptor installed prior to 05/12/21. Not searchable for adaptors installed on or after 05/12/21. |
| Phone Number | Phone number in E.164 format (e.g., +16505551987). The value should be URL escaped where + becomes %2B. |
Output
The node outputs JSON data representing the found customer(s) matching the search criteria. The structure typically includes customer profile details as returned by the Gladly API. There is no indication of binary data output for this operation.
Dependencies
- Requires an API key credential for authenticating with the Gladly API.
- The node uses the Gladly API endpoint at
https://petstore3.swagger.io/api/v3. - Proper configuration of the API authentication within n8n is necessary.
Troubleshooting
- No results found: Ensure the search parameter (email, external customer ID, or phone number) is correctly formatted and exists in the Gladly system.
- Invalid phone number format: Phone numbers must be in E.164 format and URL encoded (
+as%2B). - Authentication errors: Verify that the API key credential is valid and has sufficient permissions.
- External Customer ID not searchable: If using an external customer ID, confirm whether the Lookup Adaptor was installed before 05/12/21; otherwise, this field will not return results.