# Mailgun - API key and webhook - Credential setup | Docs - nodulz

Source: https://nodulz.com/docs/credentials/mailgun

Language: en

Credential type in nodulz : `esp:mailgun`.

## Create access

In Mailgun, open Account Settings → API Keys and create a key with required permissions. A Domain Sending Key may suffice for sending from one domain. Retrieve the separate HTTP webhook signing key for signed events.

## Configure in nodulz

In your instance, open Credentials, select the type above, name the credential and complete these fields:

```text
apiKey, baseUrl, webhookSigningKey
```

Save the credential, then select it on relevant nodes. URLs or parameters marked as node settings belong directly on that node.

## Things to check

Choose the US or EU endpoint matching the domain. A domain-limited sending key does not permit every administrative operation. Set the domain on the relevant node.

Verify an operation with expected permissions and data before publishing. Keep secrets out of logs and revoke them with the provider when no longer needed.

## Official references

- [Provider documentation 1](https://documentation.mailgun.com/docs/mailgun/user-manual/api-key-mgmt/rbac-mgmt)
- [Provider documentation 2](https://documentation.mailgun.com/docs/mailgun/user-manual/webhooks/securing-webhooks)

See also : [Credentials and rotation](/docs/credentials), [Node catalog](/docs/nodes).

## Explore further

- [Features - nodulz](https://nodulz.com/product/overview)
- [Node catalog - nodulz](https://nodulz.com/product/catalog)
- [MCP server - nodulz](https://nodulz.com/product/mcp)
- [Pricing - nodulz](https://nodulz.com/pricing)
- [Use cases and workflow automation - nodulz](https://nodulz.com/use-cases)
- [Choose what your workflows can do. - nodulz](https://nodulz.com/compare)
- [Documentation - nodulz](https://nodulz.com/docs)