Introducing Xano Actions
Build and share reusable visual building blocks
Xano Actions are reusable visual functions that serve as the building blocks for any workflow. Easily connect to various third-party services and modify the business logic to fit your unique use case.
Discover
Browse and discover actions created by the community. Test them directly without logging in.
Create
Build your own custom Actions and share them with anyone.
Install
Easily install Actions into your Xano workspace and integrate them seamlessly into your workflows.
Browse by category
Featured Actions
Function Documentation: OpenAI -> Create a Chat Completion
OpenAI API documentation
Overview
This function generates a chat completion using the OpenAI API based on a user-provided input text. It requires parameters such as the model & input message. The function validates environment variables and conditions before making an API request and processing the response.
Inputs
openaiapikey (registry|text) Required Sensitive data
Description: The API key for your OpenAI account.
model (enum) Required
Description: Specifies the model to be used for generating the chat completion.
Options:
gpt-4o-mini (default)
gpt-4o
message (text) Required
Description: The input message or prompt that will be sent to the OpenAI API for generating the chat completion.
Function Stack
OpenAI API Request
API Request to https://api.openai.com
Purpose: Sends a request to the OpenAI API using the specified model and message.
Precondition: openaiapiresponse.status == 200
Purpose: Confirms that the API request was successful (HTTP status code 200).
OpenAI API Response
Create Variable: response
Purpose: Stores the response from the OpenAI API.
Response
The function returns the generated chat completion
Success response
`json
{"Barack Obama is 6 feet 1 inch tall (185 cm)."}
`
Error response
`json
{
"message": "Incorrect API key provided: ssk-None***GQPD. You can find your API key at https://platform.openai.com/account/api-keys."
}
`
Example
Input
`json
{ "model": "gpt-4o-mini", "message": "What is Obama's height?" }
`
Response
`json
{"Barack Obama is 6 feet 1 inch tall (185 cm)."}
`
Function Documentation: Brevo → Send Single Email
Brevo API documentation
Overview
This function sends a single email using the Brevo (Sendinblue) API with HTML content. It requires inputs such as the API key, sender and receiver details, email content, and subject. The function validates and processes the input before making a request to the Brevo API.
Inputs
brevoapikey (registry/text) Required
Description: API key for authenticating with Brevo API.
Example: xkeysib-...
from (object) Required
Description: The sender's email address.
Example: sender@example.com
to (object) Required
Description: The recipient's email address.
Example: receiver@example.com
message_html (text) Required
Description: The HTML content to be sent.
Example: <html><body><h1>Hello</h1></body></html>
subject (text) Required
Description: The subject of the email.
Example: Welcome to our service!
Function Stack
Try / Catch Block
Precondition: Check Valid HTML Content
Description: Ensures the HTML content for the email is valid before proceeding.
API Request to Sendinblue
API Request to https://api.brevo.com/v3/smtp/email
Purpose: Sends the email using the Brevo (Sendinblue) API.
Return Value: The API response is stored as api_response.
Create Variable: response
Variable: var: response = var: api_response.response.result
Purpose: Stores the API response for the SMS send operation.
2 Error Handling (Catch)
Create Variable: response
Purpose: If the API call fails or returns an error, this block catches the error and provides an error message.
Response
The function returns the result of the email send operation, including status and any relevant messages.
Success Response
`json
{
"messageId": "<202410100.1236169*@smtp-relay.mailin.fr>",
}
`
Error response
`json
{
"message": "Key not found",
"code": "unauthorized"
}
`
Example
Input
`json
{
"from":{
"from_name":"John",
"from_email":"sohansakhare**@gmail.com"
},
"to":{
"to_name":"David",
"to_email":"sajankumar.*@unicoco*.com"
},
"email_html":"<html><head></head><body><p>Hello world</p></body></html>",
"subject":"abc"
}
`
Output
`json
{
"messageId": "<202410100.1236169*@smtp-relay.mailin.fr>"
}
`
A helper function that creates a 1-click MCP install link for Cursor using URL-based authentication with Xano MCP Servers. This function generates deeplinks and various markup formats (Markdown, HTML, JSX) that allow users to install MCP servers directly into Cursor with a single click.
Input Parameters
| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| mcpserverurl | string | Yes | The full URL endpoint of the Xano MCP server |
| server_name | string | Yes | Display name for the MCP server |
| server_type | enum | Yes | Type of MCP server connection |
Example Input
`json
{
"mcpserverurl": "https://x123-wu0q-dtak.n7.xano.io/x2/mcp/6vi_VA6-/mcp/sse",
"server_name": "Xano MCP Server Name",
"server_type": "sse"
}
`
Example Output
`json
{
"deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=Xano MCP Server Name&config=eyJ0eXBlIjoic3NlIiwidXJsIjoiaHR0cHM6Ly94MTIzLXd1MHEtZHRhay5uNy54YW5vLmlvL3gyL21jcC82dmlfVkE2LS9tY3Avc3NlIn0=",
"markdown": {
"dark": "",
"light": ""
},
"html": {
"dark": "<a href=\"cursor://anysphere.cursor-deeplink/mcp/install?name=Xano MCP Server Name&config=eyJ0eXBlIjoic3NlIiwidXJsIjoiaHR0cHM6Ly94MTIzLXd1MHEtZHRhay5uNy54YW5vLmlvL3gyL21jcC82dmlfVkE2LS9tY3Avc3NlIn0=\"><img src=\"https://cursor.com/deeplink/mcp-install-dark.svg\" alt=\"Add Xano MCP Server Name MCP server to Cursor\" height=\"32\" /></a>",
"light": "<a href=\"cursor://anysphere.cursor-deeplink/mcp/install?name=Xano MCP Server Name&config=eyJ0eXBlIjoic3NlIiwidXJsIjoiaHR0cHM6Ly94MTIzLXd1MHEtZHRhay5uNy54YW5vLmlvL3gyL21jcC82dmlfVkE2LS9tY3Avc3NlIn0=\"><img src=\"https://cursor.com/deeplink/mcp-install-light.svg\" alt=\"Add Xano MCP Server Name MCP server to Cursor\" height=\"32\" /></a>"
},
"jsx": {
"dark": "<a href=\"cursor://anysphere.cursor-deeplink/mcp/install?name=Xano MCP Server Name&config=eyJ0eXBlIjoic3NlIiwidXJsIjoiaHR0cHM6Ly94MTIzLXd1MHEtZHRhay5uNy54YW5vLmlvL3gyL21jcC82dmlfVkE2LS9tY3Avc3NlIn0=\"><img src=\"https://cursor.com/deeplink/mcp-install-dark.svg\" alt=\"Add Xano MCP Server Name MCP server to Cursor\" height=\"32\" /></a>",
"light": "<a href=\"cursor://anysphere.cursor-deeplink/mcp/install?name=Xano MCP Server Name&config=eyJ0eXBlIjoic3NlIiwidXJsIjoiaHR0cHM6Ly94MTIzLXd1MHEtZHRhay5uNy54YW5vLmlvL3gyL21jcC82dmlfVkE2LS9tY3Avc3NlIn0=\"><img src=\"https://cursor.com/deeplink/mcp-install-light.svg\" alt=\"Add Xano MCP Server Name MCP server to Cursor\" height=\"32\" /></a>"
}
}
`
Output Fields
deeplink
The raw Cursor deeplink URL that can be used programmatically or shared directly.
markdown
Ready-to-use Markdown install buttons with Cursor's official badge images:
dark: Dark theme install button
light: Light theme install button
html
HTML anchor tags with embedded install buttons:
dark: Dark theme HTML button
light: Light theme HTML button
jsx
JSX-compatible HTML for React components:
dark: Dark theme JSX button
light: Light theme JSX button
Usage Notes
The config parameter in the deeplink contains a base64-encoded JSON configuration
All markup formats include proper URL encoding for compatibility
The function supports both dark and light theme variants for different UI contexts
Install buttons use Cursor's official badge images hosted at cursor.com/deeplink/
Implementation Details
The function creates a Cursor deeplink following the format:
`
cursor://anysphere.cursor-deeplink/mcp/install?name={SERVERNAME}&config={BASE64CONFIG}
`
Where {BASE64_CONFIG} is a base64-encoded JSON object containing:
`json
{
"type": "{server_type}",
"url": "{mcpserverurl}"
}
`
Creates a new array concatenating array with any additional arrays and/or values.
Allows you to concatenate up to 9 arrays.
`
{
"array_1": [1,2,3],
"array_2": 12,
"array_3": [],
"array_4": [],
"array_5": [],
"array_6": "foo",
"array_7": [],
"array_8": true,
"array_9": {}
}
`
would return
`
[1,2,3,12,"foo",true,{}]
`
John Carmack’s fast inverse square root function is a famous algorithm used in computer graphics, particularly in 3D rendering, to compute the inverse square root of a number quickly.
It was notably used in the Quake III Arena game engine to speed up computations related to lighting, shading, and physics. The function approximates the value of 1/sqrt(x) very efficiently, significantly faster than the traditional method of calculating a square root followed by division.
Function Documentation: HubSpot → Create Contact
Overview
This function creates a new contact in HubSpot using specified input parameters. It involves setting environment variables, preparing the request, and handling the response.
Inputs
hubspotapikey (registry|text) Required Sensitive data
Description: The API key for your HubSpot account.
first_name (text)
Description: The first name of the contact.
last_name (text)
Description: The last name of the contact.
email (text)
Description: The email address of the contact.
company (text)
Description: The company associated with the contact.
lead_status (enum)
Description: The lead status of the contact.
Options:
NEW
OPEN
IN_PROGRESS
OPEN_DEAL
UNQUALIFIED
ATTEMPTEDTOCONTACT
CONNECTED
BAD_TIMING
contact_owner (integer)
Description: The owner of the contact.
phone_number (text)
Description: The phone number of the contact.
additional_properties (json)
Description: Additional properties in JSON format.
Schema:
`json
{
"additionalProp1": "string",
"additionalProp2": "string",
"additionalProp3": "string"
}
`
Function Stack
Set Properties Object
Create Variable: properties_object
Purpose: Sets properties object from input: additional_properties.
HubSpot API Request
API Request to https://api.hubapi.com/crm/v3/objects/contacts
Purpose: Sends a POST request to create a new contact in HubSpot.
Preconditions
Precondition: hubspot_api.response.status == 201
Purpose: Ensures successful creation of the contact with HTTP status code 201.
Response
The function returns the result from the HubSpot API response.
Success response
`json
{
"id": "12345678",
"properties": {
"company": "Xano",
.
.
.
},
"createdAt": "2024-09-23T13:26:23.352Z",
"updatedAt": "2024-09-23T13:26:23.352Z",
"archived": false
}
`
Error message
`json
{
"message":"Uh oh! Hubspot returned with an error: Property values were not valid: [{\"isValid\":false,\"message\":\"Property \\\"prop2\\\" does not exist\",\"error\":\"PROPERTYDOESNTEXIST\",\"name\":\"prop2\",\"localizedErrorMessage\":\"Property \\\"prop2\\\" does not exist\",\"portalId\":47373842},{\"isValid\":false,\"message\":\"Property \\\"prop1\\\" does not exist\",\"error\":\"PROPERTYDOESNTEXIST\",\"name\":\"prop1\",\"localizedErrorMessage\":\"Property \\\"prop1\\\" does not exist\",\"portalId\":47373842}]"
}
`
Example
Input
`json
{
"first_name": "Unico",
"last_name": "Connect",
"email": "imagine@xano.com",
"company": "UC",
"lead_status": "OPEN",
"contact_owner": 0,
"phone_number": "123456",
"customer_Id": 0,
"additional_properties":
{
"mobilephone":"123456"
}
}
`
Output
`json
{
"id": "123456789",
"properties": {
"company": "UC",
"createdate": "2024-09-23T13:30:40.386Z",
"email": "imagine@xano.com",
"firstname": "Unico",
"hsallcontact_vids": "60968500829",
"hscurrentlyenrolledinprospecting_agent": "false",
"hsemaildomain": "xano.com",
"hsiscontact": "true",
"hsisunworked": "true",
"hsleadstatus": "OPEN",
"hslifecyclestagelead_date": "2024-09-23T13:30:40.386Z",
"hsmarketablestatus": "false",
"hsmarketableuntil_renewal": "false",
"hsmembershiphasaccessedprivate_content": "0",
"hsobjectid": "60968500829",
"hsobjectsource": "INTEGRATION",
"hsobjectsource_id": "3898752",
"hsobjectsource_label": "INTEGRATION",
"hs_pipeline": "contacts-lifecycle-pipeline",
"hsregisteredmember": "0",
"hssearchablecalculatedmobilenumber": "123456",
"hssearchablecalculatedphonenumber": "123456",
"lastmodifieddate": "2024-09-23T13:30:40.386Z",
"lastname": "Connect",
"lifecyclestage": "lead",
"mobilephone": "123456",
"phone": "123456"
},
"createdAt": "2024-09-23T13:30:40.386Z",
"updatedAt": "2024-09-23T13:30:40.386Z",
"archived": false
}
`
Function Documentation: Postmark → Send Email with Template
Overview
This function allows you to send emails using the Postmark API with a pre-defined template. You can specify the recipient email address, the template ID, and the data to populate the template placeholders.
Inputs
postmarkbaseurl (registry|text) Required
Description: The base url for calling the Postmark API (e.g., "https://api.postmarkapp.com/").
postmarkservertoken (registry|text) Required Sensitive data
Description: This is the Postmark Server API Token (e.g., "14g8dce4-7054-47c9-a18a-2107e5cf4e41"). This is needed for authentication on endpoints.
from_email (text) Required
Description: The email address that will appear as the sender.
Example: noreply@yourdomain.com
to_emails (text) Required
Description: A list of email addresses to send the batch emails to.
Example: user1@example.com
template_id (integer) Required
Description: The ID of the Postmark template to use.
Example: 12345
template_model (json) Required
Description: The data to populate the template placeholders. The structure of this data depends on your specific Postmark template.
Example: Refer to Postmark documentation for template data structure.
Function Stack
Create Variable:
Create Variable: api_url
Purpose: Constructs the API URL for sending emails with templates.
Create Variable:
Create Variable: api_token
Purpose: Stores the Postmark API token.
Precondition:
Precondition: from_email should not exceed 255 characters.
Purpose: Ensures the sender email address is not too long.
Precondition: from_email is a valid email format.
Purpose: Ensures the sender email address is formatted correctly.
Precondition: to_email is a valid email format and allows comma-separated values.
Purpose: Ensures recipient email addresses are formatted correctly and the list is not too long.
Precondition: to_email should not exceed 50 email addresses.
Purpose: Limits the number of recipients per batch.
Postmask API Request:
API Request to: https://api.postmarkapp.com/email
Purpose: Sends a POST request to the api_url with the following payload:
`JSON
{
"from_email": "noreply@yourdomain.com",
"to_email": "user@example.com",
"template_id": 12345,
"template_model": {
"name": "John Doe",
"email": "john.doe@example.com"
}
}
`
Create Variable:
Create Variable: postmark_response
Purpose: Stores the response from the Postmark API.
Create Variable:
Create Variable: response
Purpose: Creates a response object with the result from the Postmark API.
Response
The function returns the result from the Postmark API response.
Success response
`json
{
"To": "user1@example.com",
"SubmittedAt": "2024-10-07T14:33:15.817Z",
"MessageID": "message-id-1",
"ErrorCode": 0,
"Message": "OK"
},
{
"To": "user2@example.com",
"SubmittedAt": "2024-10-07T14:33:15.817Z",
"MessageID": "message-id-2",
"ErrorCode": 0,
"Message": "OK"
}
`
Error response
`json
{
"ErrorCode": 401,
"Message": "Unauthorized: Missing or incorrect API key."
}
`
Example
Input
`json
{
"from_email": "noreply@yourdomain.com",
"to_email": "user@example.com",
"template_id": 12345,
"template_model": {
"name": "John Doe",
"email": "john.doe@example.com"
}
}
`
Output
`json
{
"To": "user@example.com",
"SubmittedAt": "2024-10-07T14:33:15.817Z",
"MessageID": "message-id-1",
"ErrorCode": 0,
"Message": "OK"
}
`
Compute the central moment at different level (default second). Change the power to compute different central moment.
Second Central Moment
`
{
"numbers": [1,2,3,4,5,6,7,8,9,10],
"power": 2,
"bias": false
}
`
Second Central Moment (unbiased): 9.166666666666666
Third Central Moment
`
{
"numbers": [1,2,3,4,5,6,7,8,9,10],
"power": 3,
"bias": false
}
`
Unbiased Third Central Moment: 0.0
Fourth Central Moment
`
{
"numbers": [1,2,3,4,5,6,7,8,9,10],
"power": 4,
"bias": false
}
`
Unbiased Fourth Central Moment: 23.9806547
Function Documentation: OpenAI → Generate an image (Simple)
OpenAI Vision API
Overview
This function generates an image using the OpenAI API based on a text prompt, with options for size and model. It is designed to take user input, validate it, and return an image URL if the request is successful.
Inputs
openaiapikey (registry | text)
Purpose: API key required to authenticate with OpenAI's image generation endpoint.
Example: "sk-...your-key-here"
prompt (text)
Purpose: The text description for the image to generate.
Example: "A futuristic city with flying cars"
img_size (enum)
Purpose: The size of the generated image.
Options:
"1024x1024"
"1024x1792"
"1792x1024"
model (enum)
Purpose: The OpenAI model to use for generating the image.
Options:
"dall-e-3"
"dall-e-2"
Function Stack
OpenAI API Request
Endpoint: https://api.openai.com/v1/images/generations
Purpose: Sends a POST request to the OpenAI API with the prompt and image size parameters.
Preconditions
Condition: openai_api.response.status == 200
Purpose: Ensures that the request was successful (HTTP 200 status code).
OpenAI API Response
Create Variable: response
Purpose: Stores the response from OpenAI API, which contains the URL of the generated image.
Response
The function returns the generated image URL or image content.
Success response
`json
{
"image_url": "https://api.openai.com/v1/images/abcd1234"
}
`
Error response
`json
{
"message": "Incorrect API key provided: ssk-None***GQPD. You can find your API key at https://platform.openai.com/account/api-keys."
}
`
Example
Input
Headers:
Authorization: Bearer openaiapikey
Body:
`json
{
"prompt": "A futuristic city with flying cars",
"size": "1024x1024",
"model": "DALL-E"
}
`
Output
`json
{
"image_url": "https://api.openai.com/v1/images/abcd1234"
}
`
HubSpot → List Deals
Overview
This function retrieves a list of deals from HubSpot. It involves setting environment variables, preparing the request with optional parameters, and handling the response from the HubSpot API.
Inputs
hubspotapikey (registry|text) Required Sensitive data
Description: The API key for your HubSpot account.
after (integer)
Description: The paging cursor to get the next set of deals.
limit (integer)
Description: The maximum number of deals to retrieve.
properties (text[])
Description: A list of deal properties to retrieve.
propertieswithhistory (text[])
Description: A list of deal properties with their history to retrieve.
Function Stack
HubSpot API Request
API Request to https://api.hubapi.com/crm/v3/objects/deals
Purpose: Sends a GET request to retrieve deals from HubSpot.
Parameters: Includes optional after cursor, limit, and specified properties.
Preconditions
Precondition: hubspot_api.response.status == 200
Purpose: Ensures successful retrieval of deals with HTTP status code 200.
Response
The function returns the result from the HubSpot API response.
Success response
`json
{
"deal_id": 22413038713,
"properties": [],
"propertieswithhistory": [
"closedwonreason"
]
}
`
Error response
`json
{
"message": "Uh oh! Hubspot returned with an error: Authentication credentials not found. This API supports OAuth 2.0 authentication and you can find more details at https://developers.hubspot.com/docs/methods/auth/oauth-overview"
}
`
Example
Input
`json
{
"after": "22393633108",
"limit": 10,
"properties": [],
"propertieswithhistory": [
"dealname"
]
}
`
Output
`json
[
{
"id": "22393633108",
.
.
.
},
.
.
]
`
Function Documentation: QuickBooks -> Create Payment
Quickbooks API documentation
Overview
This function creates a payment in QuickBooks by making an API call. It uses the QuickBooks API with the provided realm ID, amount, and consumer reference.
This action works on production environment only, for sandbox environment refer documentation at https://developer.intuit.com/app/developer/qbo/docs/api/accounting/all-entities/payment#create-a-payment.
Inputs
quickbooksrealmid (registry/text) Required
Description: The QuickBooks realm ID associated with the account.
Example: quickbooksrealmabc123
amount (decimal) Required
Description: The amount of the payment to be created.
Example: 100.50
consumer_ref (integer) Required
Description: A reference number associated with the consumer.
Example: 12345
quickbooksapitoken (registry|text) Required
Description: The JWT token used to authenticate requests to the quickbooks API.
Example: xkeysib-...
Function Stack
Try / Catch Block
QuickBooks API Call
API Request to https://quickbooks.api.intuit.com/v3/company/{quickbooksrealmid}/payment
Purpose: Sends a payment creation request to QuickBooks using the realm ID, amount, and consumer reference.
Return Value: The API response is stored as response.
Response Variable
Variable: var: response = var: quickbooksapiresponse.response
Purpose: Captures the response returned by the QuickBooks API.
Error Handling (Catch)
Create Variable: response
Purpose: Catches and handles any errors that occur during the QuickBooks API call and logs the error message.
Response
The function returns the result of the QuickBooks payment creation.
Success Response
`json
{
"Payment": {
"CustomerRef": {
"value": "20",
"name": "Red Rock Diner"
},
"DepositToAccountRef": {
"value": "4"
},
"TotalAmt": 25,
"UnappliedAmt": 25,
"ProcessPayment": false,
"domain": "QBO",
"sparse": false,
"Id": "150",
"SyncToken": "0",
"MetaData": {
"CreateTime": "2024-10-11T07:17:33-07:00",
"LastUpdatedTime": "2024-10-11T07:17:33-07:00"
},
"TxnDate": "2024-10-11",
"CurrencyRef": {
"value": "USD",
"name": "United States Dollar"
}
},
"time": "2024-10-11T07:17:32.610-07:00"
}
`
Error Response
`json
{
"type": "error",
"error": {
"code": "paymentcreationfailed",
"message": "Failed to create the payment due to an invalid realm ID."
}
}
`
Example
Input
`json
{
"quickbooksrealmid": "{quickbooksrealmid}",
"amount": "{amount}",
"consumerref": "{consumerref}"
}
`
Output
`json
{
"Payment": {
"CustomerRef": {
"value": "20",
"name": "Red Rock Diner"
},
"DepositToAccountRef": {
"value": "4"
},
"TotalAmt": 25,
"UnappliedAmt": 25,
"ProcessPayment": false,
"domain": "QBO",
"sparse": false,
"Id": "150",
"SyncToken": "0",
"MetaData": {
"CreateTime": "2024-10-11T07:17:33-07:00",
"LastUpdatedTime": "2024-10-11T07:17:33-07:00"
},
"TxnDate": "2024-10-11",
"CurrencyRef": {
"value": "USD",
"name": "United States Dollar"
}
},
"time": "2024-10-11T07:17:32.610-07:00"
}
`
Creates an array with all falsey values removed.
The values
false
null
0
"" (empty string)
{} (empty object)
[] (empty array)
are all falsey.
Postmark → Send Single Email
Overview
This function allows you to send a single email using the Postmark API. It requires parameters such as the sender email address, recipient email address, subject, body (in either HTML or plain text format), and optionally a template ID.
Inputs
postmarkbaseurl (registry|text) Required
Description: The base url for calling the Postmark API (e.g., "https://api.postmarkapp.com/").
postmarkservertoken (registry|text) Required Sensitive data
Description: This is the Postmark Server API Token (e.g., "14g8dce4-7054-47c9-a18a-2107e5cf4e41"). This is needed for authentication on endpoints.
from_email (text) Required
Description: The email address of the sender.
Example: noreply@yourdomain.com
to_email (text) Required
Description: The email address of the recipient.
Example: user@example.com
subject (text) Required
Description: The subject line of the email.
Example: Welcome to Our Service
html_body (text) Optional
Description: The HTML content of the email message. If provided, it takes precedence over text_body.
Example: <h1>Hello, John!</h1><p>Thank you for signing up.</p>
text_body (text) Optional
Description: The plain text content of the email message. If provided and html_body is not, it will be used.
Example: Hello, John! Thank you for signing up.
Function Stack
Create Variable
Create Variable: api_url
Purpose: Constructs the API URL for sending single emails.
Create Variable
Create Variable: api_token
Purpose: Stores the Postmark API token.
Precondition Logic
Precondition: from_email should not exceed 255 characters.
Purpose: Ensures the sender email address is not too long.
Precondition: from_email is a valid email format.
Purpose: Ensures the sender email address is formatted correctly.
Precondition: to_email is a valid email format.
Purpose: Ensures recipient email address is formatted correctly.
Precondition: to_email should not exceed 50 email addresses.
Purpose: Limits the number of recipients to avoid batch size issues.
Precondition: Either textbody or htmlbody (or both) are provided.
Purpose: Ensures that at least one form of email content is available.
Precondition: html_body is a valid HTML format.
Purpose: Ensures that if HTML is provided, it is well-formed.
API Request
API Request to: https://api.postmarkapp.com/email
Purpose: Sends a POST request to the api_url with the following payload:
`json
{
"from_email": "noreply@yourdomain.com",
"to_email": "user@example.com",
"subject": "Welcome to Our Service",
"html_body": "<h1>Hello, John!</h1><p>Thank you for signing up.</p>", // Optional
"text_body": "Hello, John! Thank you for signing up." // Optional
}
`
Create Variable
Create Variable: postmark_response
Purpose: Stores the response from the Postmark API.
Create Variable
Create Variable: response
Purpose: Creates a response object containing the result from the Postmark API.
Conditional Check
Conditional: Checks if the response status is 200 and the error code is 0.
If True: Updates the response object to indicate success.
If False: Updates the response object to indicate an error.
Response
The function returns either a success message or an error message depending on the outcome.
Success Response
`json
{
"To": "user@example.com",
"SubmittedAt": "2024-10-07T14:33:15.817Z",
"MessageID": "message-id-1",
"ErrorCode": 0,
"Message": "OK"
}
`
Error Response
`json
{
"ErrorCode": 401,
"Message": "Unauthorized: Missing or incorrect API key."
}
`
Example
Input
`json
{
"from_email": "noreply@yourdomain.com",
"to_email": "user@example.com",
"subject": "Welcome to Our Service",
"html_body": "<h1>Hello, John!</h1><p>Thank you for signing up.</p>",
"text_body": "Hello, John! Thank you for signing up."
}
`
Output
`json
{
"To": "user@example.com",
"SubmittedAt": "2024-10-07T14:33:15.817Z",
"MessageID": "message-id-1",
"ErrorCode": 0,
"Message": "OK"
}
`
Function Documentation: HubSpot → Get Contact
Overview
This function retrieves a specific contact from HubSpot using the contact's ID. It involves setting environment variables, preparing the request, and handling the response from the HubSpot API.
Inputs
id (integer)
Description: The unique identifier of the contact to be retrieved.
properties (text[])
Description: A list of contact properties to retrieve.
Function Stack
HubSpot API Request
API Request to https://api.hubapi.com/crm/v3/objects/contacts/{id}
Purpose: Sends a GET request to retrieve the specified contact from HubSpot.
Preconditions
Precondition: hubspot_api.response.status == 200
Purpose: Ensures successful retrieval of the contact with HTTP status code 200.
Response
The function returns the result from the HubSpot API response.
Success response
`json
{
"id": "12345",
"properties": {
"company": "HubSpot",
"createdate": "2024-09-12T10:58:14.335Z",
"hsobjectid": "12345",
"lastmodifieddate": "2024-09-12T10:58:18.831Z"
},
"createdAt": "2024-09-12T10:58:14.335Z",
"updatedAt": "2024-09-12T10:58:18.831Z",
"archived": false
}
`
Error response
`json
{
"message": "Uh oh! Hubspot returned with an error: Authentication credentials not found. This API supports OAuth 2.0 authentication and you can find more details at https://developers.hubspot.com/docs/methods/auth/oauth-overview"
}
`
Example
Input
`json
{
"id": 123456,
"properties": [
"company"
]
}
`
Output
`json
{
"id": "123456",
"properties": {
"company": "UC",
"createdate": "2024-09-23T13:30:40.386Z",
"hsobjectid": "60968500829",
"lastmodifieddate": "2024-09-23T13:31:43.044Z"
},
"createdAt": "2024-09-23T13:30:40.386Z",
"updatedAt": "2024-09-23T13:31:43.044Z",
"archived": false
}
`
Function Documentation: HubSpot → Update Contact
Overview
This function allows you to edit an existing contact in HubSpot using specified input parameters. It involves setting environment variables, preparing the request with updated information, and handling the response from the HubSpot API.
Inputs
hubspotapikey (registry|text) Required Sensitive data
Description: The API key for your HubSpot account.
first_name (text)
Description: The updated first name of the contact.
last_name (text)
Description: The updated last name of the contact.
email (email)
Description: The updated email address of the contact.
company (text)
Description: The updated company associated with the contact.
lead_status (enum)
Description: The updated lead status of the contact.
Options:
NEW
OPEN
IN_PROGRESS
OPEN_DEAL
UNQUALIFIED
ATTEMPTEDTOCONTACT
CONNECTED
BAD_TIMING
contact_owner (integer)
Description: The updated owner of the contact.
phone_number (text)
Description: The updated phone number of the contact.
contact_id (integer)
Description: The unique identifier of the contact to be edited.
additional_properties (json)
Description: Additional properties in JSON format to be updated.
Schema:
`json
{
"additionalProp1": "string",
"additionalProp2": "string",
"additionalProp3": "string"
}
`
> [❗] You can clear a property value by passing an empty string. Example: {"company":""} . This will clear the value stored in the company field.
Function Stack
Set Properties Object
Create Variable: properties_object
Purpose: Sets properties object from input: additional_properties and other input fields.
HubSpot API Request
API Request to https://api.hubapi.com/crm/v3/objects/contacts/{contact_id}
Purpose: Sends a PATCH request to update the specified contact in HubSpot.
Create Variable
Create Variable: inputss
Purpose: Checks if the company input is null.
Preconditions
Precondition: hubspot_api.response.status == 200
Purpose: Ensures successful update of the contact with HTTP status code 200.
Response
The function returns the result from the HubSpot API response.
Success response
`json
{
"id": "123456789",
"properties": {
"company": "Xano",
.
.
.
"phone": "42"
},
"createdAt": "2024-09-16T12:11:28.596Z",
"updatedAt": "2024-09-23T13:41:47.246Z",
"archived": false
}
`
Error message
`json
{
"message":"Uh oh! Hubspot returned with an error: Property values were not valid: [{\"isValid\":false,\"message\":\"Property \\\"prop2\\\" does not exist\",\"error\":\"PROPERTYDOESNTEXIST\",\"name\":\"prop2\",\"localizedErrorMessage\":\"Property \\\"prop2\\\" does not exist\",\"portalId\":47373842},{\"isValid\":false,\"message\":\"Property \\\"prop1\\\" does not exist\",\"error\":\"PROPERTYDOESNTEXIST\",\"name\":\"prop1\",\"localizedErrorMessage\":\"Property \\\"prop1\\\" does not exist\",\"portalId\":47373842}]"
}
`
Example
Input
`json
{
"first_name": "Xano",
"last_name": "Actions",
"email": "actions@xano.com",
"company": "Xano",
"leadstatus": "OPENDEAL",
"contact_owner": 0,
"phone_number": "42",
"contact_id": 123456789,
"additional_properties": {
"mobilephone":"1024"
}
`
Output
`json
{
"id": "123456789",
"properties": {
"company": "Xano",
.
.
.
"phone": "42"
},
"createdAt": "2024-09-16T12:11:28.596Z",
"updatedAt": "2024-09-23T13:41:47.246Z",
"archived": false
}
`
Featured Packages
LeDash
LeDash is a powerful Xano package inspired by Lodash, bringing its robust utility functions to the Xano ecosystem.
LeDash ensures predictable data handling by safely managing unpredictable or missing objects. Instead of errors, it returns sensible defaults (e.g., empty arrays, objects, or strings) tailored to your expected type, streamlining development and boosting reliability. Statistics
Provides core statistical functions including moments, variance, regression, distribution shape (skewness, kurtosis), and common aggregates like mean, median, percentiles, and sums. Supports both biased and unbiased calculations where relevant, making it useful for exploratory data analysis and lightweight modeling. Notion
The Xano Notion Actions Package is a powerful collection of zero-dependency functions that bridge the gap between your Xano backend and Notion workspaces. Keep your documentation, databases, and workflows perfectly in sync with minimal effort.