How Do I Regenerate My Automation Secret Key in Feedspace?

Overview

Regenerating your Automation Secret Key replaces the existing key with a new one. The old key is invalidated immediately. Any integration platform (such as Pabbly Connect, Make, Zapier, or n8n) that is currently using the old key will fail to authenticate until you update it with the new key.

Regenerate your key if it has been accidentally exposed, shared with someone who no longer needs access, or if your security policy requires periodic credential rotation.

Steps to Regenerate the Key

1. In the left sidebar, click Automation under the Workspace section.
2. You land on the Automation tab by default. Scroll down to the Automation Secret Key section.
3. Click the Regenerate button next to your current key.
4. A confirmation prompt will appear. Confirm the action to proceed.
5. A new Automation Secret Key is generated and displayed immediately. Click Copy to copy it to your clipboard.
6. Paste the new key into every integration that previously used the old key.

Important: What Happens to Your Existing Integrations

As soon as you confirm the regeneration, the old key is permanently invalidated. Integrations using the old key will stop authenticating instantly. Update the key in each platform before those workflows run again to avoid missed triggers or failed actions.

If you use more than one automation platform with Feedspace, update the key in all of them. For example, if both Pabbly Connect and Make use your Feedspace connection, you need to re-enter the new key in each platform separately.

When to Regenerate

• Key exposed accidentally: If the key was committed to a public repository, pasted in a chat, or otherwise made visible to unintended parties, regenerate it immediately.
• Access revoked: If a team member or contractor who had access to the key no longer works with you, regenerate the key so they cannot use it going forward.
• Security rotation policy: If your organisation requires periodic credential rotation, regenerate the key on your scheduled cycle and update all integrations at the same time.

Updating the New Key in Your Integration Platforms

Pabbly Connect

Open the workflow in Pabbly Connect, click the Feedspace trigger or action step, disconnect the existing connection, and re-connect using the new key.

Make

In Make, go to Connections, find your Feedspace connection, and edit it to replace the key. All scenarios that use that connection will begin working again once saved.

Zapier

In Zapier, open the connected account for Feedspace and update the API Key field with the new Automation Secret Key. Re-test the connection to confirm it works before re-enabling your Zaps.

n8n

In n8n, navigate to Credentials, open the Feedspace credential, and replace the key value. Save and re-test any workflows that connect to Feedspace.

What You Can Do Next

• If you have not generated a key yet, see the article on generating your Automation Secret Key for the first time.
• If you need a separate credential for REST API access, generate an API Key from the API tab in the Automation section.