Skip to main content

Knowledge Sources, Webhooks & Media Updates

This release introduces major improvements for teams building with Periskope, including live knowledge sources through MCP, richer webhook debugging tools, and a more reliable media delivery infrastructure across APIs and integrations.

✅ Connect your Knowledge Base with External Sources (MCP)

Instead of uploading and maintaining documents manually, you can now connect the AI Agent directly to a live knowledge source, such as Notion, Confluence, or your own product documentation, via MCP (Model Context Protocol).

The AI Agent can read from the connected source in real time, so there's nothing to re-upload or keep in sync.

Access it from AI → Knowledge Base → External Sources.

Click Connect Source and provide:

  • Name: A label to identify the source (for example, Company Docs)

  • Server URL: The MCP server endpoint (for example, https://docs.company.com/mcp)

  • Authentication: How Periskope authenticates with the server

Supported authentication methods:

  • None: Public documentation with no credentials required

  • Bearer: A bearer token sent as Authorization: Bearer <token>

  • Header: A custom header key/value pair (for example, X-Api-Key)

  • OAuth: Sign in through the provider and authorize access

✅ Webhook statistics, resend & delivery attempts

Webhook Logs now include statistics across all subscribed webhooks, including:

  • Activity, Average response time, Success rate, Retry rate

You can also:

  • Resend an event directly to the webhook endpoint using the new Resend button.

  • View every delivery attempt and retry in the Attempts & Responses panel inside the webhook inspector.

✅ Updated media delivery URLs

We've updated how media files are served across Periskope integrations and APIs.

Going forward, image URLs returned in API responses, webhooks, and integrations (including HubSpot, Google Sheets, Zoho Desk, and others) will use the https://api.periskope.app/app/media/* domain instead of https://storage.googleapis.com/*.

This provides a more consistent and reliable media delivery experience while laying the foundation for upcoming improvements to our media infrastructure.

No action is required for most users. However, if your workflows explicitly depend on the previous Google Cloud Storage URLs, please update them accordingly.

This is a small step in our broader media migration initiative aimed at improving performance, flexibility, and long-term reliability.

That's it for this release. Explore the new updates and let us know if you have any feedback. ✨