N8n Export Workflow/Cred to Github

Hi, prior to version 1, I use to use the bottom workflow to export my workflow/cred and update the designated json files on github. But after I updated to current version 1.27, the bottom flow no longer working. So I created a new flow like the top version using the new nodes (since the old nodes no longer available), but the data saved on github is not the correct data. On github it just write “{{ $json.data }}” or some weird symbols. Usually it will dump all the cred/workflow details.

Am I using the correct new nodes? (top) And any particular settings I should use for the new nodes?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

## Share the output returned by the last node
<!-- If you need help with data transformations, please also share your expected output. -->

## Information on your n8n setup
- **n8n version:** 1,27.3
- **Database (default: SQLite):** postgres
- **n8n EXECUTIONS_PROCESS setting (default: own, main):** regular
- **Running n8n via (Docker, npm, n8n cloud, desktop app):** docker
- **Operating system:** ubuntu 20

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:

Screenshot 2024-02-20 083328

When I use the old Move Binary Data node, the right content get updated on github file.

But the Move Binary data node has been upgraded into Convert to File node. Can anyone guide me how to achieve the same results using the new node?

hello @lamanrasmi

Have you tried to use the Binary file option in the GitHub node?

The old node outputs the data as text. The new one outputs it as JSON. So to get this work, you need to use {{ JSON.stringify($json.data) }} or pass the binary content by activating the option.

using the new github node + binary file checked using this flow:
Screenshot 2024-02-20 083328
I get errors:
ERROR: Your request is invalid or could not be processed by the service
422 - {“message”:“content is not valid Base64”,“documentation_url”:“Repository contents - GitHub Docs”} - content is not valid Base64

what would be the correct flow i should use? CLI export > Read from Disk > Github (binary on) ?
or CLI export > Read from Disk > Convert to Json > Github?

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.