Use StoreCRM from Codex or Claude Code<\/a>for step-by-step instructions covering Skill download, installation, environment variables, connection verification, example requests, and web approval.<\/p>\nOpen the web AI Assistant<\/h2> Click the AI Assistant icon in the lower-right corner of StoreCRM. Enter your question or what you want to create, and click [Send]. Do not enter personal data, confidential information, tokens, or passwords.<\/p>\n
Ask how to perform an operation<\/h2> Ask a question such as \u201cHow do I create a scenario?\u201d to see instructions and the StoreCRM help pages used as sources. Follow the source links to confirm the latest setup steps.<\/p>\nContinue a conversation from the last 30 days<\/h2> Click the clock icon to view conversations from the last 30 days associated with the current staff member. Select a conversation to continue with its context.<\/p>\nCreate a draft and review it on the web<\/h2>Describe specifically what you want to create and its purpose.<\/li> Review the generated draft summary and click [Review on web].<\/li> On the review screen, check the draft ID, operation, number of affected items, planned changes, and safety status.<\/li> Open the original StoreCRM screen, review the content and affected items again, and perform the required operation.<\/li><\/ol>\nAI the draft created by AI to the screen<\/h2>\n When AI Assistant creates a segment, campaign, scenario, or other resource, it automatically opens that resource's review and edit screen. The editing context for the AI-created resource is preserved after navigation.<\/p>\n
The campaign will be pre-filled to the creation screen. It is not automatically saved and automatically released.<\/li> scenarios are created with the necessary email, LINE, segments, and other dependencies, and then transferred to the top-level flow editor.<\/li> In the confirmation screen, check the target conditions, ex s, contents of transmission, order of execution, and unresolved references, and then make necessary corrections and save them.<\/li> If the screen move or creation fails, open the result of the conversation and check the state without duplicate creation.<\/li><\/ul>\n\n\nCreate an AI API credential for an external AI tool<\/h2>In StoreCRM, open [Settings] \u2192 [AI Settings].<\/li> Enter a name for the AI API credential. Use a name that identifies the device or tool, such as \u201cClaude\/Codex local.\u201d<\/li> Select a permission profile.<\/li> Set an expiration date if needed, and create the credential.<\/li><\/ol>\nChoosing a permission profile<\/h3>read_only\uff1a<\/strong>Allows only reading, explanations, validation, and retrieval of masked information.<\/li>draft_only (recommended):<\/strong>Allows creating and updating drafts in addition to reading. This profile is recommended for a first connection.<\/li>elevated\uff1a<\/strong>Allows proposals for high-risk operations. It does not allow direct sending, deletion, or similar actions to run automatically without confirmation.<\/li><\/ul>Select the minimum permissions required for the intended use and revoke credentials when they are no longer needed.<\/p>\n
Store the displayed connection information securely<\/h2> Immediately after creation, the raw token and the following environment variables are displayed once.<\/p>\n
STORECRM_AI_API_BASE_URL=...\nSTORECRM_AI_API_TOKEN=...\nSTORECRM_TENANT_ID=...<\/code><\/pre>\nBefore closing the display, save them in secure environment variables or secret storage used by the external AI tool.<\/li> Do not paste the token into source code, Git, Jira, chat, or help pages.<\/li> The raw token cannot be displayed again after you close the screen. Issue a new one if it is lost.<\/li><\/ul>\nConnect to a supported StoreCRM Skill\/API integration<\/h2> Follow the instructions for the supported StoreCRM Skill\/API integration and set the three environment variables above. These values are not entered in the [MCP server URL] field of a general-purpose MCP client. After connecting, first ask a read-only question to confirm that the tenant and permissions are correct.<\/p>\n
Rotate or revoke a credential<\/h2>Rotation:<\/strong>Issue a new token and update the external AI tool. The old token immediately becomes unusable.<\/li>Revoke or delete:<\/strong>Revoke or delete the credential if a device is lost, a leak is suspected, or the integration is no longer used.<\/li>Permission changes:<\/strong>Review permissions when the required operations change and continue using the minimum permissions needed.<\/li><\/ul>\nApproval and safety notes<\/h2> Operations from external AI tools are also subject to StoreCRM permissions, auditing, and draft protections. For sending, scheduling, activation, deletion, bulk updates, and similar operations, review the content and affected items on the original StoreCRM screen. Proposals requiring a web review session appear in the pending approvals list in AI Settings.<\/p>\nIf the assistant cannot answer or connect<\/h2>Start a new conversation if the web conversation has expired.<\/li> In the external AI tool, confirm that all three environment variables are set and contain no extra spaces or line breaks.<\/li> Check the credential's expiration date, revocation status, and permission profile.<\/li> The old token cannot connect after rotation. Update the external AI tool with the new value.<\/li> A connection configured as an MCP server will not work. Use a supported StoreCRM Skill\/API integration.<\/li> If an AI result differs from the actual StoreCRM settings, treat the StoreCRM screen as authoritative.<\/li><\/ul>","protected":false},"excerpt":{"rendered":"StoreCRM AI\u30a2\u30b7\u30b9\u30bf\u30f3\u30c8\u306f\u3001\u64cd\u4f5c\u65b9\u6cd5\u306e\u78ba\u8a8d\u3001\u30d8\u30eb\u30d7\u691c\u7d22\u3001\u30e1\u30fc\u30eb\u306a\u3069\u306e\u4e0b\u66f8\u304d\u4f5c\u6210\u3092\u652f\u63f4\u3057\u307e\u3059\u3002Web\u753b […]","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[16],"tags":[],"class_list":["post-5769","post","type-post","status-publish","format-standard","hentry","category-setting"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/storecrm.com\/help\/en\/wp-json\/wp\/v2\/posts\/5769","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/storecrm.com\/help\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/storecrm.com\/help\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/storecrm.com\/help\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/storecrm.com\/help\/en\/wp-json\/wp\/v2\/comments?post=5769"}],"version-history":[{"count":14,"href":"https:\/\/storecrm.com\/help\/en\/wp-json\/wp\/v2\/posts\/5769\/revisions"}],"predecessor-version":[{"id":7237,"href":"https:\/\/storecrm.com\/help\/en\/wp-json\/wp\/v2\/posts\/5769\/revisions\/7237"}],"wp:attachment":[{"href":"https:\/\/storecrm.com\/help\/en\/wp-json\/wp\/v2\/media?parent=5769"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/storecrm.com\/help\/en\/wp-json\/wp\/v2\/categories?post=5769"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/storecrm.com\/help\/en\/wp-json\/wp\/v2\/tags?post=5769"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
<\/figure>\n
<\/figure>\n
<\/figure>\n
<\/figure>\n\n\n\n\n
<\/figure>\n
<\/figure>\n
<\/figure>\n