Integrating Productboard for Feature Prioritization on Your Website

Why Productboard is the Standard for Prioritization

You spend weeks aligning the backlog, while Productboard gathers insights from feedback, interviews, and metrics — directly from your website. Without a centralized tool, prioritization becomes guesswork: managers subjectively evaluate feature importance, and developers waste time on unneeded functions. Productboard solves this with RICE and Value/Effort frameworks, which automatically assign priority based on data. We integrate a Customer Portal with voting, a REST API for note insights, and a webhook for roadmap synchronization. Result: transparent prioritization based on facts, not guesses. Our experience shows that prioritization time drops by up to 90%, and the investment in integration pays off through routine task automation. For example, an e-commerce site with 50,000 requests per month collected 1,200 insights in the first month, 30% of which became new features. Manual prioritization costs decreased 80%. Get a consultation — start with a site audit to assess potential.

How Productboard Helps Prioritize Features

Productboard uses RICE and Value/Effort frameworks to score each idea. Insights from the site (reviews, wishes) automatically enter the scoring. You see which features deliver the most value and build a roadmap based on facts.

What Integration with the Site Delivers

• Customer Portal: users vote on features and propose ideas — without extra forms.
• REST API: every site review becomes a Note in Productboard with tags (low satisfaction, performance issues).
• Webhook: the roadmap on the site updates in real-time when a feature status changes.

Problems We Solve

• Disparate feedback sources: support, chats, forms — all merge into a single window.
• Manual prioritization: hours spent on Excel tables replaced by automatic scoring.
• Stale roadmap: webhook syncs statuses without delays.

Case: a large e-commerce site with 50,000 requests per month integrated the Customer Portal and REST API. In one month, 1,200 insights were collected, 30% became new features. Prioritization time dropped from 8 hours to 30 minutes.

Setting Up the Webhook for Roadmap Sync

Register an endpoint in the Productboard dashboard. When a feature status changes, a POST request with JSON payload is sent. On the server, verify the HMAC-SHA256 signature and update the roadmap cache on the site. According to Productboard documentation, each Note is automatically indexed by tags.

How We Do It

1. Analytics: audit current feedback collection channels, configure the Productboard workspace.
2. Embed Customer Portal: iframe + SSO with JWT token.
3. Develop REST API: create Notes based on site feedback.
4. Configure Webhook: sync roadmap with the site.
5. Test End-to-End: feedback → Note → voting → roadmap.

Embedding the Customer Portal

Productboard provides a public portal for feature voting. Embed via iframe or custom domain:

<!-- Portal via iframe -->
<iframe
  src="https://portal.productboard.com/YOUR_TOKEN"
  frameborder="0"
  width="100%"
  height="800px" title="Embedded content from portal.productboard.com">
</iframe>

For SSO identification of users — a custom button with JWT:

// ProductboardTokenController
public function token(): JsonResponse
{
    $user = auth()->user();

    $payload = [
        'iss'   => config('services.productboard.api_key'),
        'iat'   => time(),
        'exp'   => time() + 3600,
        'email' => $user->email,
        'name'  => $user->name,
    ];

    $token = \Firebase\JWT\JWT::encode($payload, config('services.productboard.secret'), 'HS256');

    return response()->json([
        'token'      => $token,
        'portal_url' => 'https://portal.productboard.com/YOUR_TOKEN?jwt=' . $token,
    ]);
}

REST API: Creating a Note (Insight)

class ProductboardService
{
    private const BASE = 'https://api.productboard.com';

    public function createNote(string $content, string $userEmail, array $tags = []): array
    {
        return Http::withToken(config('services.productboard.token'))
            ->withHeaders(['X-Version' => '1'])
            ->post(self::BASE . '/notes', [
                'title'   => substr($content, 0, 100),
                'content' => $content,
                'user'    => ['email' => $userEmail],
                'tags'    => array_map(fn($t) => ['name' => $t], $tags),
                'source'  => ['origin' => 'website_feedback'],
            ])
            ->json();
    }
}

// Automatically create Note when feedback is received
public function handleFeedback(FeedbackSubmitted $event): void
{
    $tags = [];
    if ($event->score <= 3) $tags[] = 'low-satisfaction';
    if (str_contains(strtolower($event->comment), 'slow')) $tags[] = 'performance';

    app(ProductboardService::class)->createNote(
        $event->comment,
        $event->user->email,
        $tags
    );
}

Webhook for Roadmap Updates

Route::post('/webhooks/productboard', function (Request $request) {
    // Verify signature
    $computed = hash_hmac('sha256', $request->getContent(), config('services.productboard.webhook_secret'));
    if (!hash_equals($computed, $request->header('X-Productboard-Signature'))) abort(401);

    $data = $request->json();

    if ($data['data']['type'] === 'feature.status.updated') {
        $feature = $data['data']['feature'];
        // Update public roadmap on site
        Cache::forget('public_roadmap');
        Log::info("Feature updated: {$feature['name']} → {$feature['status']}");
    }

    return response('ok');
});

Productboard vs. Custom-Built Solution

Productboard deploys 10x faster and provides scoring out of the box. For startups with tight budgets, a custom solution may be justified, but as volume grows, Productboard pays off through reduced manual labor.

What's Included in the Integration

Final documentation includes architecture description, environment variables (API keys, secrets), and support contacts. We train your team to work with Productboard.

Timeline Estimates

Basic integration — from 2 to 5 working days without approval time. Pricing is individual after auditing your website.

Common Mistakes

• Missing webhook signature verification: an attacker can send a fake update. Always check HMAC.
• Incorrect Note content format: Productboard expects HTML. Convert Markdown to HTML before sending.
• Lack of tag filtering: spam feedback clogs the backlog. Implement moderation before sending to the API.

Contact us to evaluate your project. We'll help you choose the optimal integration approach. Request a site audit and receive a custom action plan. Experience: 5+ years and 30+ Productboard integration projects. We guarantee quality and transparency.

Website CRM Integration: Bitrix24, amoCRM, Salesforce, HubSpot

A sales manager manually copies leads from email into the CRM. Half of them never make it. Follow‑up calls are missed. This isn’t a people problem — it’s an architectural gap between the website and the company’s core system. We close that gap with a direct site‑to‑CRM connection: leads land in the pipeline within 30 seconds after form submission, duplication is blocked, and status changes flow both ways automatically. Request a free integration audit to identify the bottlenecks in your current flow.

Integration isn’t just a POST to an API endpoint. It’s a battle against timeouts, duplicate records, data loss, and desynchronised states. We handle three core problems at once: asynchronous delivery (so the user never waits for the CRM), deduplication by email (one address – one lead), and two‑way feedback (a status change in the CRM instantly appears on the site). Below is how we tackle each.

Bitrix24: REST API and Event Handlers

Bitrix24 dominates the Russian B2B space. Its REST API works via OAuth 2.0 or an incoming webhook (webhook is simpler but less secure for production). Main entities are lead, deal, contact, and company.

Creating a lead requires POST /rest/crm.lead.add with the correct field set. Attaching it to a funnel means passing SOURCE_ID. Adding a timeline comment uses crm.timeline.comment.add. Real‑time tracking is done through Event Handlers: register a hook with event.bind; Bitrix24 pushes a POST to your endpoint when any deal status changes.

The real complexity lies in custom fields. Every Bitrix24 installation has its own set, and their IDs must be fetched via crm.lead.fields. Mapping those fields between the site and the CRM can be done manually or automatically — we use an automatic detection mechanism that works even in non‑standard configurations (proven on 20+ projects). We guarantee correct matching, so no lead arrives without the right pipeline stage or source tag.

amoCRM: Clean REST with Predictable Endpoints

amoCRM (now Kommo for international markets) offers a cleaner API. OAuth 2.0 with refresh token, JSON API, and well‑structured endpoints. Pipelines are pipelines, deals are leads, contacts are contacts.

A common mistake: when creating a deal you must supply pipeline_id and status_id explicitly. Without them the deal lands in the default pipeline – often the wrong one. Tags for source classification go into _embedded.tags. Incoming webhooks are configured in the admin panel; they support add, update, delete, status, and note events. We always verify the webhook signature using the API key and make sure the endpoint responds with 200 OK in under 5 seconds – otherwise the CRM marks delivery as failed.

Salesforce and HubSpot: Enterprise‑Grade Integration

Salesforce is the enterprise standard. It offers REST API, SOQL for complex queries, and Apex for server‑side logic. Integration can be direct via Salesforce REST API or through middleware like Zapier or MuleSoft. For PHP projects we use phpforce/soap-client or the Force.com‑Toolkit. The main challenge is mapping hundreds of custom objects and fields; we solve it with Describe Global to collect metadata automatically – cutting setup time by three‑quarters compared to reading documentation manually (Salesforce Developer Guide).

HubSpot is popular among SaaS companies and international B2B. Its API v3 provides a REST interface with solid SDKs for PHP and Node.js (@hubspot/api-client). Contacts, Companies, Deals are standard objects. The Forms API lets you send data from any custom form directly to HubSpot without using the native widget. One pitfall: the access_token must include the right scopes; a misconfigured token returns 403 Forbidden with a vague message. We include error_logging that captures the error code – debugging takes minutes instead of hours.

Which CRM fits your business: Bitrix24, amoCRM, or HubSpot?

Why is asynchronous sending important?

Calling a CRM API synchronously from the form handler is a mistake. The API may respond in 2 seconds – or time out. The user sits waiting. The correct pattern: form submission → save to database → queue a job → return 200 to the user immediately. A background worker then pushes the lead to the CRM. If the CRM is down, the worker retries with exponential backoff. We use Redis + Bull on Node.js or Laravel Queue on PHP – this guarantees delivery even during temporary outages.

Deduplication – how we stop duplicate leads

The same contact may fill the form twice. Without deduplication the CRM ends up with two identical leads. Before creating a new lead we search by email: for Bitrix24 we call crm.duplicate.findByComm, for HubSpot we use contacts/search. If a match is found we attach a task or comment to the existing lead instead of creating a new one. In our projects this cuts duplicate entries by 95%.

Two‑way synchronization – what happens when a manager changes a deal status

If a manager updates a deal status in the CRM, the website needs to reflect that change – especially if the client has a personal account. We configure webhooks from the CRM to an endpoint on the site, then update the local database and notify the client. Critical details: verify the webhook signature and respond with 200 OK within 5 seconds, otherwise the CRM assumes delivery failed. We guarantee that the delay between a status change in the CRM and its appearance on the site never exceeds 3 seconds.

How do we conduct integration in 5 steps?

1. Audit of data flows – analyse current lead transfer, CRM field structure, and performance bottlenecks. Deliverable: “as‑is” and “to‑be” data flow diagrams.
2. Architecture design – choose the queue mechanism (Redis Bull or Laravel Queue), define the deduplication method, and prepare a field mapping specification.
3. Implementation on staging – write code on Laravel or Node.js, configure webhooks, and test with real data: lead creation, status updates, and error handling.
4. Load testing – simulate peak traffic (e.g. 500 requests per minute) and adjust retry policies and timeout settings.
5. Deployment and documentation – push to production, train the team on monitoring and retry cleanup, and deliver full endpoint documentation.

What is included in the work

• Audit report with current data flow diagrams and typical error patterns.
• Architecture design document specifying queue, deduplication, and mapping.
• Production‑ready integration code on Laravel or Node.js.
• Webhook configuration and signature verification.
• Team training on support tasks and retry cleanup.
• 30‑day warranty support for bug fixes and mapping adjustments.

Real‑world case: real‑estate agency with 400 leads per month

Timelines

The exact cost is calculated after an audit of your current processes and CRM data structure. Contact us for a project estimate – we will send a commercial proposal within one business day. With 5+ years of experience and more than 20 completed integrations, you get a solution that works from day one. Get an engineer consultation to see how your sales funnel can run without manual lead transfer.

Additional sources: Customer relationship management (Wikipedia) · REST API (Wikipedia)