Actions48
- Chat Actions
- Mensagem Actions
- Grupo Actions
- Perfil Actions
Overview
This node interacts with the Zappfy API to update privacy settings of a user profile. Specifically, for the "Perfil" (Profile) resource and the "Atualizar Configurações De Privacidade" (Update Privacy Settings) operation, it allows users to configure who can see various aspects of their profile such as read receipts, profile photo, status, online presence, last seen time, and group addition permissions.
Common scenarios include:
- Adjusting privacy preferences in messaging or social apps integrated with Zappfy.
- Automating privacy updates based on user roles or external triggers.
- Synchronizing privacy settings across multiple accounts or platforms.
For example, a user might want to restrict their profile photo visibility to only contacts except specific blacklisted ones, or disable read receipts entirely.
Properties
| Name | Meaning |
|---|---|
| Nome Da Instância | The name of the instance to identify which profile is being updated. |
| Confirmação De Leitura | Who can see when you have read messages. Options: Todos (all), Ninguém (none). |
| Foto Do Perfil | Who can see your profile photo. Options: Todos (all), Meus Contatos (contacts), Exceto Contatos Específicos (contact blacklist), Ninguém (none). |
| Status | Who can see your status message. Options: Todos (all), Meus Contatos (contacts), Exceto Contatos Específicos (contact blacklist), Ninguém (none). |
| Online | Who can see when you are online. Options: Todos (all), Igual Ao Visto Por Último (match last seen). |
| Visto Por Último | Who can see your last seen time. Options: Todos (all), Meus Contatos (contacts), Exceto Contatos Específicos (contact blacklist), Ninguém (none). |
| Grupos | Who can add you to groups. Options: Todos (all), Meus Contatos (contacts), Exceto Contatos Específicos (contact blacklist). |
Output
The node outputs a JSON array containing the response from the Zappfy API after updating the privacy settings. The exact structure depends on the API response but typically includes confirmation of updated fields or error details if the update failed.
No binary data output is indicated.
Dependencies
- Requires an active connection to the Zappfy API.
- Needs an API authentication token configured in n8n credentials (referred generically as "an API key credential").
- Network access to
https://docs.zappfy.io/api-referencebase URL.
Troubleshooting
- Operation not supported error: If the selected operation or resource is invalid or not implemented, the node throws an error indicating unsupported operation. Ensure correct resource and operation names are used.
- API authentication errors: Missing or invalid API credentials will cause authentication failures. Verify that the API key credential is correctly set up.
- Invalid property values: Providing unsupported options for privacy settings may result in API errors. Use only the allowed option values listed in properties.
- Network issues: Connectivity problems to the Zappfy API endpoint will cause request failures. Check network and firewall settings.
Links and References
- Zappfy API Documentation (base URL referenced in the node)