Postion
  • 社区动态
  • 定价标准
控制台
登录账号
Discord

基础入门

总览介绍为什么选择 Postion?核心概念快速入门指南搬家与迁移控制台指南新用户必看变现指南

创作者专区

站点管理写作与编辑Postion 编辑器品牌与定制化界面风格指南SEO 搜索引擎优化社交分发工作流模板市场商业化变现内容访问与定价订阅模式Stripe 支付接入其他收入来源提现与手续费数据分析高级数据分析邮件营销Stripe 收款设置指南自定义域名设置指南Webhook 集成指南导出数据CRM 粉丝管理CRM 标签指南CRM 客户分群

共建社区

社区准则早期采纳者红利如何参与最佳实践成功案例

技术开发支持

平台架构Postion 底层原理绑定自定义域名Webhooks 钩子公开 API 接口文档存储限制与配额

其他

常见问题解答疑难解答与排错
文档
Webhook Integration Guide

Webhook Integration Guide

Learn how to set up webhooks to integrate Postion with your existing tools. Automate workflows, sync data, and build custom integrations.

Webhooks allow your external applications to receive real-time notifications when events happen on your Postion site. Use them to automate workflows, sync data with your CRM, trigger emails, and more.

What Are Webhooks?

A webhook is an HTTP callback — when a specific event occurs on Postion (like a new subscriber or a purchase), we send a POST request to a URL you specify with data about that event.

Setting Up Webhooks

Step 1: Create a Webhook Endpoint

  1. Go to Dashboard → Webhooks
  2. Click "Add Webhook"
  3. Enter your endpoint URL (e.g., https://your-app.com/api/postion-webhook)
  4. Select the events you want to receive

Step 2: Choose Your Events

EventTriggerPayload
subscriber.createdNew subscriber signs upUser info, plan details
subscriber.updatedSubscriber changes planOld/new plan, user info
subscriber.deletedSubscriber cancelsUser info, reason
post.publishedNew post is publishedPost title, URL, author
purchase.completedOne-time purchase madeProduct, amount, buyer info
payment.receivedSubscription payment processedAmount, subscriber, plan
payment.failedPayment failsSubscriber info, failure reason

Step 3: Verify Your Endpoint

After creating the webhook, Postion sends a verification request to your URL. Your endpoint must respond with a 200 OK status to confirm it's ready.

Webhook Payload Format

All webhook payloads follow this structure:

{
  "event": "subscriber.created",
  "timestamp": "2025-07-15T10:30:00Z",
  "data": {
    "id": "sub_abc123",
    "email": "[email protected]",
    "name": "Jane Doe",
    "plan": "pro",
    "site_id": "site_xyz789"
  }
}

Security: Verifying Webhook Signatures

Every webhook request includes a signature header (X-Postion-Signature) that you should verify to ensure the request is genuinely from Postion.

import crypto from 'crypto';
 
function verifyWebhookSignature(payload, signature, secret) {
  const hash = crypto
    .createHmac('sha256', secret)
    .update(payload)
    .digest('hex');
  return hash === signature;
}

Always verify webhook signatures in production. Never trust unverified webhook data.

Common Integration Patterns

Sync with Your CRM

When a subscriber signs up, automatically create a contact in your CRM:

  1. Listen for subscriber.created events
  2. Extract the subscriber's email and name
  3. Create or update the contact in your CRM (HubSpot, Salesforce, etc.)

Send Welcome Emails via Custom Service

Trigger a personalized welcome email through your own email service:

  1. Listen for subscriber.created events
  2. Use the subscriber data to personalize the email
  3. Send via your preferred email provider (SendGrid, Mailgun, etc.)

Slack Notifications

Get notified in Slack when key events occur:

  1. Create a Slack Incoming Webhook URL
  2. Set up a middleware that receives Postion webhooks
  3. Forward formatted messages to your Slack channel

Analytics Tracking

Log events to your analytics platform:

  1. Listen for all relevant events
  2. Forward to Mixpanel, Amplitude, or your custom analytics
  3. Build dashboards to track subscriber lifecycle

Retry Policy

If your endpoint is unavailable, Postion retries with exponential backoff:

AttemptDelay
1st retry1 minute
2nd retry5 minutes
3rd retry30 minutes
4th retry2 hours
5th retry12 hours

After 5 failed attempts, the webhook is marked as failing, and you'll receive an email notification.

Troubleshooting

"Webhook not receiving events"

  • Verify your endpoint URL is publicly accessible (not localhost)
  • Check that your endpoint returns a 200 status code within 10 seconds
  • Ensure the correct events are selected in your webhook settings

"Invalid signature"

  • Make sure you're using the correct webhook secret from your dashboard
  • Verify you're computing the HMAC on the raw request body, not parsed JSON

"Events arriving out of order"

Webhooks may arrive out of order due to network conditions. Use the timestamp field to determine the true sequence of events.

For the full API reference, see our Public API Documentation. For technical details about the webhook system architecture, see Webhooks Architecture.

上一页自定义域...
下一页导出数据
Postion

写下专属于你的篇章

TwitterGitHubDiscordDiscordInstagram

探索

  • 控制台
  • 社区
  • 价格
  • 帮助文档
  • 常见问题

公司

  • 更新日志
  • 开发路线图
  • 联系我们
  • 加入我们
  • 官方博客

资源

  • 邀请机制
  • 快速入门
  • 什么是 Postion
  • 控制台指南
  • 公开 API 指南

支持与服务

  • 关于 Postion
  • 加入 Discord
  • BuouUI 项目
  • 站点地图
  • 博客 RSS

© Postion 2026 — BuouTech Inc.

版本说明无障碍隐私政策服务条款