On form submission Trigger with attachment

Questions
,
1

simple storing of form data, insainly complex for some reason

I have read all these posts about the error and NONE are this scenario / use-case because I am NOT having a URL but rather the file is in the form as binary data. Why is this so complicated and why does the node not automatically handle this as part of the backend logic and use its own internal webhook like the Gmail send and wait for a response. Similarly it can host the file url and give Airtable what it wants. I am so spun a round at the momentā€¦ I even tried uploading the attachment to google drive to reproduce some of the other posts, just so I can get a real URL to follow along with no luck. At this point I give up, there has to be a simpler way?

ā€˜Attachmentsā€™ expects a array but we got object

Please share your workflow

** (note the code shows localhost but it is actually using a real url https then auto [dot] cnxlab [dot] us **

Information on your n8n setup

  • n8n version: = 1.86.1
  • Database is the default SQLite
  • n8n EXECUTIONS_PROCESS setting (default: own, main): form
  • Running n8n via (Docker, npm, n8n cloud, desktop app): npm
  • Operating system: Windows 11, v 24H2

I was able to get it to work by making a folder in drive sharing it with everyone who has the link so its public and security by obscurity then the other posts worked (permisisons issue aparenlty in this use case) this however is insainly coverly complicated and over engineered just to handel the file attachment that the built-in AirTable node operation can easily handle internal to itself like other nodes using the webhook operation similar to again Gmailā€™s Node - ā€œSend and Wait Messageā€, IMO.

I am still going to leave this open to see if there is an easier way?

1 Like
2

Hi @GenXerator,

Just had this issue yesterday. Add this to your .env file and it should update.
webhook_url=mysite.

Best,

Robert

3

@rbreen yes that is already there but gets lost when you copy and past the work flow here - disclaimer is above in post. wasenā€™t sure how else to communicate that here. I do have it work around working using drive at the moment.