Source Functions

1. From your workspace, go to Connections > Catalog and click the Functions tab.
2. Click New Function.
3. Select Source as the function type and click Build.

After you click Build, a code editor appears. Use the editor to write the code for your function, configure settings, and test the function's behavior.

Expand image

Source functions must have an onRequest() function defined. This function is executed by Segment for each HTTPS request sent to this function's webhook.

1
async function onRequest(request, settings) {
2
  // Process incoming data
3
}

The onRequest() function receives two arguments:

• request - an object describing the incoming HTTPS request.
• settings - set of settings for this function.

To parse the JSON body of the request, use the request.json() method, as in the following example:

1
async function onRequest(request) {
2
  const body = request.json()
3
  console.log('Hello', body.name)
4
}

Use the request.headers object to get values of request headers. Since it's an instance of Headers, the API is the same in both the browser and in Node.js.

1
async function onRequest(request) {
2
  const contentType = request.headers.get('Content-Type')
3
  const authorization = request.headers.get('Authorization')
4
}

To access the URL details, refer to request.url object, which is an instance of URL.

1
async function onRequest(request) {
2
  // Access a query parameter (e.g. `?name=Jane`)
3
  const name = request.url.searchParams.get('name')
4
}

You can send messages to the Segment API using the Segment object:

1
async function onRequest(request) {
2
  Segment.identify({
3
    userId: 'user_id',
4
    traits: {
5
      name: 'Jane Hopper'
6
    }
7
  })
8

9
  Segment.track({
10
    event: 'Page Viewed',
11
    userId: 'user_id',
12
    properties: {
13
      page_name: 'Summer Collection 2020'
14
    }
15
  })
16

17
  Segment.group({
18
    groupId: 'group_id',
19
    traits: {
20
      name: 'Clearbit'
21
    }
22
  })
23

24
  Segment.set({
25
    collection: 'products',
26
    id: 'product_id',
27
    properties: {
28
      name: 'Nike Air Max'
29
    }
30
  })
31
}

Use Identify calls to connect users with their actions, and to record traits about them.

1
Segment.identify({
2
  userId: 'user_id',
3
  traits: {
4
    name: 'Jane Hopper'
5
  }
6
})

The Segment.identify() method accepts an object with the following fields:

• userId - Unique identifier for the user in your database.
• anonymousId - A pseudo-unique substitute for a User ID, for cases when you don't have an absolutely unique identifier.
• traits - Object with data about or related to the user, like name or email.
• context - Object with extra information that provides useful context, like locale or country.

Track calls record actions that users perform, along with any properties that describe the action.

1
Segment.track({
2
  event: 'Page Viewed',
3
  userId: 'user_id',
4
  properties: {
5
    page_name: 'Summer Collection 2020'
6
  }
7
})

The Segment.track() method accepts an object with the following fields:

• userId - Unique identifier for the user in your database.
• anonymousId - A pseudo-unique substitute for a User ID, for cases when you don't have an absolutely unique identifier.
• properties - Object with data that is relevant to the action, like product_name or price.
• context - Object with extra information that provides useful context, like locale or country.

Group calls associate users with a group, like a company, organization, account, project, or team.

1
Segment.group({
2
  groupId: 'group_id',
3
  traits: {
4
    name: 'Clearbit'
5
  }
6
})

The Segment.group() method accepts an object with the following fields:

• groupId - Unique identifier for the group in your database.
• traits - Object with data that is relevant to the group, like group_name or team_name.
• context - Object with extra information that provides useful context, like locale or country.

Page calls record whenever a user sees a page of your website, along with any other properties about the page.

1
Segment.page({
2
  name: 'Shoe Catalog',
3
  properties: {
4
    url: 'https://myshoeshop.com/catalog'
5
  }
6
})

The Segment.page() method accepts an object with the following fields:

• userId - Unique identifier for the user in your database.
• anonymousId - A pseudo-unique substitute for a User ID, for cases when you don't have an absolutely unique identifier.
• name - Name of the page.
• properties - Object with information about the page, like page_name or page_url.
• context - Object with extra information that provides useful context, like locale or country.

Screen calls record when a user sees a screen, the mobile equivalent of Page, in your mobile app.

1
Segment.screen({
2
  name: 'Shoe Feed',
3
  properties: {
4
    feed_items: 5
5
  }
6
})

The Segment.screen() method accepts an object with the following fields:

• userId - Unique identifier for the user in your database.
• anonymousId - A pseudo-unique substitute for a User ID, for cases when you don't have an absolutely unique identifier.
• name - Name of the screen.
• properties - Object with data about the screen, like screen_name.
• context - Object with extra information that provides useful context, like locale or country.

The Alias call merges two user identities, effectively connecting two sets of user data as one.

1
Segment.alias({
2
  previousId: 'old-email@example.com',
3
  userId: 'new-email@example.com'
4
})

The Segment.alias() method accepts an object with the following fields:

• previousId - Previous unique identifier for the user.
• userId - Unique identifier for the user in your database.
• anonymousId - A pseudo-unique substitute for a User ID, for cases when you don't have an absolutely unique identifier.

The Set call uses the object API to save object data to your Redshift, BigQuery, Snowflake, or other data warehouses supported by Segment.

1
Segment.set({
2
  collection: 'products',
3
  id: 'product_id',
4
  properties: {
5
    name: 'Nike Air Max 90',
6
    size: 11
7
  }
8
})

The Segment.set() method accepts an object with the following fields:

• collection - A collection name, which must be lowercase.
• id - An object's unique identifier.
• properties - An object with free-form data.

Declare settings variables in the function handler, rather than globally in your function. This prevents you from leaking the settings values across other function instances.

The handler for source functions is onRequest().

Segment Functions run on the Node.js LTS runtime (currently v20). This keeps the runtime current with industry standards and security updates.

Based on the AWS Lambda and Node.js support schedule, production applications should only use Node.js releases that are in Active LTS or Maintenance LTS.

When Segment upgrades the Functions runtime to a new LTS version, existing functions automatically use the new runtime after their next deployment. Segment recommends checking your function after deployment to ensure everything works as expected, since dependency or syntax changes between Node.js versions might affect your function's behavior.

Functions don't support importing dependencies, but you can contact Segment Support to request that one be added.

The following dependencies are installed in the function environment by default:

• atob v2.1.2 exposed as atob

• aws-sdk v2.488.0 exposed as AWS

• btoa v1.2.1 exposed as btoa

• fetch-retry exposed as fetchretrylib.fetchretry

• form-data v2.4.0 exposed as FormData

• @google-cloud/automl v2.2.0 exposed as google.cloud.automl

• @google-cloud/bigquery v5.3.0 exposed as google.cloud.bigquery

• @google-cloud/datastore v6.2.0 exposed as google.cloud.datastore

• @google-cloud/firestore v4.4.0 exposed as google.cloud.firestore

• @google-cloud/functions v1.1.0 exposed as google.cloud.functions

• @google-cloud/pubsub v2.6.0 exposed as google.cloud.pubsub

• @google-cloud/storage v5.3.0 exposed as google.cloud.storage

• @google-cloud/tasks v2.6.0 exposed as google.cloud.tasks

• hubspot-api-nodejs exposed as hubspotlib.hubspot

• jsforce v1.11.0 exposed as jsforce

• jsonwebtoken v8.5.1 exposed as jsonwebtoken

• libphonenumber-js exposed as libphonenumberjslib.libphonenumberjs

• lodash v4.17.19 exposed as _

• mailchimp marketing exposed as mailchimplib.mailchimp

• mailjet exposed as const mailJet = nodemailjet.nodemailjet;

• moment-timezone v0.5.31 exposed as moment

• node-fetch v2.6.0 exposed as fetch

• oauth v0.9.15 exposed as OAuth

• @sendgrid/client v7.4.7 exposed as sendgrid.client

• @sendgrid/mail v7.4.7 exposed as sendgrid.mail

• skyflow exposed as skyflowlib.skyflow

• stripe v8.115.0 exposed as stripe

• twilio v3.68.0 exposed as twilio

• uuidv5 v1.0.0 exposed as uuidv5.uuidv5

• winston v2.4.6 exposed as const winston = winstonlib.winston

• xml v1.0.1 exposed as xml

• xml2js v0.4.23 exposed as xml2js

• zlib v1.0.5 exposed as zlib.zlib

  
  uuidv5 is exposed as an object. Use uuidv5.uuidv5 to access its functions. For example:

  Copy code block

  1
  async function onRequest(request, settings) {
  2
       uuidv5 = uuidv5.uuidv5;
  3
       console.log(typeof uuidv5);
  4
  
  5
        //Generate a UUID in the default URL namespace
  6
        var urlUUID = uuidv5('url', 'http://google/com/page');
  7
        console.log(urlUUID);
  8
  
  9
        //Default DNS namespace
  10
        var dnsUUID = uuidv5('dns', 'google.com');
  11
        console.log(dnsUUID);
  12
    }

  zlib's asynchronous methods inflate and deflate must be used with async or await. For example:

  Copy code block

  1
  zlib = zlib.zlib;  // Required to access zlib objects and associated functions
  2
  async function onRequest(request, settings) {
  3
  const body = request.json();
  4
  
  5
  const input = 'something';
  6
  
  7
  // Calling inflateSync method
  8
  var deflated = zlib.deflateSync(input);
  9
  
  10
  console.log(deflated.toString('base64'));
  11
  
  12
  // Calling inflateSync method
  13
  var inflated = zlib.inflateSync(new Buffer.from(deflated)).toString();
  14
  
  15
  console.log(inflated);
  16
  
  17
  console.log('Done');
  18
  }

The following Node.js modules are available:

• crypto Node.js module exposed as crypto.
• https Node.js module exposed as https.

Other built-in Node.js modules aren't available.

For more information on using the aws-sdk module, see how to set up functions for calling AWS APIs.

Basic cache storage is available through the cache object, which has the following methods defined:

• cache.load(key: string, ttl: number, fn: async () => any): Promise<any>
  • Obtains a cached value for the provided key, invoking the callback if the value is missing or has expired. The ttl is the maximum duration in milliseconds the value can be cached. If omitted or set to -1, the value will have no expiry.
• cache.delete(key: string): void
  • Immediately remove the value associated with the key.

Some important notes about the cache:

• When testing functions in the code editor, the cache will be empty because each test temporarily deploys a new instance of the function.
• Values in the cache are not shared between concurrently-running function instances; they are process-local which means that high-volume functions will have many separate caches.
• Values may be expunged at any time, even before the configured TTL is reached. This can happen due to memory pressure or normal scaling activity. Minimizing the size of cached values can improve your hit/miss ratio.
• Functions that receive a low volume of traffic may be temporarily suspended, during which their caches will be emptied. In general, caches are best used for high-volume functions and with long TTLs. The following example gets a JSON value through the cache, only invoking the callback as needed:

1
const ttl = 5 * 60 * 1000 // 5 minutes
2
const val = await cache.load("mycachekey", ttl, async () => {
3
    const res = await fetch("http://echo.jsontest.com/key/value/one/two")
4
    const data = await res.json()
5
    return data
6
})

Settings allow you to pass configurable variables to your function, which is the best way to pass sensitive information such as security tokens. For example, you might use settings as placeholders to use information such as an API endpoint and API key. This way, you can use the same code with different settings for different purposes. When you deploy a function in your workspace, you are prompted to fill out these settings to configure the function.

First, add a setting in Settings tab in the code editor:

Expand image

Click Add Setting to add your new setting.

Expand image

You can configure the details about this setting, which change how it's displayed to anyone using your function:

• Label - Name of the setting, which users see when configuring the function.
• Name - Auto-generated name of the setting to use in function's source code.
• Type - Type of the setting's value.
• Description - Optional description, which appears below the setting name.
• Required - Enable this to ensure that the setting cannot be saved without a value.
• Encrypted - Enable to encrypt the value of this setting. Use this setting for sensitive data, like API keys.

As you change the values, a preview to the right updates to show how your setting will look and work.

Click Add Setting to save the new setting.

Once you save a setting, it appears in the Settings tab for the function. You can edit or delete settings from this tab.

Expand image

Next, fill out this setting's value in Test tab, so that you can run the function and check the setting values being passed.

Note, this value is only for testing your function.

Expand image

Now that you've configured a setting and filled in a test value, you can add code to read its value and run the function:

1
async function onRequest(request, settings) {
2
  const apiKey = settings.apiKey
3
  //=> "super_secret_string"
4
}

When you deploy a source function in your workspace, you are prompted to fill out settings to configure the source. You can access these settings later by navigating to the Source Settings page for the source function.

Expand image

You can test your code directly from the editor in two ways: either by receiving real HTTPS requests through a webhook, or by manually constructing an HTTPS request from within the editor.

The advantage of testing your source function with webhooks is that all incoming data is real, so you can test behavior while closely mimicking the production conditions.

Note: Segment has updated the webhook URL to api.segmentapis.com/functions. To use webhooks with your function, you must:

• Generate a Public API token.
• Create a Public API Token, or follow these steps: In your Segment Workspace, navigate to Settings > Workspace settings > Access Management > Token. Click + Create Token. Create a description for the token and assign access. Click Create and save the access token before clicking Done.
• For POST calls, use this Public API token in the Authorization Header, as Bearer Token : public_api_token

You can use webhooks to test the source function either by sending requests manually (using any HTTP client such as cURL, Postman, or Insomnia), or by pasting the webhook into an external server that supports webhooks (such as Slack).

A common Segment use case is to connect a Segment webhooks destination or webhook actions destination to a test source, where the Webhook URL/endpoint that is used corresponds to the provided source function's endpoint, then you can trigger test events to send directly to that source, which are routed through your Webhook destination and continue on to the source function: Source > Webhook destination > Source Function.

From the source function editor, copy the provided webhook URL (endpoint) from the "Auto-fill via Webhook" dialog.

Note : When a new source is created that utilizes a source function, the new source's endpoint (webhook URL) will differ from the URL that is provided in the source function's test environment.

To test the source function:

1. Send a POST request to the source function's provided endpoint (webhook URL)
2. Include an event body
3. The request must include these Headers:

• Content-Type : application/json or Content-Type : application/x-www-form-urlencoded
• Authorization : Bearer _your_public_api_token_

You can also manually construct the headers and body of an HTTPS request inside the editor and test with this data without using webhooks. The Content-Type Header is required when testing the function:

• Content-Type : application/json or Content-Type : application/x-www-form-urlencoded

Expand image

After you finish building your source function, click Configure to name it, then click Create Function to save it. The source function appears on the Functions page in your workspace's catalog.

If you're editing an existing function, you can Save changes without updating instances of the function that are already deployed and running.

You can also choose to Save & Deploy to save the changes, and then choose which already-deployed functions to update with your changes. You might need additional permissions to update existing functions.

Your function may encounter errors that you missed during testing, or you might intentionally throw errors in your code (for example, if the incoming request is missing required fields).

If your function throws an error, execution halts immediately. Segment captures the incoming request, any console logs the function printed, and the error, and displays this information in the function's Errors tab. You can use this tab to find and fix unexpected errors.

Expand image

Functions can throw an Error or custom Error, and you can also add additional helpful context in logs using the console API. For example:

1
async function onRequest(request, settings) {
2
  const body = request.json()
3
  const userId = body.userId
4

5
  console.log('User ID is', userId)
6

7
  if (typeof userId !== 'string' || userId.length < 8) {
8
    throw new Error('User ID is invalid')
9
  }
10

11
  console.log('User ID is valid')
12
}

• Bad Request: Any error thrown by your code not covered by the other errors.
• Invalid Settings: A configuration error prevented Segment from executing your code. If this error persists for more than an hour, contact Segment Support.
• Message Rejected: Your code threw InvalidEventPayload or ValidationError due to invalid input.
• Unsupported Event Type: Your code doesn't implement a specific event type (for example, onTrack()) or threw an EventNotSupported error.
• StatusCode: 429, TooManyRequestsException: Rate Exceeded: Rate limit exceeded. These events will be retried when the rate becomes available.
• failed calling Tracking API: the message is too large and over the maximum 32KB limit: Segment's Tracking API can only handle API requests that are 32KB or smaller. Reduce the size of the request for Segment to accept the event.
• Retry: Your code threw RetryError indicating that the function should be retried.

Segment only attempts to run your source function again if a Retry error occurs.

Functions have specific roles which can be used for access management in your Segment workspace.

Access to functions is controlled by two permissions roles:

• Functions Admin: Create, edit, and delete all functions, or a subset of specified functions.
• Functions Read-only: View all functions, or a subset of specified functions.

You also need additional Source Admin permissions to enable source functions, connect destination functions to a source, or to deploy changes to existing functions.

If you are a Workspace Owner or Functions Admin, you can manage your source function from the Functions tab in the catalog.

From the Functions tab, click Connect Source and follow the prompts to set it up in your workspace.

After configuring, find the webhook URL - either on the Overview or Settings → Endpoint page.

Copy and paste this URL into the upstream tool or service to send data to this source.

Segment retries invocations that throw RetryError or Timeout errors up to six times. After six attempts, the request is dropped. The initial wait time for the retried event is a random value between one and three minutes. Wait time increases exponentially after every retry attempt. The maximum wait time between attempts can reach 20 minutes.

Retry errors only appear in the source function error logs if the event has exhausted all six retry attempts and, as a result, has been dropped.

The maximum payload size for an incoming webhook payload is 512 KiB.

The execution time limit is five seconds, however we strongly recommend that you keep execution time as low as possible. If you are making multiple external requests you can use async or await to make them concurrently, which will help keep your execution time low.

Segment alphabetizes payload fields that come in to deployed source functions. Segment doesn't alphabetize payloads in the Functions tester. If you need to verify the exact payload that hits a source function, alphabetize it first. You can then make sure it matches what the source function ingests.

GET requests are not supported with a source function. Source functions can only receive data through POST requests.

No. Tracking Pixels operate client-side only and need to be loaded onto your website directly. Source functions operate server-side only, and aren't able to capture or implement client-side tracking code. If the tool you're hoping to integrate is server-side, then you can use a Source function to connect it to Segment.

The test function interface has a 4KB console logging limit. Outputs surpassing this limit will not be visible in the user interface.

No, Source functions can't send custom responses to the tool that triggered the Function's webhook. Source functions can only send a success or failure response, not a custom one.

This error occurs because Segment prevents Source functions from sending data back to their own webhook endpoint (https://fn.segmentapis.com). Allowing this could create an infinite loop where the function continuously triggers itself.

To resolve this error, check your Function code and ensure the URL https://fn.segmentapis.com is not included. This URL is used to send data to a Source Function and shouldn't appear in your outgoing requests. Once you remove this URL from your code, you'll be able to save the Function successfully.