Insights, updates, and news from the team behind the embedded integration platform for B2B software companies.
Creating a logging framework is a Twelve-Factor App best-practice. Here's how logging works with integrations using Prismatic's built-in logging framework, and how you can use it to trigger alerts for your team.
It's important to keep tabs on your customers' integrations and respond quickly if something goes wrong. Let's explore using Prismatic to send integration alerts via email, text, or through your existing systems like PagerDuty or Slack.
It's important to be able to write an integration once, and deploy it to multiple customers who have unique credentials. Let's look at storing customer credentials in Prismatic, and how to tie credentials to instances of integrations.
Authentication and credential management is inherently difficult. Learn how to handle credentials in custom components with our walkthrough tutorial.
Do you want to detect a breaking change of your custom components in CI/CD, or detect it in production? Of course that's a rhetorical question! Let's look at how to add unit testing to our build pipelines.
Learn the configuration process from start to finish. See how to use configuration variables to deploy the same integration to multiple customers with different configurations.
Did you know that you can manage your customers, integrations, instances, and more from the command line? In this post we'll use Prismatic's CLI tool, Prism, to create an integration and deploy it to a customer.
Dev teams are increasingly incorporating SaaS tools as components of their applications rather than developing every last bit of functionality from scratch.
Learn how you can quickly incorporate short, product- or industry-specific code into your integrations using the Prismatic code component.
