5 docs tagged with "Sub Components"

Abandoned carts are missed opportunities to convert interested shoppers into loyal customers. Sending an abandoned cart email notification is a way to gently nudge them to come back, whether it is with a personalized message or a special discount. Automating abandoned cart emails requires orchestrating data from your eCommerce system with an email service provider to identify, segment, tailor, and send your messages. Buillding an abandoned cart notification process can be challenging as teams have to manage syncing data across systems, handling high-volume requests, and ensuring flexibility in the style and messaging of your emails.

This straightforward recipe demonstrates a core Conscia behaviour - interacting with an API endpoint, and executing a task per-record against the results. In this example, we will be reading and writing from an Airtable, an innovative spreadsheet-type collaboration tool. We will read from a Table and for each unserved row, perform a unit of work on that input in Conscia, then write the output to another Table.

Conscia Recipes are designed to be intentionally open-ended, providing a robust starting point for building custom workflows. However, just as Components can come togther to form more complex Flows or populate bespoke experiences, Recipes can be built using others as a foundation.

Logging is a critical piece in any digital system. It enhances visibility, facilitates troubleshooting, and supports system reliability. With this recipe, you can implement a solution with Conscia that sends log entries to Datadog.

With an example that retrieves a product category tree from Salesforce B2B Core APIs, this document describes how you can use Sub Components to implement recursion with Conscia to access hierarchical data structures in third-party products. Many third-party APIs provide access to hierarchical data one level at a time. Calling code must retrieve the child nodes for a root node and then retrieve the child nodes of those child nodes and then retrieve the child nodes of those grandchild nodes, continuing to some level of depth or until there are no more descendants. Where an API does not offer a direct way to retrieve an entire hierarchy, solutions can use recursion to access the entire node tree. This scenario is common in generating website navigation elements or similar hierarchical structures when the API provider does not offer a comprehensive hierarchy endpoint.