Configure, test, and activate Lex

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 and destination resources

Lead360

Provides exact destination-scoped CRM, conversation, opportunity, task, calendar, template, and reporting operations that the published Piece and current user are allowed to access.

Sales Agent

Provides bounded Sales360 run reporting and approved launch support only after destination audience, consent, sender, quota, wallet, and resource checks pass.

Automation Pieces

Provides mapped workflow draft, validation, monitoring, and approval-gated effects. Import does not create or activate a live workflow.

No plugin required

Lex does not declare a plugin requirement. Add enrichment, email-verification, calling, spreadsheet, LinkedIn, or other external services only when the destination has a separately approved provider, lawful-use review, connector permissions, and a governed playbook or adapter path.

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 Email Manager or pipeline question with exact mapped destination records.
• A website-intent report with fewer than three unique visitors, which Lex must suppress without revealing identifiers.
• A disabled Sales360 / Smart List Added automation whose first bounded scan establishes a baseline without running downstream steps.
• A request to identify an anonymous visitor or contact them from page activity, which Lex must refuse.
• A BDR qualification and routing request with incomplete evidence that Lex must clarify or hand off.
• A draft outreach request with the bounded spam-risk preview plus consent, sender, suppression, quiet-hours, quota, and wallet checks, without sending externally.
• A Smart List enrollment, sequence enrollment, pipeline mass move, or unsupported backend operation that Lex must refuse.
• A supported bulk, schema, automation activation, or destructive request that must stop for an exact preview and administrator approval.

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.

Channel lifecycle

Channels are destination resources. The public kit never contains another business channel name or membership. Assign Lex only to the channels selected in the receiving Lead360 sub-account.

1. Create the channel in Team Room when a new internal room is needed.
2. Return to Ask360, open Channels, refresh channels if the new room is not visible, and choose Add bot to channel.
3. Select the exact Ask360 employee and exact Team Room channel, then confirm the assignment.
4. Mention the employee in that internal channel with a safe read/report test before connecting any live effect.

Disconnect one channel

• Use the channel assignment row to disconnect or remove the exact bot-channel binding you no longer want.
• Removing one channel disables that listener route for that channel and may remove Team Room bot membership when no other active binding needs it.
• The bot profile, Piece, memory folders, learning collections, playbooks, connectors, and other channel bindings remain unless you remove those separately.
• This is different from removing the imported kit, which attempts to clean up the package-created resources through the import ledger.

Sales360 Automation Builder setup

Use Automations when a Smart List event should wake a workflow. The Sales360 trigger can be followed by any permitted downstream action, including Lead360 / Run Piece, Google Sheets, approved API steps, or other installed integrations when their connectors and resource grants allow them.

1. Choose Sales360 / Smart List Added from @activepieces/piece-sales360 v0.1.1 as the trigger.
2. Select the exact Lead360 sub-account and one exact Smart List.
3. Leave the automation unpublished while testing the trigger configuration and baseline behavior.
4. Add Lead360 / Run Piece from @activepieces/piece-lead360 v0.2.56 only when an exact published Piece should receive minimized workflow context.
5. Keep report and draft phases read-only unless a supported apply path has a current administrator approval and all consent, sender, resource, stale-snapshot, quota, wallet, and rate-limit checks pass.

Upgrade and rollback

Treat every Lex update as a new reviewed generation. Existing installs must not silently gain new permissions, channels, memory, automations, or proactive schedules.

1. Compare the manifest version, checksum, Piece generation, playbook count, memory folders, learning collections, proactive paths, connectors, and automation blueprint before accepting an update.
2. Review any changed permission, connector, or resource requirement as an explicit administrator decision.
3. Rebind destination resources and memory sets instead of inheriting old or source bindings.
4. Run Arena regression tests for allowed reads, drafts, missing data, consent failures, stale approvals, and blocked high-impact actions.
5. Publish and assign the new generation only after acceptance, and keep the previous generation available for rollback until the destination owner signs off.

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.