Actions101
- š¤ Chatting Actions
- š„ļø Sessions Actions
- š Auth Actions
- š¼ļø Screenshot Actions
- š¢ Channels Actions
- š¢ Status Actions
- š¬ Chats Actions
- š¤ Contacts Actions
- š„ Groups Actions
- ā Presence Actions
- š·ļø Labels Actions
- š Observability Actions
Overview
This node checks if a contact exists based on a provided phone number within a specified session. It is useful for verifying the presence of a contact in a system before performing further actions, such as sending messages or updating contact details. For example, it can be used in customer support workflows to confirm if a customer's phone number is registered.
Use Case Examples
- Check if a phone number exists in the contact list before sending a promotional message.
- Verify contact existence during onboarding to avoid duplicate entries.
Properties
| Name | Meaning |
|---|---|
| Session | The session identifier used to scope the contact check. |
| Phone | The phone number to check for existence in the contacts. |
| Request Options | Additional request settings such as batching, SSL handling, proxy, and timeout configurations. |
Output
JSON
exists- Boolean indicating if the contact exists.phone- The phone number checked.session- The session identifier used for the check.
Dependencies
- Requires an API key or session token for authentication to access the contact checking service.
Troubleshooting
- Ensure the session value is valid and active; invalid sessions will cause authentication errors.
- Verify the phone number format is correct; malformed numbers may lead to false negatives.
- If SSL errors occur, consider enabling the 'Ignore SSL Issues' option, but be aware of security risks.
- Proxy settings must be correctly configured if used; incorrect proxy details can cause request failures.
- Timeouts may occur if the server is slow or unresponsive; adjust the timeout setting accordingly.