ContributionsMost RecentMost LikesSolutionsRe: Bringing attention to the End of Life for Webhooks I understand why Quickbase would want to get rid of the webhook feature, but it is definitely a step in the wrong direction for several reasons. 1. Lack of Collaboration and Visibility: Pipelines lack the cross-team collaboration and visibility inherent in webhooks. To replace webhooks, pipelines need shared access among admins and a comprehensive view of related pipelines for efficient maintenance. 2. Synchronous Execution: Webhooks offer synchronous execution, ensuring instant response to events, unlike pipelines which might introduce delays. 3. Efficient Bulk Updates: Webhooks excel in handling bulk updates efficiently, minimizing overhead by repeating actions in a single api call. 4. Slow Pipeline Building: Pipeline construction can be sluggish compared to webhooks, potentially hindering productivity in complex workflows. The number of seconds waiting for a dropdown to load or a field to populate really hinders the builders' flow. 4. Cost Considerations: Webhook calls to outside servers incur fewer costs compared to pipelines, where every HTTP call uses an account step. 5. API Integrations:Webhooks have a limited, but useful API control via the legacy XML API. There is no such API control for pipelines. In essence, while Quickbase's decision to phase out webhooks may seem logical from a business perspective, it overlooks crucial functionalities vital for efficient workflow management. Enhancing pipeline capabilities to match the efficiency and performance of webhooks should be prioritized before ending webhook support. ------------------------------ Bradley ------------------------------ Re: Efficiently use pipelines for record change logsSo if I'm understanding the docs correctly, It is not possible to loop through the record fields? Basically, I could solve this problem in 2 steps if I could do a for each field in the record, but that doesn't appear possible. ------------------------------ Bradley ------------------------------ Efficiently use pipelines for record change logsHi, I was going through the quickbase university courses and came across this use case of using pipelines' Quickbase Records Updated feature to log changes to a table. Building Powerful Pipelines Using included Features I have a similar use case, but I have nearly 40 fields in the table and I only want the log a single changed field in the log table. In coding, I would do something like: for field in table_fields: if field.prev.value != field.current.value: create_logs_record(field.name, field.prev.value, field.current.value, ...) Is there a way I can efficiently do this in pipelines using jinja or some other method? Currently, I have a trigger on update and then a long series of `if changed, create record else ...` which is tedious to create and would be difficult to modify. ------------------------------ Bradley ------------------------------ Solved