Actions84
- Avatar Actions
- Document Actions
- Function Actions
- Messaging Actions
- Create APNS Provider
- Create Email
- Create FCM Provider
- Create Mailgun Provider
- Create MSG91 Provider
- Create Provider
- Create Push
- Create Sendgrid Provider
- Create SMS
- Create SMTP Provider
- Create Subscriber
- Create Telesign Provider
- Create Textmagic Provider
- Create Topic
- Create Twilio Provider
- Create Vonage Provider
- Delete Provider
- Delete Subscriber
- Delete Topic
- Get Message
- Get Provider
- Get Subscriber
- Get Topic
- List Message Logs
- List Messages
- List Provider Logs
- List Providers
- List Subscriber Logs
- List Subscribers
- List Targets
- List Topic Logs
- List Topics
- Update APNS Provider
- Update Email
- Update FCM Provider
- Update Mailgun Provider
- Update MSG91 Provider
- Update Provider
- Update Push
- Update Sendgrid Provider
- Update SMS
- Update SMTP Provider
- Update Telesign Provider
- Update Textmagic Provider
- Update Topic
- Update Twilio Provider
- Update Vonage Provider
- Storage Actions
- Token Actions
- Users Actions
Overview
The node allows updating an existing SMTP messaging provider configuration in the Appwrite platform. This operation is useful when you want to modify the settings of an SMTP provider used for sending emails, such as changing the host, port, credentials, or enabling/disabling the provider.
Typical use cases include:
- Updating SMTP server details after migration or infrastructure changes.
- Changing authentication credentials securely without recreating the provider.
- Enabling or disabling the SMTP provider dynamically based on workflow conditions.
For example, if your email sending service changes its SMTP host or requires a new password, you can update these details using this node operation without interrupting your messaging workflows.
Properties
| Name | Meaning |
|---|---|
| Provider ID | Unique identifier of the SMTP provider to update. Use unique() to generate a random ID or provide a custom ID. |
| Provider Name | The display name of the SMTP provider. |
| Host | SMTP server hostname or IP address. |
| Port | Port number on which the SMTP server listens (default 587). |
| Username | Username for SMTP authentication. |
| Password | Password for SMTP authentication (input is masked). |
| Encryption | Type of encryption used by SMTP server. Options: None, SSL, TLS. |
| Auto TLS | Boolean flag to enable automatic TLS negotiation. |
| Mailer | Optional mailer name string identifying the mailer client. |
| Enabled | Boolean flag indicating whether the SMTP provider is enabled or disabled. |
Note: The properties above correspond to the "direct" prefixed parameters (hostDirect, portDirect, etc.) used specifically in the update SMTP provider operation.
Output
The output is a JSON object representing the updated SMTP provider resource returned from the Appwrite API. It typically includes fields such as the provider's ID, name, configuration details, status (enabled/disabled), and other metadata confirming the successful update.
No binary data output is produced by this operation.
Dependencies
Requires an active connection to the Appwrite API with valid credentials including:
- API endpoint URL
- Project ID
- An API key credential with permissions to manage messaging providers.
The node uses the official Appwrite SDK internally to perform the update operation.
Troubleshooting
Common issues:
- Invalid or missing Provider ID will cause the update to fail.
- Incorrect SMTP host or port may result in connectivity errors.
- Authentication failures due to wrong username or password.
- Insufficient API permissions to update messaging providers.
Error messages:
"Resource not found": The specified provider ID does not exist."Unauthorized"or"Permission denied": Check API key permissions."Connection refused"or"Timeout": Verify SMTP host and port accessibility.
Resolution tips:
- Double-check the Provider ID and ensure it matches an existing provider.
- Confirm SMTP server details and credentials are correct.
- Ensure the API key used has adequate permissions.
- Test connectivity to the SMTP server outside n8n to isolate network issues.