STEP 1
Connect AWS SQS and Cmercury
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
AWS SQS and Cmercury Integration
Build communication workflows between AWS SQS and Cmercury on a visual canvas — set up data fields sync between apps once and let data flow when events come automatically. Integration will work without code and your team will see the workflow inside WEXTL® builder.
3-day trialCancel anytimeUp to 10 minutes quick set up
- GDPR
- Data Encryption
- 2FA
- Local Data Region
Learn about AWS SQS and Cmercury
Detailed info you need to know about AWS SQS and Cmercury integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect AWS SQS to Cmercury
Set up your AWS SQS and Cmercury integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected AWS SQS and Cmercury nodes onto the canvas [4], or describe what you want and WEXTL wires the flow together with AI Builder.
STEP 3
Map your data
Choose which fields need to sync between AWS SQS and Cmercury. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between AWS SQS and Cmercury work in WEXTL?
WEXTL exposes actions and triggers for AWS SQS and Cmercury that help you connect apps and automate repetitive tasks [1]. A trigger is an event that happens, an action — a step that performs when the event has occurred.
AWS SQS triggersCmercury actions
AWS SQS modules
- Add PermissionAdds a permission to a queue for a specific principal.
- Cancel Message Move TaskCancels a running message move task.
- Change Message VisibilityChanges the visibility timeout of a received message.
- Change Message Visibility BatchChanges the visibility timeout of multiple received messages in one request.
- Create QueueCreates a new SQS queue. FIFO queues must have a name ending in .fifo and set the FifoQueue attribute.
- Delete MessageDeletes a received message from a queue, acknowledging successful processing.
- Delete Message BatchDeletes up to 10 messages from a queue in a single request.
- Delete QueueDeletes an SQS queue and all its messages. This action is irreversible.
- Get Queue AttributesReturns attributes of an SQS queue.
- Get Queue UrlReturns the URL of an existing SQS queue by name.
- List Dead Letter Source QueuesLists source queues that have a dead-letter queue configured.
- List Message Move TasksLists active and completed message move tasks for a source queue.
- List Queue TagsReturns the tags assigned to an SQS queue.
- List QueuesLists SQS queues in the region, optionally filtered by name prefix.
- Make an API CallPerforms an arbitrary authorized API call to the Amazon SQS endpoint.
- Purge QueueDeletes all messages from a queue without deleting the queue itself. This action is irreversible.
- Receive MessageRetrieves up to 10 messages from a queue. Messages become invisible for the visibility timeout; delete them to acknowledge processing.
- Remove PermissionRemoves a permission from an SQS queue.
- Send MessageSends a message to an SQS queue.
- Send Message BatchSends up to 10 messages to an SQS queue in a single request.
- Set Queue AttributesSets the attributes of an SQS queue.
- Start Message Move TaskStarts a message move task to move messages from a dead-letter queue to a source queue.
- Tag QueueAdds or updates cost-allocation tags on an SQS queue.
- Untag QueueRemoves cost-allocation tags from an SQS queue.
- Watch Queue MessagesTriggers when new messages arrive in an SQS queue. Messages become invisible for the visibility timeout; chain Delete Message to acknowledge.
Cmercury modules
- Activate a Mailing ListActivates an archived mailing list using the API and returns a successfully activated list.
- Add a ContactAdds a contact to the mailing list using the cmercury API. If the contact doesn't already exist, it will be created.
- Add a MessageAdds a new message using the API.
- Add a PhoneAdds a phone number to the SMS list without adding it to the regular mailing list.
- Archive a Mailing ListArchives a mailing list using the provided API and returns a successfully archived list.
- Create a Mailing ListCreates a mailing list using the API.
- Create a Suppression ListCreates a suppression list using the API.
- Get Contact DetailsRetrieves all contact attributes from the email list using this API.
- Get Contact StatusRetrieves the status of a contact, such as Active, Bounced, Unsubscribed, or Trashed.
- Get Mailing ListRetrieves all mailing lists in your cmercury account, including details like list ID, name, sender name, from email address, active subscriber count, and last message date.
- Schedule a MessageUses this API to schedule a message for a future time.
- Send a MessageSends a created message using the API.
- Send a Test MessageSends a quick test message created in the panel.
- Update a ContactUpdates a contact in the mailing list.
- Update a Contact's StatusUpdates the status of a member record on a list using the API.
- Update a ListUpdates an existing mailing list using this API.
- Update a MessageUpdates a message using the API within the panel.
- Upload a Record to a Mailing ListUploads member records to a mailing list using a globally accessible FTP-hosted file.
Frequently asked questions
Common questions about connecting AWS SQS and Cmercury.
Connect your AWS SQS and Cmercury accounts once, pick a trigger in one app and an action in the other, then map the fields so data flows automatically between them. [3]
Example: when AWS SQS's "Watch Queue Messages" fires, WEXTL can "Activate a Mailing List" in Cmercury. AWS SQS has 1 trigger (including Watch Queue Messages); Cmercury has 18 actions (including Activate a Mailing List, Add a Contact, and Add a Message). Add filters and transforms between steps when you need them. [1]
Yes — the integration works in both directions. Use each app's triggers to start a workflow and the other app's actions to update it. [2]
No. AWS SQS-to-Cmercury automations are built visually on the canvas. You can optionally add custom JavaScript with Functions when you need advanced logic. [4]
Yes. Trigger-based automations start the moment AWS SQS (or Cmercury) fires a new event — webhook-backed apps run within seconds, and polling-only apps re-check on a schedule you control. [7]
A first automation typically takes 5–10 minutes: connect each app's credential once, drop a trigger + action onto the canvas, map the fields, and turn the workflow on.
You can build your AWS SQS + Cmercury automation on a 3-day trial with every feature unlocked. Cancel anytime. For your protection, a small deposit is charged to your card when your trial starts. It counts toward your first payment and is non-refundable. [8]
References
List of sources used to gather information about the AWS SQS and Cmercury integration.
- AWS SQS and Cmercury integration source code, module specs and credentials implementation.
- Our AWS SQS and Cmercury integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for AWS SQS and Cmercury — used to verify field meanings, authentication flows, and anything our own specs don't fully capture.
- WEXTL® visual workflow builder, anonymized data from our technical support team.
- AWS SQS integration information
- Cmercury integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library