When Should You Use the Zapier Classic Auth?

Pulsetic offers two Zapier integrations to help you automate workflows easily. However, due to technical limitations confirmed by the Zapier support team, the standard integration may not work with non-Gmail email accounts.

If you’re seeing the error Error 400: redirect_uri_mismatch when trying to connect Pulsetic with Zapier, it likely stems from this email provider limitation.

To resolve this, we provide an alternative integration method using your Pulsetic token key - known as Zapier Classic Auth. This method ensures compatibility regardless of your email provider.

When to Use Zapier Classic Auth

• You’re using a non-Gmail or custom email domain with Zapier.
• You encounter the Error 400: redirect_uri_mismatch error during setup.
• You want to connect Pulsetic with Zapier using your token key directly.

How to Use Zapier Classic Auth (Step-by-Step)

1. Get Your Pulsetic API Key

   Log into your Pulsetic dashboard, choose the monitor and navigate to Alerts > Zapier to copy your personal API key.

2. Go to Zapier Classic Integration

   Use this Zapier Classic Auth link to access the alternative connection setup.

3. Authenticate with API Token

   Paste your API key when prompted to authorize the connection.

4. Create Your Zap

   Once authenticated, you can create Zaps as usual - choosing Pulsetic as your trigger or action app.

If you have any questions or issues during setup, feel free to contact our support team.