Insights, updates, and news from the team behind the embedded integration platform for B2B software companies.
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.
Integration development usually requires authentication against third-party applications, which can be a tough problem. Prismatic abstracts much of the work surrounding auth and credential management. Let's look at handling credentials in a custom component.
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.
Configuration variables allow you to deploy the same integration to multiple customers with different configurations. Let's walk through that process, from start to finish.
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.
A large portion of your integrations can be written using Prismatic's built-in components, but what happens when you need something specific to your software or industry? Today we'll walk through building a custom component.
This site uses cookies. By continuing to use this website, you agree to their use.