Connecting Trybe (UGC creators)

Trybe runs performance-based UGC for brands: creators join your creator program and submit content, you approve it and run it in your ads, and creators are paid on performance. Connect your Trybe brand to Cook and you can ask about your creators in chat, from the Cook API or from an app connected through the Cook MCP server.

Before you start

• You need your Trybe brand’s API key. It starts with tk_live_.
• Trybe turns on Brand API access for each brand. If your brand has no key, or Cook says “Brand API access isn’t on for this brand”, ask Trybe to enable it.
• You need permission to manage integrations in the Cook workspace.

Connect Trybe

1. Open Integrations and find Trybe.
2. Click Connect, paste the API key and click Connect again.

Cook checks the key with Trybe before it saves anything. The key is stored encrypted on your workspace’s connection and is used only for your workspace.

If Trybe refuses the key, the card says why:

What the card says	What to do
Trybe didn’t accept that key	Copy the key from Trybe again; it may have been revoked.
Brand API access isn’t on for this brand; ask Trybe to enable it.	Ask Trybe to turn on Brand API access for your brand, then connect again.

What you can ask

• “Who were my top 5 creators by orders last 7 days?”
• “Which creators drove the most GMV this month?”
• “How much did we spend on ads running Maya’s content in September, and what was the ROAS?”
• “Which creators are overdue on their sample?”
• “Show me the submissions waiting for review.”
• “Find submissions where the creator mentions the discount code.”

Orders are the conversions Trybe attributed to a creator. Purchases are what the ad platforms (Meta, TikTok, AppLovin) reported on the ads that ran the creator’s content. Cook uses orders unless you ask for ad purchases. Dates are whole UTC days, and “last 7 days” ends yesterday, since Trybe reports complete days only. A ranking covers at most 90 days.

Reviewing a submission

Ask Cook to approve, reject or ask for a revision of a pending submission, for example “approve submission submission_8f3e…” or “ask Maya to reshoot the intro in better light”. Cook files an approval card naming the creator, the submission and the comment the creator will read. Nothing changes in Trybe until you approve the card. When you do, Cook sends the review to Trybe and writes the result on the card.

A revision request needs a comment telling the creator what to change. Only a pending submission can be reviewed.

From the Cook API and MCP

The same reads and the review card are API operations: trybe.creators, trybe.creator, trybe.performance, trybe.submissions, trybe.submission and trybe.reviewSubmission, and the MCP tools trybe_creators, trybe_creator, trybe_performance, trybe_submissions, trybe_submission and trybe_review_submission. They need an account API key, since they run as the key’s person. See the API reference.

Disconnect

Open Integrations, click Trybe, then Disconnect. Cook deletes the saved key. To stop Cook’s access on Trybe’s side as well, revoke the key in Trybe.