> Portal Navigation:
> 
> - Append `.md` to any URL under `https://dev.wix.com/docs/` to get its markdown version.
> - Pages are either content pages (article or reference text) or menu pages (a list of links to child pages).
> - To get a menu page, truncate any URL to a parent path and append `.md` (e.g. `https://dev.wix.com/docs/sdk.md`, `https://dev.wix.com/docs/sdk/core-modules.md`).
> - Top-level index of all portals: https://dev.wix.com/docs/llms.txt
> - Full concatenated docs: https://dev.wix.com/docs/llms-full.txt

## Resource: Sample Flows

## Article: Templates Sample Flows

## Article Link: https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/activity-log/template-v1/sample-flows.md

## Article Content:

# Templates API: Sample Flows

This article presents a possible use case and corresponding sample flow that you can support. It provides a useful starting point as you plan your implementation.

## Enrich a contact's activity feed with template details

When displaying a contact's activity timeline you may want to show the template's icon and
description alongside each activity. This flow shows how to look up template details for a list
of activities.

To enrich a contact's activity feed with template details:

1. Call [List Activities](https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/activity-log/activity-v1/list-activities.md) with the contact's `contactId` to retrieve the
   contact's activities.
2. Call [List Templates](https://dev.wix.com/docs/api-reference/crm/members-contacts/contacts/activity-log/template-v1/list-templates.md), iterating through all pages until no `next` cursor is
   returned in `metadata.cursors`. Build a lookup map of `id → template` from the results.
3. For each activity with a `templateId`, look up the matching template. Use `template.icon.url`
   to display an icon next to the activity and `template.activityDescription` for a short
   human-readable summary of what the activity represents.