Add PushWoosh Connector

Audience: Low-code Engineers

Skill Prerequisites: Actions, Tokens, Connectors

Creates a new PushWoosh connector in a connector group. The connector stores the PushWoosh API access token that the Create PushWoosh Notification action uses to send push notifications. The action can save the ID of the new connector in a token, so later actions can use or update it.

The API access token is saved encrypted.

note

This action requires the Push Notifications feature to be licensed.

Typical Use Cases

• Let each customer or tenant save its own PushWoosh account from a setup form
• Create PushWoosh connectors from a setup workflow instead of by hand
• Save the new connector's ID so you can update or delete it later

Don't use it to

• Change an existing PushWoosh connector. Use Update PushWoosh Connector instead.
• Check that the token works. The action saves it without contacting PushWoosh, and Test Connector doesn't support PushWoosh connectors.
• Add a connector of another type. Use Add Connector instead.

Related Actions

Action Name	Description
Update PushWoosh Connector	Changes the details of an existing PushWoosh connector.
Get Connector	Reads the details of a connector.
Delete Connector	Removes a connector.

Input Parameter Reference

Parameter	Description	Supports Tokens	Default	Required
Group Title	The PushWoosh connector group to add the connector to. The list shows PushWoosh groups only. The saved value is the group's ID.	No	empty string	Yes
Entry title	The name of the connector, for example PushWoosh - [AppName].	Yes	empty string	No
API Access Token	The PushWoosh API access token. Saved encrypted.	Yes	empty string	No
EntryId Token Name	The name of a token to save the new connector's ID in, for example PushWooshConnectorId. Brackets are optional.	No	empty string	No

Output Parameters Reference

Parameter	Description
[<EntryId Token Name>]	The ID of the new connector, a GUID. It's only set when EntryId Token Name has a value.

Considerations

• The group decides the connector type. If Group Title is empty, the action fails with Invalid GroupId. If no group has that ID, it fails with Connector group (id: ...) not found.
• Nothing is required by the connector. An empty API Access Token is saved as empty, and sending notifications will fail.
• The token isn't tested. A wrong token is saved without an error. You'll only find out when a notification is sent.
• Names aren't unique. Running the action twice with the same title creates two connectors.
• Keep secrets out of the action. The editor shows API Access Token as plain text. Pass the value through a token, for example from a form, instead of typing it into the action.

Examples

tip

To understand how to use the below examples, please see Running Examples.

1. Save a PushWoosh access token

This action adds a connector to the PushWoosh group with ID 7, using the access token from a form. The new connector's ID is saved in [PushWooshConnectorId]. Replace 7 with the ID of your PushWoosh group, or pick the group in the editor after importing.

{
    "Title": "Add PushWoosh Connector",
    "ActionType": "cs.pushnotifications.pushwoosh.add",
    "Description": "Save the PushWoosh API access token",
    "Parameters": {
        "Group": "7",
        "EntryName": "PushWoosh - [AppName]",
        "ApiAccessToken": "[PushWooshApiToken]",
        "EntryIdTokenName": "PushWooshConnectorId"
    }
}

Revised 09/26/2026