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
This node operation allows you to create a new Mailgun messaging provider within the Appwrite platform via n8n. It is useful for users who want to integrate Mailgun email sending capabilities into their workflows managed by Appwrite, enabling automated and programmatic email dispatch through Mailgun's API.
Typical scenarios include:
- Setting up a Mailgun provider to send transactional or marketing emails.
- Automating email notifications from an application using Appwrite as backend.
- Managing multiple email providers centrally in Appwrite and switching between them dynamically.
For example, you can create a Mailgun provider with your API key and domain, specify sender details, and enable it for use in your messaging workflows.
Properties
| Name | Meaning |
|---|---|
| Provider ID | Unique identifier for the provider. Use unique() to auto-generate or provide a custom ID. |
| Provider Name | Human-readable name for the Mailgun provider. |
| API Key | The Mailgun API key used for authenticating requests. |
| Domain | The Mailgun domain associated with your account. |
| EU Region | Boolean flag indicating whether to use the Mailgun EU region endpoint. |
| From Name | The sender's display name for outgoing emails. |
| From Email | The sender's email address. |
| Reply To Name | The name shown in the reply-to field of emails. |
| Reply To Email | The email address used for replies. |
| Enabled | Whether the provider is enabled (active) or not. |
| Additional Fields | Optional extra settings including: |
| - BCC: Comma-separated list of BCC email addresses. | |
| - CC: Comma-separated list of CC email addresses. | |
| - Draft: Whether the message is saved as draft. | |
| - HTML: Whether the email content is HTML formatted. | |
| - Scheduled At: ISO 8601 timestamp for scheduled delivery. | |
| - Targets, Topics, Users: Comma-separated lists of IDs for targeting messages. |
Output
The output is a JSON array containing the response from the Appwrite API after creating the Mailgun provider. This typically includes details of the newly created provider such as its ID, name, configuration, status, and metadata returned by the Appwrite service.
No binary data output is involved in this operation.
Dependencies
- Requires an active Appwrite project with API access configured.
- Needs an API key credential for Appwrite to authenticate API calls.
- Requires valid Mailgun credentials (API key and domain).
- The node uses the Appwrite SDK internally to communicate with the Appwrite backend.
Troubleshooting
- Invalid API Key or Domain: If the Mailgun API key or domain is incorrect, the creation will fail. Verify these values in your Mailgun dashboard.
- Permission Errors: Ensure the Appwrite API key has sufficient permissions to create messaging providers.
- Network Issues: Connectivity problems between n8n and Appwrite or Mailgun endpoints may cause timeouts or errors.
- Duplicate Provider ID: Using a non-unique provider ID that already exists will cause conflicts. Use
unique()to generate a unique ID automatically. - Disabled Provider: If the provider is created but disabled, it won't be usable until enabled.