Skip to main content

Set up Salesprompter

Start with your Salesprompter workspace and the CLI. Connect HubSpot or an outreach tool when you are ready to use that integration.

1. Sign in and choose a workspace

Create an account or sign in on salesprompter.ai. Select the workspace you intend to use for your leads and integrations.

2. Connect the CLI

You need an installed Salesprompter CLI and access to your workspace. Open Integrations in the app and use the CLI connection card to generate a short-lived token.

Follow the current CLI quickstart for the login command and account verification. Keep the token private. Verify the account and workspace before running a lead workflow.

3. Review your first lead workflow

The quickstart starts from a saved ICP. You need its program ID and access to the corresponding lead data. If either is missing, stop and finish workspace setup before running the commands.

Review the ICP and a small lead selection before moving on to enrichment or scoring. Check each command in the installed CLI help: data reads and enrichment can require provider access, and dry-run support depends on the command.

Stop before CRM updates, campaign sync or sending messages. For a command that supports a dry run, inspect that preview before using its apply option. A preview does not establish that data has been synced or a message sent.

Optional: connect HubSpot

HubSpot is needed for HubSpot-specific workflows, rather than for signing in or issuing a CLI token. Use the HubSpot card in Integrations and follow the connection instructions shown there.

Use an account with permission to authorize the requested CRM access. Review the requested permissions and selected workspace. Confirm the connection status before relying on it, and inspect any proposed contact, company or list changes before syncing.

Provider credentials and usage depend on the workflow you choose. Check its current configuration and costs before starting enrichment.

If setup stops

See Troubleshooting or contact support with the command name and redacted error. Never include tokens, API keys or customer records.