Connect

Outcome: After this step, SellerShorts can POST inputs to your webhook, and your automation can authenticate and send results back via callback.

The Connect step is where you link your AI automation to SellerShorts. You'll configure the webhook URL where we send buyer inputs and set up authentication to ensure secure communication.

Overview

When buyers run your AI Short, we need to send their inputs to your automation and receive the results back. This step establishes the technical connection between SellerShorts and your AI automation platform.

Required configuration

Webhook URL

• Protocol – Must use HTTPS (HTTP is not allowed for security)
• Method – POST requests only
• Format – Must accept application/json content type
• Examples:
  • https://hook.make.com/abc123xyz
  • https://api.n8n.cloud/webhook/uuid
  • https://your-domain.com/api/webhook

Authentication headers

You must add at least one authentication header to verify requests come from SellerShorts:

Recommended patterns:

• Authorization: Bearer YOUR_TOKEN – Best for OAuth/JWT/token services
• x-api-key: YOUR_KEY – Best for static API keys/gateways
• x-auth-token: YOUR_TOKEN – Alternative token header

Callback configuration

Callback URL

For async processing, you'll send results back to your Callback URL shown in-app.

Callback Secret

• Header name: x-callback-secret
• Purpose: Verifies callback requests come from your automation
• Controls: Generate new secret, show/hide value, copy to clipboard
• Security: Keep this secret secure – treat it like a password

Optional features

Polling endpoint

If you can't use callbacks, you can provide a polling URL:

• URL pattern: https://api.yourtool.com/status/{order_id}
• Placeholder: Use {order_id} – we'll replace with the actual UUID
• When used: If callback delivery fails, we'll poll this endpoint

Payload preview

• Sample JSON – See exactly what we'll send to your webhook
• Copy cURL – Get a complete cURL command for testing
• Real data – Preview includes your actual input configuration

Connection testing

Required connection test

Before proceeding, you must test your connection:

1. Enable your webhook – Make sure it's ready to receive requests
2. Disable callbacks temporarily – Turn off any modules that send data back during testing
3. Click "Test Connection" – We'll send a sample POST request
4. Check the results – Green checkmark means success

Common test failures and fixes

Authentication errors

• 401/403 errors – Add correct Authorization: Bearer or x-api-key header
• Wrong token format – Check if your platform expects a specific header format
• Expired tokens – Refresh OAuth tokens or generate new API keys

URL and routing errors

• 404 errors – Double-check webhook URL path and spelling
• 405 errors – Ensure endpoint accepts POST requests with JSON
• 3xx redirects – Use the final HTTPS URL, not one that redirects

Content type errors

• 415/422 errors – Configure endpoint to accept application/json
• Parsing errors – Make sure your webhook can parse JSON payloads

Network errors

• Timeouts – Check if your automation platform is accessible
• DNS errors – Verify domain name resolves correctly
• SSL errors – Ensure valid HTTPS certificate

Platform-specific guidance

Make.com

• URL format: https://hook.make.com/your-hook-id
• Headers: Add custom header in HTTP module settings
• Testing: Enable webhook, disable callback modules during test

n8n

• URL format: https://your-instance.n8n.cloud/webhook/your-path
• Headers: Configure in Webhook node authentication tab
• Testing: Set webhook to "Test URL" mode initially

Relevance AI

• URL format: Custom endpoint in your workspace
• Headers: Use Authorization: Bearer workspace-token
• Testing: Test endpoint separately before connecting

Botpress

• URL format: https://webhook.botpress.cloud/your-bot-id
• Headers: Configure in bot webhook integration settings
• Testing: Enable webhook integration, check bot logs

Security best practices

• Use strong tokens – Generate secure, unique authentication tokens
• Rotate regularly – Change tokens periodically for better security
• Monitor access – Watch for unusual webhook activity
• Validate payloads – Check that incoming requests match expected format
• Log requests – Keep records for debugging and security monitoring

Testing workflow

1. Set up webhook – Configure your automation to receive JSON POST requests
2. Add authentication – Ensure your webhook validates the auth headers
3. Test locally first – Use tools like ngrok or Postman to verify
4. Configure in SellerShorts – Enter URL, headers, and callback settings
5. Run connection test – Verify everything works together
6. Fix any issues – Use error messages to troubleshoot problems

What's next?

After successfully connecting your automation, you'll move to the Test step where you can run a complete test order to verify your AI Short works end-to-end.

[SCREENSHOT HERE: Connection test interface with success state]