🎉 Celebrate with 10% OFF on All Products! Use Code: GFEX10 Or Buy Any 2+ Items for 30% OFF with Code: GFEX30!

Gravity Forms AWS Messaging Premium Add-on Setup Guide

Updated 8 min read Gravity Forms Integrations A–Z
On this page
  1. Video walkthrough
  2. What you need
  3. Step 1: install and connect
  4. The other settings
  5. Step 2: add a feed to a form
  6. Publish to SNS
  7. Send to SQS
  8. Put an EventBridge event
  9. Invoke a Lambda function
  10. Condition
  11. What happens after a submission
  12. Sending that never doubles
  13. Retries
  14. Entry list actions
  15. Merge tags and notifications
  16. Use with payments
  17. For developers
  18. Privacy and security
  19. Troubleshooting
  20. Questions
  21. Do I pay GravityExtra for the AWS usage?
  22. Can one submission reach several AWS services?
  23. Is the secret key safe?
  24. Does it support temporary credentials?

Video walkthrough

Gravity Forms AWS Messaging Add-On Setup Guide: SNS, SQS, EventBridge & Lambda (WordPress Side)
Video setup guide: Gravity Forms AWS Messaging Watch on YouTube

The Gravity Forms AWS Messaging Premium Add-on connects a Gravity Forms form to your own Amazon Web Services account. When a form is submitted, a feed publishes a message to an SNS topic, sends a message to an SQS queue, puts an event on EventBridge, or invokes a Lambda function. The message or payload is built from the form fields with merge tags, conditional logic decides when it goes out, and the work runs in the background so the visitor never waits. Every request is signed with AWS Signature Version 4, and your secret key is stored encrypted.

What you need

  • WordPress 5.8 or newer, PHP 7.4 or newer and Gravity Forms 2.5 or newer. Tested with Gravity Forms 3.1.2 on PHP 8.3 and Gravity Forms 2.9.8 on PHP 7.4.
  • An AWS account with the topic, queue, function or event bus you want to reach, in one region.
  • An IAM user or role with an access key ID and secret access key, and permission for the actions you use: sns:Publish, sqs:SendMessage, events:PutEvents or lambda:InvokeFunction.
  • Your GravityExtra licence key. Without an active licence nothing is sent and the entry gets a note that says so.

The add-on follows the AWS API references read on 27 October 2026. SNS Publish and SQS SendMessage use the query protocol on the service host of your region; EventBridge PutEvents and Lambda Invoke use the JSON protocol. Every request is signed with AWS Signature Version 4 and goes only to the amazonaws.com endpoint of your region, so a credential can never be sent anywhere else.

Step 1: install and connect

  1. Upload and activate the add-on in Plugins.
  2. Open Forms → Settings → AWS Messaging and activate your licence key.
  3. Enter the AWS region, the access key ID and the secret access key. Choose a default action. Press Save.
  4. Press Check the connection. The add-on makes a harmless list call for the default action with your credentials. Nothing is published and nothing is invoked. A key that may not list resources still shows that AWS knows the credentials, which is enough.
The AWS Messaging settings screen in Gravity Forms: the licence box, the AWS region, the access key ID, the encrypted secret key, the default action and the Check the connection button
The settings: your own AWS region, access key and encrypted secret key, and the default action for every feed.

The secret access key is encrypted before it is saved, with a key made from your site’s own security salts, and it is never shown again. Leave the box empty to keep the stored key, or tick Remove the stored secret key and session token when saving to delete it. For temporary credentials from AWS STS you can also store a session token, which is encrypted the same way.

The other settings

  • AWS region: the region of your topics, queues, functions and buses, for example us-east-1 or eu-central-1. The add-on builds the service host from it.
  • Default action: the action a new feed starts with. Each feed can override it.
  • Daily cap: after this many messages in one day (UTC), over all feeds, the add-on stops and writes a note. Empty or 0 means no cap. AWS bills every request.

Step 2: add a feed to a form

  1. Open the form, go to Settings → AWS Messaging and press Add New.
  2. Give the feed a name that says what it does, for example Order to SNS.
  3. Choose the Action. The fields below change to match it.
  4. Fill in the target and the message or payload, turn on the Condition if the send is only for some entries, then save.
An AWS Messaging feed: the action switch, the SNS topic ARN, the subject and message built from form fields with merge tags, and the condition
A feed: the action, the target in your AWS account, and the message built from the form.

Publish to SNS

Enter the topic ARN, for example arn:aws:sns:us-east-1:123456789012:orders, and the message with merge tags. An optional subject is used by email subscriptions of the topic. For a FIFO topic (its name ends in .fifo) set a message group ID; a deduplication id is added for you so a retry never publishes twice. Leave the topic empty to use the default topic in the settings.

Send to SQS

Enter the queue URL, for example https://sqs.us-east-1.amazonaws.com/123456789012/orders, and the message body. A JSON body is sent exactly as written, so a consumer can read structured data. A FIFO queue takes a message group ID, with the deduplication id added for you.

Put an EventBridge event

Set the source (for example com.yoursite.forms), the detail type (for example Form submitted), and the detail, which is the data of the event. Valid JSON is sent as-is; any other text is sent as a JSON string. The event goes to the default bus unless you name another bus. Rules on the bus can then route the event to other AWS services.

Invoke a Lambda function

Enter the function name or ARN and the payload (the event your function receives). Choose Event to fire and forget, which is best for forms, or RequestResponse to wait for the function to run. A function that returns an error is reported on the entry, and the request is not repeated.

Condition

The same rules as Gravity Forms notifications: send only for the Premium plan, only when the Urgent box is ticked, only for one country, and so on. A form can have as many feeds as you like, each with its own action, target, message and condition, so one submission can reach several AWS services at once.

What happens after a submission

The entry is saved and the confirmation is shown at once. A background job then runs each matching feed: it signs the request with AWS Signature Version 4, sends it to the service host of your region, and writes a note on the entry with the action and the message id that AWS returned (the SNS message id, the SQS message id, the EventBridge event id, or the Lambda request id). A refusal from AWS is written in the note with the AWS error.

The AWS Messaging box on a Gravity Forms entry: the action, the status sent, the target and the message id returned by AWS
Every send on the entry: the action, the status, the target and the AWS message id.

Sending that never doubles

Each send carries a deduplication token made from your site, the entry, the feed and the send number. For a FIFO topic or queue that token is the AWS deduplication id, so a repeated request is harmless and the add-on retries safely. For a standard target the token is written in the note, so you can find the one request in your AWS logs.

Retries

  • When AWS cannot be reached at all (the name does not resolve, the connection is refused) or throttles the request, nothing was sent, so the job tries again after 1 minute, 5 minutes, 30 minutes, 2 hours and 12 hours. A longer Retry-After from AWS wins.
  • When the request may have reached AWS but no clear answer came back (a time-out after the request left, a reset connection, an HTTP 5xx answer), the add-on does not repeat it for a standard target. The entry is marked as unsure and the note gives the deduplication id to look for in CloudWatch or CloudTrail. A FIFO target is retried because its deduplication id makes a repeat safe.
  • Refusals (wrong credentials, no permission, an invalid request, a missing target) are final and explained in the note.
  • A job for an entry that was already sent does nothing, and a lock stops two jobs from sending the same entry at the same time.

Entry list actions

  • Send to AWS (skip sent): runs the feeds of the selected entries that have not been sent. Entries that are sent, being sent or unsure are skipped.
  • Send to AWS again (sends another message): runs again on purpose, with a new deduplication token, for example after you checked that an unsure message never arrived.

Merge tags and notifications

Use these merge tags in notifications and confirmations. Add _ and a feed id to read one feed, for example {aws_status_12}; without it the newest result of the entry is used.

  • {aws_status}: queued, retrying, sending, sent, unsure or fail.
  • {aws_message_id}: the id AWS returned for the message.
  • {aws_action}: sns, sqs, events or lambda.

Forms with an AWS Messaging feed also get two notification events: AWS: the message was sent and AWS: the message could not be sent. Each one is sent once per entry and feed, so your team hears about a problem at once.

Use with payments

The feeds follow the Gravity Forms add-on framework, so a payment add-on that delays feeds until the payment is complete also delays the send: an order event goes out only for paid orders.

For developers

  • gform_aws_messaging_request (filter, also per form and per feed): change the action, the target and the message parts before the request is signed; return something that is not an array to cancel the send for this entry (a note says so).
  • gfawsmsg_send_sent (action): AWS accepted the message. Arguments: the result, the entry, the feed and the form.
  • gfawsmsg_send_failed (action): the send failed or is unsure. Arguments: the entry, the feed, the form and the reason.

Privacy and security

The message or payload built from the form is sent to your own AWS account, to an amazonaws.com endpoint in your region, to publish, send, put or invoke. AWS processes the data under its own terms, so mention AWS in your privacy policy. The secret access key and the session token are encrypted at rest, only used to sign the request, and never written to a note.

Troubleshooting

  • Nothing is sent: read the entry notes. Every reason is written there: no licence, no region or credentials, a missing target, an empty message, the daily cap, or the AWS error.
  • Credentials not accepted: the access key, the secret key or the region is wrong, or the IAM user has no permission for the action. Check them and use Check the connection.
  • Target not found: the topic ARN, queue URL, function or bus does not exist in this region. Copy it again from the AWS console.
  • The entry says unsure: look for the deduplication id from the note in your AWS logs before you use Send again, or use a FIFO topic or queue so retries are always safe.

Questions

Do I pay GravityExtra for the AWS usage?

No. AWS bills your own account for every request. The add-on is a licence for the software, updates and support.

Can one submission reach several AWS services?

Yes. Add one feed per action. A single entry can publish to SNS, send to SQS, put an EventBridge event and invoke a Lambda function.

Is the secret key safe?

It is encrypted with a key made from your site’s security salts, never shown again, and only used to sign the request to your region. Notes and logs never contain it.

Does it support temporary credentials?

Yes. Store an STS session token next to the access key and secret key; it is encrypted and added to the signed request.

Still need help?

Our support team answers tickets every day, usually within a few hours.

0
0
Your Cart
Your cart is emptyReturn to Shop
🔥 FREQUENTLY BOUGHT TOGETHER
Complete Combo & Save 40%!
ITEM IN YOUR CART
Gravity Forms Klaviyo Add-on
$39.00/yr
+
🎁 RECOMMENDED ADD-ON SAVE 40% OFF
Original Price: $39.00/yr
Bundle Special Price: $23.40/yr