How can I downgrade n8n from version 1.74.3 to 1.68.1 due to Twitter OAuth issues?

Below is some guidance on this topic:

n8n Cloud Downgrading Considerations

For self-hosted n8n instances, downgrading can be achieved by reverting to the desired Docker image (or package version) after ensuring you have a backup of your workflows and data. However, when using n8n Cloud the version is managed by n8n and downgrades aren’t a self-service option.

Recommended Next Steps

1. Contact n8n Cloud Support:
   Since you’re using n8n Cloud, you’ll need to reach out to the support team. They can advise on whether reverting is possible in your setup or if an alternative workaround exists.

2. Backup Your Workflows and Data:
   If support is able to revert your installation, be sure you have a complete backup to avoid any data loss during the process.

3. Follow Up on the Twitter OAuth Issue:
   The GitHub issue you referenced indicates a specific problem with the Twitter (now X) OAuth method in version 1.74.3. In some cases, alternative solutions may be available (for instance, modifying how credentials are configured) that can allow you to continue using your current version instead of reverting.

Summary

For n8n Cloud users, the recommended approach is to contact n8n Cloud support and explain your situation regarding the Twitter OAuth connection issue. Downgrading on n8n Cloud isn’t typically done directly by users, so support is the best channel for this request.

Feel free to ask for further clarification on n8n credential or node configuration topics if needed.