This topic was automatically generated from Slack. You can find the original thread here.
make give live : Hi I’, trying to use the airtable > slack pipeline but I can’t save the event listener in slack for some reason. It just won’t let me click save 
Any ideas please?
Dylan Sather (Pipedream) : it’s possible it already saved your changes. Could you try refreshing the page and seeing if that works?
Since this is an issue with Slack’s UI, if that doesn’t work, I’d recommend reaching out to their team - they usually provide fast support
make give live : Hey Dylan, it was my bad - hadn’t set up the bot event part so it wouldn’t save.
Dylan Sather (Pipedream) : got it 
make give live : however it works when I send a test but not when I make actual changes to the table. They get through to slack but not to pipedream - any ideas please? MGL Airtable Slack Messages -> Webhook - Pipedream
make give live : my url endpoint is an integromat webhook https://hook.integromat.com/mly9e4dup7ihg48ysnnefc761l6pbksy
Dylan Sather (Pipedream) : Have you tried using the Airtable event sources? These listen for new / updated / deleted records from Airtable directly, instead of relying on the Airtable -> Slack integration. That’s a much simpler and more robust integration - let me know if that helps
make give live : just looking at that now and I’m giddy with excitement! It could be just the ticket!
make give live : I’m struggling with the records part - I’m assuming that’s why it’s failing - is there a tutorial I can follow to see how to make this work please?
make give live : at null.createError (/opt/ee/node_modules/axios/lib/core/createError.js:16:15)
at null.settle (/opt/ee/node_modules/axios/lib/core/settle.js:17:12)
at IncomingMessage.handleStreamEnd (/opt/ee/node_modules/axios/lib/adapters/http.js:236:11)
at IncomingMessage.emit (events.js:203:15)
at null.endReadableNT (_stream_readable.js:1145:12)
at process._tickCallback (internal/process/next_tick.js:63:19)
Dylan Sather (Pipedream) : Take a look at this workflow. I’d recommend taking a look at the Airtable API docs to see how they expect record updates to be passed, but you can see an example in the format_airtable_records step of that workflow. We then pass that formatted record data to the Airtable update step.
I’d recommend taking a look at these docs for more information about how to use code steps, and how data is passed between steps:
• Node.js code docs
• Step exports (returning data from steps to use in future steps)
• Step params (passing data to steps)
make give live : really struggling with this even hardcoding values. It says it can’t find any records yet I’ve hardcoded the explict recordid that I want to update…
make give live : please help - if I can get this working I’ll be a customer for life!
Dylan Sather (Pipedream) : just to confirm, if you select that first record in Airtable and look at the URL of the record ID in your browser’s address bar, is it the same as the allocations ID? Or does that allocations ID refer to something else?
make give live : hey no , that would be the source record id. I have stored the target record id as a field in the source table and I want to update the target table’s record that has a record id matching allocations ID
Dylan Sather (Pipedream) : so I could be misunderstanding, but it seems like you might be passing the wrong record ID / table combination in this case - is that right? Based on the screenshot it looks like you’re trying to update the first record in the allocations table, but since there’s no record ID matching the one you’re passing in the allocations table, the update step fails
