Skip to main content
Triggr creates expiring Password Pusher links for passwords and files, on pwpush.com or your own server.

​
Set up Password Pusher

1

Find your hostname

On pwpush.com, use your region’s host, eu.pwpush.com or us.pwpush.com (the footer shows it; see data regions). A self-hosted server needs HTTPS at a public address, with Triggr’s IP addresses allowed through any firewall.
2

Copy your API token

On pwpush.com, open /api_tokens on your region’s host, such as https://eu.pwpush.com/api_tokens. On a self-hosted server, select API Token in your account menu and click the blurred token to reveal it.

​
Connect it in Triggr

1

Open the configuration

Go to Integrations > Password Pusher and click Configure on the Base Configuration card.
The Base Configuration card with Status Not Configured, Admin Consent Not Required and a Configure button.
2

Enter the host and token

Enter the host name alone in Hostname, adding a port only if it isn’t 443 (pwpush.example.com:8443), and the token in ApiToken. Turn on Allow insecure TLS for a self-signed certificate, then click Save Configuration.
The Password Pusher configuration window with ApiToken and Hostname fields, an Allow insecure TLS switch under Advanced, and a Save Configuration button.

​
Create pushes from workflows

Create a Push (Authenticated) takes JSON in jsonBody, in Password Pusher’s JSON API format. Send the response’s html_url to the recipient.
  • The link expires at whichever limit comes first. retrieval_step adds a click-through page so link previews don’t use up views; passphrase and note are optional.
  • Create File Push (Authenticated) takes one file_push[files][] File row per file in its Form Data (multipart) editor, plus optional Text fields file_push[payload], file_push[expire_after_days], file_push[expire_after_views], file_push[retrieval_step] and file_push[passphrase]. File pushes need a pwpush.com plan with file uploads, or PWP__ENABLE_FILE_PUSHES on your server.
  • Create a Push sends no token, so it only works on servers that allow anonymous pushes. Retrieving a push by its urlToken counts as a view.

​
Troubleshooting

Check ApiToken is current, pasted in full, and from the same server or region as Hostname.
The server doesn’t accept anonymous pushes. Use Create a Push (Authenticated).
Check Hostname has no https:// or path, and uses your region’s host rather than pwpush.com. For certificate errors, turn on Allow insecure TLS.
Every field name must start with file_push[. Check your plan includes file uploads, or set PWP__ENABLE_FILE_PUSHES on your server.