Actions2
- Message Actions
- File Actions
Overview
This node interacts with the XMPP protocol to send files to specified recipients. It is useful in scenarios where automated file sharing is needed over XMPP, such as sending reports, documents, or media files to users or groups within an XMPP network. For example, it can be used to send a PDF report to a user identified by their JID (Jabber ID).
Use Case Examples
- Sending a PDF file to a user with JID user@domain.
- Automating the distribution of images or documents to multiple XMPP contacts.
Properties
| Name | Meaning |
|---|---|
| To (JID) | The Jabber ID (JID) of the recipient to whom the file will be sent. This is a required string input. |
| File (Base64) | The file content encoded in Base64 format. This is a required string input representing the file to be sent. |
| File Name | The name of the file being sent, including its extension. This is an optional string input with a default value of 'file.pdf'. |
Output
JSON
sentFile- Details or confirmation of the sent file operation, such as status or metadata returned by the XMPP service.
Dependencies
- Requires an XMPP connection credential for authentication and communication with the XMPP server.
- Requires a RabbitMQ connection credential, likely for message queuing or event handling related to the file sending process.
Troubleshooting
- Ensure the 'To (JID)' field is correctly formatted as a valid Jabber ID; otherwise, the file will not be delivered.
- Verify that the Base64 encoded file content is correctly encoded and not corrupted to avoid transmission errors.
- Check that the XMPP and RabbitMQ credentials are correctly configured and have the necessary permissions.
- Common error: 'Unsupported operation' indicates that the specified resource or operation is not implemented or incorrectly specified.