STEP 1
Connect Cmercury and Pushcut
Save credentials in WEXTL once. We store them encrypted and reuse the authorization across every workflow [3]. No coding or API skills required.
Cmercury and Pushcut Integration
Build communication workflows between Cmercury and Pushcut 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 Cmercury and Pushcut
Detailed info you need to know about Cmercury and Pushcut integrations in WEXTL. Explore which modules apps support and how you connect them.
How to connect Cmercury to Pushcut
Set up your Cmercury and Pushcut integration in 3 simple steps [2] — no coding required. Up to 10 minutes setup.
STEP 2
Build a workflow
Paste selected Cmercury and Pushcut 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 Cmercury and Pushcut. Use filters or leverage a JS custom code step in between — everything is on the canvas.
How does the integration between Cmercury and Pushcut work in WEXTL?
WEXTL exposes actions and triggers for Cmercury and Pushcut 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.
Pushcut triggersCmercury actions
Pushcut modules
- Cancel ExecutionCancels a delayed Automation Server action before it runs.
- Create SubscriptionRegisters a URL that Pushcut calls whenever the named online action runs.
- Delete Delivered NotificationRemoves a notification you already sent from your devices.
- Delete Scheduled NotificationDeletes a submitted notification from your devices, including one that is still scheduled.
- Delete SubscriptionRemoves an online action subscription so Pushcut stops calling its URL.
- Execute Automation Server ActionRuns a shortcut or a HomeKit scene on your Pushcut Automation Server.
- List Automation ServersRetrieves a list of the Automation Servers in your Pushcut account and whether each one is connected.
- List DevicesRetrieves a list of the devices registered in your Pushcut account.
- List Logged NotificationsRetrieves a list of the notifications recorded in your Pushcut notification log.
- List NotificationsRetrieves a list of the notifications defined in your Pushcut app.
- List SubscriptionsRetrieves a list of the online action subscriptions created with this API key.
- Make an API CallPerforms an arbitrary authorized API call.
- Move ImageRenames an image you uploaded to Pushcut.
- Send Smart NotificationSends one of your defined Pushcut notifications, optionally with a new title, text, image, or actions.
- Update ImageUploads an image to Pushcut under a name you choose, replacing any image with that name.
- Watch Logged NotificationsTriggers when a new notification appears in your Pushcut notification log.
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 Cmercury and Pushcut.
Connect your Cmercury and Pushcut 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 Pushcut's "Watch Logged Notifications" fires, WEXTL can "Activate a Mailing List" in Cmercury. Cmercury has 18 actions (including Activate a Mailing List, Add a Contact, and Add a Message); Pushcut has 15 actions (including Cancel Execution, Create Subscription, and Delete Delivered Notification). 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. Cmercury-to-Pushcut 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 Cmercury (or Pushcut) 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 Cmercury + Pushcut 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 Cmercury and Pushcut integration.
- Cmercury and Pushcut integration source code, module specs and credentials implementation.
- Our Cmercury and Pushcut integration documentation, structured input and output parameters, scopes, and authentication methods.
- Official vendor API documentation for Cmercury and Pushcut — 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.
- Cmercury integration information
- Pushcut integration information
- WEXTL® Scheduling
- WEXTL® Pricing and Trial
- WEXTL® Apps Library