Hey Andrew!
Good questions
For the first two, I’d suggest checking out the formatAirtableRecordAsSlackAttachment
function. This is where we actually choose which fields to show in the Slack attachment (and the ordering), so you could update that code to use whichever fields you want.
Pagination is a bit trickier, and there are a few ways to do it. I’d recommend checking out the pageSize
param to the list records API endpoint, and the offset
that is returned in the response. You could fetch only 10 records on the first request by setting pageSize
to 10, and then use the offset
to fetch another 10 records on a subsequent request (maybe using Slack buttons).
JB
Hey Andrew!
Good questions
For the first two, I’d suggest checking out the formatAirtableRecordAsSlackAttachment
function. This is where we actually choose which fields to show in the Slack attachment (and the ordering), so you could update that code to use whichever fields you want.
Pagination is a bit trickier, and there are a few ways to do it. I’d recommend checking out the pageSize
param to the list records API endpoint, and the offset
that is returned in the response. You could fetch only 10 records on the first request by setting pageSize
to 10, and then use the offset
to fetch another 10 records on a subsequent request (maybe using Slack buttons).
JB
Thank you, JB. I really appreciate the support.
Unfortunately though, I’m not a developer; I’m able to read code well enough to tweak it, but am not sufficiently versed to add functionality.
BY NO MEANS would I ever assume it’s your role to help at that level or add features to your repo!
But I would like to ask here, if there are any freelance developers that have already started working with your code, interested in helping us take our nascent Airtable bots to the next level. If so, please reply here or email me at acenright@gmail.com.
Thanks all,
A.