Posts made by sparkwise

@girish said in Using the n8n CLI:

I put this in the docs as well - https://docs.cloudron.io/apps/n8n/#cli

In the docs, it could be helpful to linking "n8n CLI" to the documentation link: https://docs.n8n.io/reference/cli-commands/

@girish That worked perfectly! Thank you.

n8n ships with a n8n CLI (found on Cloudron at /app/code/node_modules/.bin/n8n.) When I try to use it to export a workflow, I run into this...

/app/code/node_modules/.bin/n8n export:workflow --backup --output=/tmp/n8n/

Error exporting workflows. See log messages for details.
EROFS: read-only file system, mkdir '/root/.n8n'

Is there a different way to invoke the command that works on Cloudron?

@bubonicfred Thanks for sharing! I hadn't noticed it yet.

@nebulon Thank you for pointing out that setting MAILER_INBOUND_EMAIL_DOMAIN changes the @false email address. In digging in a bit deeper, I do think it may make sense to ignore this. The IMAP Email Channel does works, which would presumably be compatible with Cloudron Email. The forwarding address seems to enable automatically matching and connecting incoming emails to pre-existing conversation threads. This is nice but not strictly necessary.

@nebulon We recently set up Chatwoot, and it's been great so far!

The work to support the IMAP Email Channel that was discussed in this thread has since been finished and released. I was able to configure an Email Channel with IMAP and SMTP details using a Google account, so presumably this could work with Cloudron email now, too. This allowed me to set up a dedicated email address for Chatwoot-based support.

The one piece that I wasn't able to get configured fully was the "conversation continuity" discussed above. I'm still seeing the "Forward to Email" address provided by Chatwoot as xxxxxxxx@false. It's not clear to me if some configuration with Cloudron Email (for the inbound email service) might address this, but it seems worth revisiting now that the IMAP integration is in place.

@girish Thank you!

I'm looking to convert markdown to HTML in a n8n workflow. There are no built-in n8n nodes that do this, so it requires an external node module. marked seems like a good candidate for this.

Based on @girish's comment on Using handlebars.js, it sounds like this would need to be hardcoded into the Dockerfile. Would it be possible to include marked (or something equivalent) in an app update?

Thank you!