Functions enable you to write code or leverage existing integrations to address your business needs, without the need to spin up your own servers or incur an increased latency through call-outs to an external server or serverless technology. The code you write or use runs within PubNub's operational environment, giving you the scale and speed that you need for your applications.
To create a function you need to first create a module. Think of a module as a container for your functions.
To create a Module:
Choose an app with a corresponding keyset.
Fill in the mandatory Name field and the optional Description field.
For further information on how to create functions, refer to the Serverless processing section.
You can select the module to view all functions that have been created inside of it.
At first glance, you can see whether a module is Running or Stopped. You can also see a number of metrics related to functions inside that module:
|Total||The number of created functions inside the module.|
|Running||All functions in the module are running and operational.|
|Failed||One or more functions in the module failed to run because of an error, and all functions are stopped. Check the logs for more information.|
|Stopped||None of the functions in the module are running. Messages will pass through the PubNub network without triggering your saved Functions.|
|Pending||Functions in the module are being started. This is a transient state and the module may remain in this state for up to 20 seconds.|
This section gives you an overview of all functions that may be available in a module:
|Function||Name of your function.|
|Event||Event type tied to your function.|
|Channels/Path/Interval||Configuration parameters of your function.|
|State||State of your function. Refer to the previous table to view available states.|
|Log level||Log output configuration. Available log levels include: Debug, Log, Assert, Warn, Error.|
Third-party services integration
Apart from creating a function by yourself, you can also leverage existing third-party integrations, including but not limited to language translation, sentiment analysis, SMS, text-to-speech, and content moderation. You can do that by clicking on the Import Block button inside a module. This takes you to the Integrations catalog outside of Admin Portal where you can view all possible integrations or read a brief overview of required dependencies. After you choose an integration to import, it will open in a new tab.
Function configuration view
You can click one of the functions inside the module to open the function configuration view. This view gives you the ability to configure your function, change its code as well as rename it, specify which channel the function uses, or test your function. The view is divided into the following sections:
You can configure the following parts of your function:
|Name||Current name of the function.|
|Event type||Event type of the currently selected function.|
|Log level||Log output. Available log levels include: Debug, Log, Assert, Warn, Error.|
|Channel||Channel the function runs on.|
|URI Path||A suffix that is added to the full URL path at which your On Request function is triggered. For example, if you specify the URI Path as |
|Test payload||Test message payload. Its initial structure changes based on the event type of the selected function. You can change the payload to suit your needs.|
|My Secrets||Credentials configuration. You can store secrets and use them in the function body.|
Use it to create or modify the code responsible for your function. The example code differs between function event types and is based on the one you select when you first create a function. If you change the function event type from the drop-down list in the function parameters section, the code will not refresh.
For further information on how to create functions, refer to the Creating a function section.
Displays debug information about your module and function. You can show all filters, clear the console, or filter the view by selecting one or more of the following:
|Filter name||Displayed information|
|Module status||The deployment status and deployment regions.|
|Channel status||The channel your function runs on.|
|Console output||The output logged to the console from within your function body.|
|Test messages||Type and body of published messages set in the Test payload section.|
Wildcard channels won't work inside the code editor, you have to provide a specific channel.