Fixed IPs

By default, webhook deliveries come from any Memberfy address. If your destination only accepts calls from known addresses (a firewall, a provider's IP list), check Send from fixed IPs when creating the webhook: deliveries then come only from these two addresses.

#How to use them

1. When creating the webhook, check Send from fixed IPs (in Settings › Integrations and APIs, Webhooks tab; see Integrations & APIs). The option already shows both IPs, and so does the webhook's detail.
2. In the destination's firewall, allow both IPs, on port 443. A delivery can come from either one.
3. Block the rest, if you want: with the option checked, no delivery comes from another address.
4. Click Send test to check that the delivery gets through.

Allow both addresses even if you only see one of them in your logs.

Any change to these addresses is announced in advance, with time to update the firewall.

#Workflows: the Call webhook block

On the Business and Scale plans, the calls of the workflows' Call webhook block go out from these same two IPs, with no option to tick, up to 10,000 calls a month. Past that, the rest go out from changing IPs until the month turns, and the owner gets a notice in the bell. On the other plans, calls go out from changing IPs. The run history shows where each call went out from. The month is the calendar month in the community's time zone: the count restarts at midnight on the 1st and does not carry over on an annual plan.

Fixed IPs change nothing about the signature: verify the signature of every delivery the same way. Allowing the IP doesn't replace verification.

#Related

• Webhooks
• Webhook events
• Workflows