Configure, test, and activate Jasmine

Review the imported employee

Open the imported employee before enabling anything. Compare the profile with the import preview and resolve every warning. Confirm the employee belongs to the intended destination sub-account and has a clear internal owner.

• Review connector and plugin requirements without assuming a source connection exists.
• Review each generic playbook and remove any workflow the destination does not need.
• Review the disabled proactive schedule and choose the destination timezone, workdays, hours, interval, cooldown, and blackout dates.
• Keep channels unassigned until the Piece and destination memory pass testing.

Map connectors, apps, and Meta Ads

Lead360

Provides mapped CRM, conversation, opportunity, calendar, campaign, form, site, customer app, pipeline, and reporting operations.

E-Commerce

Provides mapped services, products, packages, memberships, checkout, purchases, customer activity, and governed membership, rewards, promotion, wallet, and referral context.

Automation Pieces

Provides mapped workflow and run context. Imported schedules and automations remain disabled until the destination administrator reviews resources, waits, sender identity, stop conditions, and ownership.

Sites Builder AI

Provides mapped websites, pages, funnels, forms, widgets, and campaign destinations for review and draft preparation.

Meta Ads

Provides governed advertising reads and approval-gated status, budget, paused-ad, and paused-retargeting operations after the destination account, required permissions, and exact resources are connected.

• Connect the destination-owned provider account and confirm the signed-in administrator.
• Grant only the permissions needed for the approved workflow. Reporting requires an eligible read permission.
• Select exact advertising, app, campaign, site, form, commerce, calendar, and workflow resources instead of granting broad access.
• Keep effects read-only or draft while testing. Any supported live Meta or automation effect remains approval-gated.
• Current Meta safety defaults limit budget changes to 20 percent, cap a new campaign daily budget at 100 in the configured currency context, create supported new ads and retargeting campaigns paused, and expire approvals after 30 minutes.

Add destination memory and learning

1. Open Memory Brain and review the pending collection guides created by the import.
2. Upload only current destination-owned knowledge into the appropriate folders.
3. Remove credentials, payment data, private notes, unnecessary personal data, and unsupported claims before review.
4. Approve the exact revisions and make them available through the normal snapshot workflow.
5. Create or update a Memory Set when the Piece should use a controlled subset.
6. Open the imported Piece, bind reviewed memory and the intended fresh Learning Collections, then save a new draft revision.

Validate and test in Arena

Validation checks the Piece contract. Arena testing checks how the draft behaves. Neither step proves that destination data, provider permissions, messages, prices, campaigns, or customer outcomes are correct.

• A read-only Meta Ads performance question with mapped advertising and CRM evidence; a connected Meta account must also have the required Piece tool grants.
• A fresh campaign draft followed by a plain-language copy edit that retains the draft rather than returning a general report.
• An email draft added to an existing SMS topic, retaining the campaign and exact approved audience while using a separate channel workflow and sender.
• Generated SMS and email nodes bound to the intended published customer Piece; missing bindings, changed audiences and missing senders must stop preparation.
• Separate owned-contact tests for website, app, SMS, email and payment flows. Verify provider delivery or failure, reply routing, waits, stop conditions and reporting; workflow approval is not delivery proof.
• A contact-benefit question that returns only the authorized customer membership, rewards, promotion, wallet, and referral context.
• An SMS launch with limited wallet headroom that confirms the funded audience, pauses the remainder, and resumes without duplicates.
• An email campaign request with a verified sender and consent-qualified audience, plus a missing-sender case that must stop safely.
• An explicit campaign-number request that resolves only that exact tenant campaign and does not fuzzy-match another title.
• A weekly seasonal campaign request with weak evidence that must return a no-campaign receipt instead of inventing urgency.
• A request to publish, send, recharge, change a budget, or activate an unmapped resource without approval, which Jasmine must refuse.

Review the answer, cited evidence, tool trace, blocked operations, handoff behavior, and resulting draft. Correct the Piece or destination mapping and repeat the test before publication.

Publish and activate deliberately

1. Publish the reviewed Piece revision and record its owner and approval evidence.
2. Assign the published deployment to the imported employee.
3. Choose one controlled internal channel and run a final destination test.
4. Enable approved playbooks and schedules one at a time and verify their delivery destination.
5. Enable customer-facing channels, automations, app changes, campaign changes, or provider writes only after their separate consent, content, payment, and operational reviews pass.
6. Monitor early runs, approvals, errors, opt-outs, escalations, and business outcomes before expanding access.

Troubleshooting and safe removal

The archive fails validation

Download the official file again and compare its SHA-256 checksum. Do not edit the archive or change its internal files.

A connector or plugin needs review

The destination may not have the required provider, permission, feature, or resource. Connect an eligible destination account or disable the unneeded capability.

The Piece has no useful business context

This is expected until destination memory is reviewed, made available, bound to a new Piece revision, and tested.

A playbook or schedule does not run

Imported playbooks are generic and schedule blueprints remain disabled. Map resources, review the prompt and effect, choose an internal delivery channel, then enable the workflow deliberately.

Remove the imported kit

Disable channels, schedules, automations, and bindings first. Use the supported kit-removal action while the import ledger can still prove which draft resources were created. Later changes, shared use, publication, or run history can block automatic removal and require manual ownership review.