What does running TikTok Shop invites and samples through Storika do?
Running TikTok Shop invites and samples through Storika's MCP connector lets an assistant send a Target Collaboration invite to named creators, or set up an Open Collaboration any creator can join, and work through the creator sample requests on the campaign brand's TikTok Shop.
What can a marketer ask to invite creators and handle sample requests?
A marketer can write: "Invite these creators to our sunscreen on TikTok Shop for my spring launch campaign, and show me the proposal before you send it." Later the marketer can write: "Show me the open creator sample requests, and approve the ones I pick."
Which Storika connector tools run TikTok Shop invites and samples, and in what order?
Storika's send_tiktok_shop_invite runs first, in two calls: a proposal, then the send after the marketer's yes. handle_sample_requests runs next with action list to show the creator sample requests, and then with action approve or reject, also in two calls.
What comes back from TikTok Shop invites and sample requests through Storika?
Storika's send_tiktok_shop_invite returns a proposal and a confirmation_ref. handle_sample_requests with action list shows each open creator request with its request_id, creator, product, approve-by day and sample rule, and the approved samples with their shipping stage, tracking number and ship-by day. Delivered comes only from the carrier's tracking.
Which TikTok Shop invite and sample step waits for the marketer's yes?
Sending a creator invite and approving or rejecting a sample request each wait for the marketer's yes in Storika. The first call changes nothing and returns a confirmation_ref, and the assistant calls again with the same arguments and the ref only after the yes. Approving commits the shop to ship a sample. Action list changes nothing.
Tools in the order they run
- send_tiktok_shop_invite, first call: takes campaign_id, product_id and type: target with creator_handles for named creators, or open for any creator. Nothing is sent. It returns a proposal and a confirmation_ref. Keep the handles times the products at 25 or fewer in one call.
- send_tiktok_shop_invite, second call: after the marketer's yes, the same arguments and the confirmation_ref send the invite once.
- handle_sample_requests with action list: takes campaign_id and shows the open requests and the approved samples. It changes nothing.
- handle_sample_requests with action approve or reject, first call: takes request_ids copied from the list, at most 25, and a reject_reason for a reject. It changes nothing. It returns the requests it will act on, names every id it will not act on, and returns a confirmation_ref.
- handle_sample_requests with action approve or reject, second call: after the marketer's immediate yes, the same arguments and the confirmation_ref change the shop. Approve and reject are for a Brand Manager.
The product_id comes from fetch with the target products:<brand>, which lists the active products of the brand's connected TikTok Shop. whoami says whether TikTok Shop is connected for each brand. Action cancel withdraws a sent target invite and action edit changes it, both with collaboration_id and the same two calls. Sample rules are edited in the Storika web app, not through the connector. The assistant fetches tools/list at each new session and follows the live schemas.