In certain edge cases, however, this will create some issues. In almost every case, this is a fine strategy. I usually find it faster to just send record ID to Make and pickup all other data from the record there, rather than attach all needed data to webhook URL This is how you would send just the Record ID on its own to a webhook in Make: let config = nfig() Then you would have full access to all of your field values. However, as also mentioned in that thread, if you’re using an integration tool like Make’s webhooks, the simplest & easiest & best thing to do would be to just send the RecordID on its own to Make’s webhook, and then use the Airtable - Get A Record module to pull in all the rest of the field values from your record, including any linked record fields, attachment fields, etc. If you need to send multiple pieces of data to your webhook, that thread shows you how to write the script for that. This is how you would send just the Record ID to a webhook in Make: let config = nfig() let url = ` … The easiest & best thing to do would probably be to just send the RecordID on its own to Make’s webhook, and then use the Airtable - Get A Record module to pull in all the rest of the values from your record, including any array fields like your linked record field. This expression is not callable Automations Your Expense Record field is an array (not a string) because it is a linked record field.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |