菜单
Create API-only OpenFunnel users on behalf of end-users. Use when an orchestrator or provider needs to provision OpenFunnel access programmatically for downstream users.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | provision-user |
| description | Create API-only OpenFunnel users on behalf of end-users. Use when an orchestrator or provider needs to provision OpenFunnel access programmatically for downstream users. |
| metadata | {"internal":true} |
For orchestrator providers who need to create OpenFunnel API users for their end-users programmatically.
The provider has an API key with provisioner access. When their end-user needs OpenFunnel access, this skill creates an API-only user mapped to the provider's domain. Credits are shared across the provider's domain, so the provider pays for all users they create.
The created user:
Email mapping:
guy@gooseworks.comalice@alice-startup.comalice@gooseworks.comThis ensures all provisioned users share the provider's credit pool.
Ask for the end-user's email address.
Extract the prefix from the end-user's email, then combine it with the provider's domain:
End-user email: alice@alice-startup.com
Provider email: guy@gooseworks.com
-> Internal email: alice@gooseworks.com
The provider's domain comes from the X-User-ID header.
POST /api/v1/admin/create-user
Headers:
X-API-Key: {provider API key}
X-User-ID: {provider email}
Body:
{ "email": "alice@gooseworks.com" }
User created:
Email: alice@gooseworks.com
API Key: {api_key from response}
This user can now access OpenFunnel via API using these credentials.
POST /api/v1/admin/create-user
Requires: the provider must have is_provisioner enabled on their account.
Request:
email (string): the constructed internal emailResponse:
idemailapi_keyConsume OpenFunnel live view alert webhooks by running a public HTTPS listener, verifying signed webhook requests, parsing saved-view insight payloads, and processing alerts safely. Use when the user wants a bot to receive or act on live view alerts via webhook.
Spot companies hiring to solve specific problems (daily). Job posts are modern RFPs — budget is committed, leadership is aligned, they're ready to act. Inferred pain-points from hiring events are leading indicators of buying behavior.
Spot companies and people with active pain-points (daily). Inferred from live company and people events using the TAQ model — Trait (who they are), Activity (what they're doing now), Qualifier (what they already have). Inferred pain-points are leading indicators of buying behavior.
Score accounts 0-100 on pain-point relevance with evidence and reasoning
Advanced account setup — ICP profiles, blocklists, and integrations (Salesforce, HubSpot, Slack)
Enrich a list of company domains into account IDs, relevant contacts, and work emails. Use when the user has multiple accounts or domains and wants OpenFunnel to return account-level contact lists with email coverage.