Article
Use Triggers to Handle Third-Party Needs
prismatic.io
Quoted on this wiki
Every place a page here uses this source, in the order the words come in it.
Now, you can technically handle both Salesforce and Amazon SNS integrations through a series of integration steps, but it gets messy. “Every Salesforce integration would need to be called synchronously, and the last step would need to return an "Acknowledgment" (ACK) XML response back to Salesforce. Additionally, every Salesforce integration would need to start with a Deserialize XML step in order to parse the payload that came in.” Every integration with Amazon SNS would need to start with some "confirm subscription" logic, and SNS integrators would need to reinvent that wheel with each new SNS integration they create.
Custom webhook responses “Salesforce requires a very particular acknowledgement (ACK) response in XML format, and an HTTP 200 status code.” We can see that custom response here:
We recently introduced the ability for you to write your own triggers within your custom components. This gives you more control over the functionality of webhook triggers. “The third-party apps and services that you integrate with often have unique requirements when it comes to webhooks.” Using Prismatic's existing custom component SDK, developers now have the flexibility to customize how a webhook trigger responds to a request from a third party and to encapsulate third-party-specific logic within triggers. Bundling up these nitty-gritty details within the trigger abstracts many complexities from integration builders. This means your integration builders – who are often non-developers – don't need deep familiarity with webhooks and can now build integrations faster and with fewer steps.
We recently introduced the ability for you to write your own triggers within your custom components. This gives you more control over the functionality of webhook triggers. “Some third parties expect confirmation messages or particular responses when they send webhook requests, and others send proprietary data that needs to be parsed before it's useful in an integration.” Using Prismatic's existing custom component SDK, developers now have the flexibility to customize how a webhook trigger responds to a request from a third party and to encapsulate third-party-specific logic within triggers. Bundling up these nitty-gritty details within the trigger abstracts many complexities from integration builders. This means your integration builders – who are often non-developers – don't need deep familiarity with webhooks and can now build integrations faster and with fewer steps.
Why did we do this? The third-party apps and services that you integrate with often have unique requirements when it comes to webhooks. Some third parties expect confirmation messages or particular responses when they send webhook requests, and others send proprietary data that needs to be parsed before it's useful in an integration. “Using Prismatic's existing custom component SDK, developers now have the flexibility to customize how a webhook trigger responds to a request from a third party and to encapsulate third-party-specific logic within triggers.” In this post, we'll look at a couple examples of third-party services – Salesforce and Amazon SNS – and examine how we built component-specific triggers to help make integrations with Salesforce and Amazon SNS easier to build. We're using these two common services as examples – the industry-specific third-party services you integrate with will have different idiosyncrasies that you can account for by writing your own triggers.
Why did we do this? The third-party apps and services that you integrate with often have unique requirements when it comes to webhooks. Some third parties expect confirmation messages or particular responses when they send webhook requests, and others send proprietary data that needs to be parsed before it's useful in an integration. “Bundling up these nitty-gritty details within the trigger abstracts many complexities from integration builders.” In this post, we'll look at a couple examples of third-party services – Salesforce and Amazon SNS – and examine how we built component-specific triggers to help make integrations with Salesforce and Amazon SNS easier to build. We're using these two common services as examples – the industry-specific third-party services you integrate with will have different idiosyncrasies that you can account for by writing your own triggers.
Why did we do this? The third-party apps and services that you integrate with often have unique requirements when it comes to webhooks. Some third parties expect confirmation messages or particular responses when they send webhook requests, and others send proprietary data that needs to be parsed before it's useful in an integration. “This means your integration builders – who are often non-developers – don't need deep familiarity with webhooks and can now build integrations faster and with fewer steps.” In this post, we'll look at a couple examples of third-party services – Salesforce and Amazon SNS – and examine how we built component-specific triggers to help make integrations with Salesforce and Amazon SNS easier to build. We're using these two common services as examples – the industry-specific third-party services you integrate with will have different idiosyncrasies that you can account for by writing your own triggers.
Amazon SNS is fine with any response, but when you first set up SNS to point to a webhook endpoint it sends a "confirm subscription" payload to that endpoint. It expects the owner of the webhook to make a request to a URL that SNS specifies in its payload to confirm that it's listening properly. “Now, you can technically handle both Salesforce and Amazon SNS integrations through a series of integration steps, but it gets messy.” Every Salesforce integration would need to be called synchronously, and the last step would need to return an "Acknowledgment" (ACK) XML response back to Salesforce. Additionally, every Salesforce integration would need to start with a Deserialize XML step in order to parse the payload that came in.
Preprocess data that comes in “If there are tasks that need to be taken care of whenever you integrate with a particular third party, you can wrap those tasks nicely into a trigger.” Salesforce, for example, has outbound messages (their form of webhook) that contain XML payloads. If every Salesforce webhook payload contains XML, we should probably deserialize the XML in the trigger. Otherwise, we'd have to start every integration with Salesforce with a Deserialize XML step.
Quotes are verbatim and belong to their publishers. Where a quote has been translated, the original wording is kept below it.