> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hologrow.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Lark CLI

> Connect Hologrow Pulse to Lark so agents can create docs, send team updates, mention teammates, create tasks, and schedule recurring business alerts.

# Lark CLI

Use the Lark plugin when you want Hologrow Pulse to turn analysis into team actions inside Lark. After the plugin is connected, Pulse can create Lark Docs, send group messages, mention teammates, create and update tasks, and schedule recurring reports or alerts.

This guide is written for all Hologrow Pulse users. If your workspace uses Feishu, the same workflow may appear as Lark or Feishu depending on your region and account configuration.

## First-use checklist

Before asking Pulse to take action in Lark, confirm the basics:

* The data accounts you want to analyze are connected to Hologrow Pulse and have finished syncing.
* You know the target Lark group names, owner names, and timezone for any scheduled messages.
* If Pulse needs to collaborate inside a group, the Lark bot or integration user has already been invited to that group.
* You have tested one small data question before turning the result into a report, message, task, or automation.
* For important actions, ask Pulse to return a traceable link or identifier, such as a document link, task link, message reference, or schedule confirmation.

## Enable Lark

1. Open [agent.hologrow.ai](https://agent.hologrow.ai) and sign in.
2. In the left sidebar, select **Plugins**.
3. Find **Lark**.
4. Connect or enable the plugin.
5. If your workspace already has a preconfigured Lark connection, refresh it by turning the Lark plugin off and then on again.
6. Return to **Ask Pulse** and start a new request.

You normally do not need to paste API keys into prompts. If the plugin asks for setup information that you do not have, contact your Hologrow workspace admin before continuing.

## What you can ask Pulse to analyze

Pulse can work with the data sources connected in your Hologrow workspace. Availability depends on your organization's integrations and permissions.

| Data area                        | Common analysis                                                           | Example metrics                                                       |
| -------------------------------- | ------------------------------------------------------------------------- | --------------------------------------------------------------------- |
| Ecommerce and orders             | Product sales, order trends, country or site performance, SKU performance | Revenue, orders, units sold, refunds, average order value             |
| Paid media                       | Campaign and product-level advertising performance                        | Spend, impressions, clicks, conversions, conversion value, ROAS       |
| Web analytics                    | Traffic, landing pages, user acquisition, conversion paths                | Sessions, conversion rate, source or medium, landing page performance |
| Search performance               | Organic search demand and page discovery                                  | Clicks, impressions, queries, landing pages                           |
| Marketplaces and marketplace ads | Marketplace sales, product performance, ad attribution                    | Sales, orders, ad spend, attributed sales, ROAS, ACOS                 |

For best results, include the **time range**, **business object**, **metrics**, and **Lark action** in the same request.

## What Pulse can do in Lark

| Capability                  | What Pulse can do                                                                                                             |
| --------------------------- | ----------------------------------------------------------------------------------------------------------------------------- |
| Create Lark Docs            | Turn analysis into weekly business reviews, product retrospectives, ad performance reviews, or focused investigation reports. |
| Send group messages         | Send concise text summaries, tables, charts, or decision-ready updates to a target group.                                     |
| Mention teammates           | Mention specific owners in group messages when follow-up is needed.                                                           |
| Create and update tasks     | Create tasks, assign owners, set due dates, and update status or task details later.                                          |
| Schedule reports and alerts | Send recurring business summaries or threshold-based alerts at a specified time and timezone.                                 |

When asking Pulse to perform a Lark action, specify the target group, recipient, owner, due date, schedule time, and timezone. If a group name or person is ambiguous, ask Pulse to confirm before acting.

## Prompt templates

Replace the bracketed placeholders with your real dates, products, groups, owners, and thresholds.

### Create a report document

```text theme={null}
Create a Lark Doc for this week's business review. Use the connected ecommerce, advertising, search, and analytics data in Hologrow Pulse. Include core KPIs, channel performance, product performance, anomalies, and recommended actions for next week. Return the document link when complete.
```

```text theme={null}
Create a Lark Doc for [product name or product ID]. Analyze the last 30 days of sales, site traffic, paid media, search performance, and marketplace ads if available. Include budget recommendations, page optimization ideas, and the data sources used.
```

### Send a group message

```text theme={null}
Send yesterday's business summary to the Lark group [group name]. Include revenue, orders, ad spend, conversion value, ROAS, and any metric that changed by more than [threshold] compared with the previous day. Use a concise table and return the message confirmation.
```

```text theme={null}
Compare [product A] and [product B] for [time period]. Include units sold, revenue, ad spend, ROAS, and profit if available. Send the comparison to the Lark group [group name] with three conclusions about which product deserves more budget.
```

### Mention an owner when an issue appears

```text theme={null}
Check Google Ads and Meta Ads for the last 7 days. If any campaign has ROAS below [target value], send an alert to the Lark group [group name], mention [owner name], and include the campaign, spend, conversion value, ROAS, likely cause, and recommended action.
```

### Create or update tasks

```text theme={null}
Based on the ad review above, create Lark tasks for campaigns below [target ROAS]. Each task title should include the campaign name. Assign the owner to [name], set the due date to [date], and describe the optimization action and acceptance metric.
```

```text theme={null}
Update the Lark task [task link]. Change the owner to [name], change the due date to [date], and add this progress note: [progress note]. Return the updated task link and status.
```

### Schedule a recurring report or monitor

```text theme={null}
Every weekday at 09:30 ([timezone]), send the previous day's business summary to the Lark group [group name]. Include revenue, orders, ad spend, conversion value, ROAS, and anomalies that need attention.
```

```text theme={null}
Set up a monitor. If any campaign spent more than [amount] yesterday and ROAS was below [target value], send a Lark alert to [group name], mention [owner name], and include campaign name, spend, conversion value, ROAS, and recommended next step.
```

## Working safely

* Start with data, then act. Ask Pulse to explain the metric definitions, time range, and conclusion before creating a document, sending a message, or creating a task.
* Be specific about the destination. Provide the Lark group name for messages, the owner for tasks, and the timezone for scheduled reports.
* Ask for traceable results. For important operations, request the Lark Doc link, task link, message confirmation, or schedule details.
* Avoid duplicate actions. Add: "If an equivalent task or schedule already exists, return the existing link instead of creating a duplicate."
* When something fails, ask Pulse to identify the cause: missing data sync, disconnected account, insufficient Lark permissions, unclear group name, or unrecognized member name.

A good first request is simple: ask Pulse to create a short business summary for this week. Once the numbers and interpretation look correct, ask it to turn the result into a Lark Doc, send it to a team group, or convert follow-up actions into Lark tasks.