Skip to main content

Code Component Usage

The Code Component#

The code component allows you to execute product or industry-specific code within an integration. This page outlines when and how to use a code component.

Why Use a Code Component?#

You will likely have integration logic that can't be solved using the standard components Prismatic provides. The portion of your integrations that are specific to your product or industry can be accomplished using code component steps, or custom components.

When to Use a Custom Component Instead#

Code component steps should be succinct and integration-specific. If the code you write could be reused in other integrations, or if the code is complex enough that it would benefit from unit tests, etc., you should use a custom component instead.

Adding a Code Component to an Integration#

Within the integration designer, add a step to your integration. Select the Code component, Code Block action.

You will be presented with a new code step in your integration, and you can click the "Edit" button to open the code editor:

Code Structure#

The code component provides a stub function by default. Let's examine the structure of the code:

module.exports = async ({ logger, configVars, credential }, stepResults) => {  return { data: null };};

The code component requires you to export an asynchronous function. The default code uses arrow function notation to create an async function to return.

Code Component Parameters#

This function is provided a few parameters. The first positional parameter, context, is comprised of logger, configVars, and credential properties that allow you to log, access config variables, and access credentials tied to this step respectively. The second positional parameter, stepResults, is an object that contains output from previous steps of the integration.


logger is an object that can be used for logging and debugging. logger has four functions: debug, info, warn, and error. For example:

module.exports = async ({ logger, configVars, credential }, stepResults) => {"Things are going great");  logger.warn("Now less great...");};

Config Variables#

configVars provides the Code Component with access to all config variables of an integration.

You can add config variables to your integration by clicking the Config Variables button in the integration designer.

If you create a config variable Acme ERP Endpoint, you could reference that config variable in a code component block with configVars["Config Variable Name"] syntax:

module.exports = async ({ logger, configVars, credential }, stepResults) => {  const fuelApiUrl = `${configVars["Acme ERP Endpoint"]}/fuel`;  // ...};

Notice that the step output on the left-hand side shows a proper endpoint with /extrapath appended to it:


The credential object that is passed in to a code component function contains any credentials that are bound to the function. See the credential documentation on the custom components page for full details on handling credentials - handling of credentials is the same in both custom components and the code component.

Any type of credentials can be associated with a code component.

In this example we have a code component step that accesses a username / private_key pair that is associated with it. It throws an error if no credentials is passed in, or if the credential is of a type other than private_key:

module.exports = async ({ logger, configVars, credential }, stepResults) => {  if (credential?.authorizationMethod !== "private_key") {    throw "This step requires a private key credential.";  }  const { username, private_key } = credential.fields;  console.log(    `This is terrible security practice, but here's your username: "${username}" and private key: "${private_key}"`  );  return { data: null };};

Referencing Previous Step Outputs#

Most steps of an integration return some sort of value. An HTTP - GET action, for example, might return a JSON payload from a REST API. An Amazon S3 - Get Object will return a binary file pulled from S3.

The code component can reference those outputs through the stepResults parameter. stepResults is an object that contains results from all previous steps.

For example, if you have an HTTP - GET step named Fetch Users List that pulls down an array of users from, you can generate an array of email addresses with this code:

module.exports = async (context, stepResults) => {  const userArray = stepResults.fetchUsersList.results;  const emailArray = =>;  return { data: emailArray };};
Step results are often objects

Many components return objects that have multiple keys. So, you can reference stepResults.myStepName.results.someKey. It's rare for a component to return serialized JSON, so there's rarely need to JSON.parse() results from a previous step.

Previous Steps Names as Variables#

Since names of steps can include spaces and non-JavaScript-friendly characters, alphanumeric characters of step names are converted to camelCase. So, a step named Download JSON from API would be converted to downloadJsonFromApi. You can test out step name -> referenceable name conversions here:

Referencing Integration Trigger Payload Data#

The integration trigger is simply another step that can have a unique name. Suppose an integration is triggered by a webhook, the trigger is named "My integration trigger", and the webhook is provided a payload of {"exampleKey": "exampleValue"}.

That exampleKey would be accessible using stepResults.myIntegrationTrigger like so:

module.exports = async ({ logger }, stepResults) => {  const exampleKey =;`Received '${exampleKey}'`);};

Using JavaScript destructuring, you can instead write this:

module.exports = async (  { logger },  {    myIntegrationTrigger: {      results: {        body: {          data: { exampleKey },        },      },    },  }) => {`Received '${exampleKey}'`);};

Notice the logged message in the testing pane

Code Component Return Values#

The code component can optionally return a value for use by a subsequent step. The return value can be an object, string, integer, etc., and will retain its type as the value is passed to the next step.

The return value is specified using the data key in the return object.

In this example we return a string with value "":

module.exports = async ({ logger, configVars, credential }, stepResults) => {  return { data: "" };};

The output can be used as input for the next step by referencing codeComponentStepName.results.

To see an example of returning more complex data structures, and a good example use case for a code component, see the Using a Code Component to Transform Data quickstart.

Returning Binary Data from a Code Component#

Sometimes you'll want your code component to return binary data (like a rendered image or PDF). To do that, return an object with a data property of type Buffer (a file buffer), and a contentType property of type String that contains the file's MIME type:

module.exports = async ({ logger, configVars, credential }, stepResults) => {  // ...  const fileBuffer = SomePdfLibrary.generatePdf();  return {    data: fileBuffer,    contentType: "application/pdf",  };};

To see an example use case for returning binary data from a code component, check out our Generate a PDF with a Code Component.

For More Information: Using a Code Component to Transform Data

Adding Dependencies to a Code Component#

If your code component depends on node modules from npm, dependencies will automatically be imported. For example, if your code component reads:

const fetch = require("node-fetch/lib/index.js");
module.exports = async ({ logger, configVars, credential }, stepResults) => {  const response = await fetch("");  const responseJson = await response.json();  return { data: responseJson };};

Then node-fetch will be imported as a dependency automatically from the UNPKG CDN.

You can also specify specific versions of npm packages for your code component:

const lodash = require("lodash@2.4.2");const fetch = require("node-fetch@2.6.1/lib/index.js");

You can require any file from npm using package[@version][/file] syntax. Note that with the lodash import above, no file was specified. If no file is specified, the main file defined in the npm package's package.json is imported. An explicit path was called out for the node-fetch import because the node-fetch package defaults to importing a browser version of the package, and we want a compiled server version instead.