SquadStack provides businesses with an omni-channel outreach engine + distributed team of expert calling reps. Our platform qualifies your Leads faster and provides more sales opportunities.
\nWe are tech-first company and strongly believe in end to end integrations to allow for seamless data flow between our systems
\nThroughout this documentation, we will look at the various aspects about integrating your system with Squadstack.
\nTo start with, here's what a fully integrated setup looks like:
\nDepending upon your customer/lead management system, we have multiple ways in which we can integrate with you.
\nHere's some common integration approaches along with their pros and cons:
\nThroughout the documentation certain words will be used to describe relevant parties involved. The definitions are given down below.
\nRefers to the individual/organisation who’ll be using SquadStack’s services to reach out to their customers/potential customers.
\nLead refers to the person(your potential customer) that SquadStack performs the outreach to. All the necessary details of the lead are passed on to SquadStack which will be used in the process of the reach out.
\nCampaign refers to the flow that you have pre-configured on SquadStack’s backend as per your business needs. Any campaign would define a sequence of events and every lead associated to that campaign would follow these sequence of events. Reach out to voicesales@squadstack.com to create your campaign.
\n\nPlease reach out to your Squadstack POC to get the reference ID for your campaign specific endpoint
\n
This endpoint is used to create a new lead in Squadstack.
The request should include a payload with mandatory parameters such as lead_id, phone_number, contact_name.
The lead ID should be unique for each lead as it will be used as an identifying factor for that lead throughout the campaign
\nAlong with the mandatory parameters you can pass additional metadata about the lead that may be relevant to the specific campaign that you are creating the lead im Squadstack
\nlead_id (string, mandatory): The ID of the lead.phone_number (string, mandatory): The phone number associated with the lead.contact_name (string, mandatory): The name of the contact for the lead.custom_field1 (string): A custom field for additional information. You can rename this as per the context of the key that you are sendingcustom_field2 (string): Another custom field for additional information.You can rename this as per the context of the key that you are sendin\n\nAdditional custom fields can be added as per campaign requirement
\n
Upon successful execution, the API returns a status code of 200 and a JSON response containing the details of the lead created, including the phone_number, contact_name, lead_id, and other custom keys passed in the request
{\n \"phone_number\": \"9999999999\",\n \"contact_name\": \"John Doe\",\n \"custom_field2\": \"custom_value2\",\n \"lead_id\": \"sample_lead_id\",\n \"custom_field1\": \"custom_value1\"\n}\n\n\n\nPlease reach out to your Squadstack POC to get the reference ID for your campaign specific endpoint
\n
This endpoint is used to update a lead in Squadstack.
You can use this endpoint to either add new metadata to your lead or update existing metadata. If you are updating exisitng metadata, be sure to use the same key name as passed while lead creation
lead_id (string): The ID of the lead to be updated.
field_to_update (string): The field in the lead that needs to be updated.
Upon a successful request, the response will include the lead_id and the keys that were added/modified via your request.
\nThe response will include the updated lead_id and the updated field_to_update with their new values.
{\n \"lead_id\": \"sample_lead_id\",\n \"field_to_update\": \"new value\"\n}\n\n\n\nPlease reach out to your Squadstack POC to get the reference ID for your campaign specific endpoint
\n
This endpoint allows you upsert a lead into the Squadstack.
When you make an Upsert request:
Request Body
\nlead_id (string,mandatory): The ID of the lead.
phone_number (string,mandatory for the first request): The phone number associated with the lead.
contact_name (string,mandatory for the first request): The name of the contact.
custom_field1 (string): A custom field for additional information. This can be named as per the context of the value
custom_field2 (string): Another custom field for additional information. This can be named as per the context of the value
Response
\ncontact_name (string): The name of the contact.lead_id (string): The ID of the lead.phone_number (string): The phone number associated with the lead.Example Response
\n{\n \"contact_name\": \"John Doe\",\n \"lead_id\": \"sample_upsert_lead_id\",\n \"phone_number\": \"9999999999\",\n \"custom_field2\": \"custom_value2\",\n \"custom_field1\": \"custom_value1\"\n}\n\n\n\nPlease reach out to your Squadstack POC to get the reference ID for your campaign specific endpoint
\n
This endpoint is used to mark a successful conversion for a lead in your campaign. Conversion usually refers to when the lead reaches a positive terminal state in your system, and you want to mark that outcome on Squadstack as well.
Converted leads will not be touched upon(unless manually reactivated).
It is important that we receive all conversion hits so that we can provide accurate ROI reporting to your business teams
The request body should be in raw format and include the following parameters:
\nlead_id (string,mandatory): The unique identifier of the lead that is to be converted.
\ndetail (string/JSON,mandatory): Additional details about the lead conversion. This could be specific details around the terminal stage of the lead
\nThe response to this request will have a status code of 200 and will include the following parameters:
\nlead_id (string): The unique identifier of the converted lead.
\ndetail (string/JSON): Additional details about the lead conversion.
\nSample payload:
\n{\n \"lead_id\" : \"leadid1\"\n \"detail\":\n {\n \"order_placed_at\" : \"2023-12-22 16:15:14\",\n \"ordered item\" : \"item1\",\n \"order_amount\" : \"300\"\n }\n}\n\nAn example of a successful response:
\n{\n \"lead_id\": \"sample_lead_id\",\n \"detail\": \"Lead successfully converted\"\n}\n\nStatus Codes
\n","urlObject":{"protocol":"https","path":["voice","crm-integration-v2","ref_id","lead-converted"],"host":["api","squadstack","com"],"query":[],"variable":[]}},"response":[{"id":"4a0f68e6-7b53-4cb8-8302-6e926f32565d","name":"Convert a lead","originalRequest":{"method":"POST","header":[{"key":"Authorization","value":"Bearer your_token"},{"key":"Content-Type","value":"application/json"}],"body":{"mode":"raw","raw":"{\n \"lead_id\": \"sample_lead_id\",\n \"detail\" : \"Lead successfully converted\"\n}","options":{"raw":{"language":"json"}}},"url":"https://api.squadstack.com/voice/crm-integration-v2/ref_id/lead-converted"},"status":"OK","code":200,"_postman_previewlanguage":"json","header":[{"key":"Date","value":"Thu, 18 Jan 2024 18:49:28 GMT"},{"key":"Content-Type","value":"application/json"},{"key":"Transfer-Encoding","value":"chunked"},{"key":"Connection","value":"keep-alive"},{"key":"Server","value":"nginx"},{"key":"Allow","value":"GET, POST, PATCH, HEAD, OPTIONS"},{"key":"x-xss-protection","value":"1; mode=block"},{"key":"Vary","value":"Cookie"},{"key":"x-content-type-options","value":"nosniff"},{"key":"X-Frame-Options","value":"SAMEORIGIN"},{"key":"Content-Encoding","value":"gzip"}],"cookie":[],"responseTime":null,"body":"{\n \"lead_id\": \"sample_lead_id\",\n \"detail\": \"Lead successfully converted\"\n}"}],"_postman_id":"c808c9c6-0fc2-4703-936f-550d514edb39"},{"name":"Disable a Lead","id":"d61f03a1-3558-45e6-a4e2-a14ac204a112","protocolProfileBehavior":{"disableBodyPruning":true},"request":{"method":"POST","header":[{"key":"Authorization","value":"Bearer your_token"},{"key":"Content-Type","value":"application/json"}],"body":{"mode":"raw","raw":"{\n \"lead_id\": \"sample_lead_id\"\n}","options":{"raw":{"language":"json"}}},"url":"https://api.squadstack.com/voice/crm-integration-v2/ref_id/lead-disabled","description":"\n\nPlease reach out to your Squadstack POC to get the reference ID for your campaign specific endpoint
\n
This endpoint is used to disable a lead in your campaign. Disabling a lead will stop any further activities on the lead. The lead will still be present in your campaign database, but it would not be picked for calling/messaging/IVR/any other services that you may be availing from Squadstack
\nThe response to this request will have a status code of 200 and will include a JSON object with the key \"lead_id\" and its corresponding value.
\n{\n \"lead_id\": \"sample_lead_id\"\n}\n\n\n\nPlease reach out to your Squadstack POC to get the reference ID for your campaign specific endpoint
\n
This endpoint is used to delete lead from Squadstack systems. Please note that deleting a lead will purge all information of that lead and we would not be able to recover it.
\nStatus: 200
\nlead_id: (string) The ID of the lead that was deleted.
\n{\n \"lead_id\": \"lead_id_to_be_deleted\"\n}\n\nWelcome to Squadstack API reference guide!
Here you will find documentation around all our APIs and the relevant action that each API takes.
You can find a list your campaigns here
\n\nPlease note that we provide campaign specific endpoints , and as such, you would be given a unique reference ID that would need to be substituted in your endpoint.
\n
Please reach out to your Squadstack POC or write to us at customer-integrations@squadstack.com to get your campaign specific reference IDs.
All of our endpoints can be accessed by basic authentication. You can access the token here.
\n\n\nPlease reach out to customer-integrations@squadstack.com in case you are unable to access the token
\n
Our standard rate limits are 100 requests per minute. Kindly contact customer-integrations@squadstack.com in case an increase of rate limit is needed.
\nPrerequisites for whitelisting:
\n\n\nPlease note that these are mandatory before you integrate our APIs
\n
Auth token
\n"},{"key":"Content-Type","value":"application/json"}],"body":{"mode":"raw","raw":"[\n {\n \"lead_id\": \"lead_id1\",\n \"phone_number\": \"9999999999\",\n \"contact_name\": \"John Doe\",\n \"customkey1\": \"custom value\",\n \"customkey2\": \"custom value\"\n },\n {\n \"lead_id\": \"lead_id2\",\n \"phone_number\": \"9999999999\",\n \"contact_name\": \"Jane Doe\",\n \"customkey1\": \"custom value\",\n \"customkey2\": \"custom value\"\n },\n {\n \"lead_id\": \"lead_id3\",\n \"phone_number\": \"9999999999\",\n \"contact_name\": \"Jasmine Doe\",\n \"customkey1\": \"custom value\",\n \"customkey2\": \"custom value\"\n }\n\n]","options":{"raw":{"language":"json"}}},"url":"https://api.squadstack.com/voice/crm-integration-v2/ref_id/lead-created","description":"This endpoint allows you to create leads in bulk in your campaign
\nA maximum of 100 leads per API call
\nA maximum of 100 API calls per minute across all endpoints combined
\nThe request body should be in raw format and should contain a JSON array with objects having
\nlead_id (string, required): The Unique ID of the lead.
\nphone_number (string, required): Phone number of the lead.
\ncontact_name (string, required): The name of the lead
\ncustomkey1 (string/integer): Custom metadata for the lead.
\ncustomkey2 (string/integer): Custom metadata for the lead
\n\n\nAdditional keys can be added as per business requirement. Naming conventions can be customised as needed
\n
The response for this request is a JSON object with the following properties:
\n\"status\": Indicates the status of the bulk API operation
\n\"message\": Provides additional information about the response.
\n\"result\": An array containing objects; each object represets the result of a downstream request made for a specific lead. Each object will contain the following properties:
\n\"status_code\": Status of the request against that specific lead
\n\"data\": An object containing details about the operation, which will include
\nlead_id
\nall other input keys
\nan error message in case of a failed API request
\n\"metadata\": An object providing metadata about the operation, including the total number of leads, successful operations, and failed operations.
\nAuth token
\n"},{"key":"Content-Type","value":"application/json"}],"body":{"mode":"raw","raw":"[\n {\n \"lead_id\": \"lead_id_to_be_updated1\",\n \"stage\": \"new_stage\",\n \"key_to_be_updated\": \"new_value\",\n \"new_key_to_be_added\": \"value\"\n },\n {\n \"lead_id\": \"lead_id_to_be_updated2\",\n \"stage\": \"new_stage\",\n \"key_to_be_updated\": \"new_value\",\n \"new_key_to_be_added\": \"value\"\n },\n {\n \"lead_id\": \"lead_id_to_be_updated3\",\n \"stage\": \"new_stage\",\n \"key_to_be_updated\": \"new_value\",\n \"new_key_to_be_added\": \"value\"\n }\n]","options":{"raw":{"language":"json"}}},"url":"https://api.squadstack.com/voice/crm-integration-v2/ref_id/lead-updated","description":"This endpoint allows you to make bulk updates(update multiple leads at once) to your leads in your campaign
\nA maximum of 100 leads per API call
\nA maximum of 100 API calls per minute across all endpoints combined
\nThe request body should be in raw format and should contain an array of objects with the following parameters:
\nlead_id (string,required): The ID of the lead to be updated.
stage (string): The new stage of the lead.
key_to_be_updated (string): A pre-existing key that you want to update with a new value
new_key_to_be_added (string): A new key that you want to add on to an existing lead's metadata
\n\nPlease note that the naming convention for the additional keys can be as per the business requirement/ as per the key names passed originally
\n
The response for this request is a JSON object with the following properties:
\n\"status\": Indicates the status of the bulk API operation
\n\"message\": Provides additional information about the response.
\n\"result\": An array containing objects; each object represets the result of a downstream request made for a specific lead. Each object will contain the following properties:
\n\"status_code\": Status of the request against that specific lead
\n\"data\": An object containing details about the operation, which will include
\nlead_id
\nall other input keys
\nan error message in case of a failed API request
\n\"metadata\": An object providing metadata about the operation, including the total number of leads, successful operations, and failed operations.
\nAuth token
\n"},{"key":"Content-Type","value":"application/json"}],"body":{"mode":"raw","raw":"[\n {\n \"lead_id\": \"lead_id_to_be_upserted1\",\n \"phone_number\": \"9999999999\",\n \"contact_name\": \"John Doe\",\n \"customkey1\": \"custom value\",\n \"customkey2\": \"custom value\"\n },\n {\n \"lead_id\": \"lead_id_to_be_upserted2\",\n \"phone_number\": \"9999999999\",\n \"contact_name\": \"Jane Doe\",\n \"customkey1\": \"custom value\",\n \"customkey2\": \"custom value\"\n },\n {\n \"lead_id\": \"lead_id_to_be_upserted3\",\n \"phone_number\": \"9999999999\",\n \"contact_name\": \"Jasmine Doe\",\n \"customkey1\": \"custom value\",\n \"customkey2\": \"custom value\"\n }\n\n]","options":{"raw":{"language":"json"}}},"url":"https://api.squadstack.com/voice/crm-integration-v2/ref_id/lead-upserted","description":"This endpoint is used to upsert leads in bulk into your campaign.
\nBehaviour of our upsert API:
\nIf a lead with the given Lead ID already exists in your campaign, we will merely updated the metadata with new values passed against existing keys / add new metadata for new keys that were passed (works like an update API call)
\nIf a lead with the given Lead ID does not exist in your campaign, we will create a new lead (works like a create lead API call)
\nA maximum of 100 leads per API call
\nA maximum of 100 API calls per minute across all endpoints combined
\nThe request body should be in raw format and should contain an array of objects with the following parameters:
\nlead_id (string,required): The ID of the lead.
phone_number (string,required): The phone number of the lead.
contact_name (string,required): The name of the contact.
customkey1 (string): Custom key 1 for the lead.
customkey2 (string): Custom key 2 for the lead.
The response for this request is a JSON object with the following properties:
\n\"status\": Indicates the status of the bulk API operation
\n\"message\": Provides additional information about the response.
\n\"result\": An array containing objects; each object represets the result of a downstream request made for a specific lead. Each object will contain the following properties:
\n\"status_code\": Status of the request against that specific lead
\n\"data\": An object containing details about the operation, which will include
\nlead_id
\nall other input keys
\nan error message in case of a failed API request
\n\"metadata\": An object providing metadata about the operation, including the total number of leads, successful operations, and failed operations.
\nAuth token
\n"},{"key":"Content-Type","value":"application/json"}],"body":{"mode":"raw","raw":"[\n {\n \"lead_id\": \"lead_id_to_be_converted1\",\n \"detail\": \"Lead converted successfully\"\n },\n {\n \"lead_id\": \"lead_id_to_be_converted2\",\n \"detail\": {\n \"conversion_identifier\" : \"identifier\",\n \"conversion_metric\": \"metric\",\n \"conversion_date\": \"date\"\n }\n },\n {\n \"lead_id\": \"lead_id_to_be_converted3\", \n \"detail\": {\n \"conversion_identifier\" : \"identifier\",\n \"conversion_metric\": \"metric\",\n \"conversion_date\": \"date\",\n \"conversion_type\": \"type\",\n \"conversion_units\": \"units\"\n }\n }\n]","options":{"raw":{"language":"json"}}},"url":"https://api.squadstack.com/voice/crm-integration-v2/ref_id/lead-converted","description":"This endpoint is used to convert leads in bulk in your campaign
\nA maximum of 100 leads per API call
\nA maximum of 100 API calls per minute across all endpoints combined
\nThe request body should be in raw format and should contain a JSON array with objects having :
\nlead_id (string,required): The ID of the lead.
detail (string/JSON, required): The phone number of the lead.
\nThe response for this request is a JSON object with the following properties:
\n\"status\": Indicates the status of the bulk API operation
\n\"message\": Provides additional information about the response.
\n\"result\": An array containing objects; each object represets the result of a downstream request made for a specific lead. Each object will contain the following properties:
\n\"status_code\": Status of the request against that specific lead
\n\"data\": An object containing details about the operation, which will include
\nlead_id
\nall other input keys
\nan error message in case of a failed API request
\n\"metadata\": An object providing metadata about the operation, including the total number of leads, successful operations, and failed operations.
\nAuth token
\n"},{"key":"Origin","value":"{{origin}}","description":"Your Origin
\n"},{"key":"Content-Type","value":"application/json"}],"body":{"mode":"raw","raw":"[\n {\n \"lead_id\": \"lead_id_to_be_disabled1\"\n },\n {\n \"lead_id\": \"lead_id_to_be_disabled2\"\n },\n {\n \"lead_id\": \"lead_id_to_be_disabled3\"\n }\n]","options":{"raw":{"language":"json"}}},"url":"https://api.squadstack.com/voice/crm-integration-v2/ref_id/lead-disabled","description":"This endpoint is used to disable leads in bulk in your campaign
\nA maximum of 100 leads per API call
\nA maximum of 100 API calls per minute across all endpoints combined
\nThe request body should be in raw format and contain a JSON array of objects with each object having:
\nlead_id (string,required): The ID of the lead.The response for this request is a JSON object with the following properties:
\n\"status\": Indicates the status of the bulk API operation
\n\"message\": Provides additional information about the response.
\n\"result\": An array containing objects; each object represets the result of a downstream request made for a specific lead. Each object will contain the following properties:
\n\"status_code\": Status of the request against that specific lead
\n\"data\": An object containing details about the operation, which will include
\nlead_id
\nall other input keys
\nan error message in case of a failed API request
\n\"metadata\": An object providing metadata about the operation, including the total number of leads, successful operations, and failed operations.
\nAuth token
\n"},{"key":"Content-Type","value":"application/json"}],"body":{"mode":"raw","raw":"[\n {\n \"lead_id\": \"lead_id_to_be_deleted1\"\n },\n {\n \"lead_id\": \"lead_id_to_be_deleted2\"\n },\n {\n \"lead_id\": \"lead_id_to_be_deleted3\"\n }\n]","options":{"raw":{"language":"json"}}},"url":"https://api.squadstack.com/voice/crm-integration-v2/ref_id/lead-deleted","description":"This endpoint is used to delete leads in bulk in your campaign.
\nPlease note that deleting a lead will purge all information of that lead and we would not be able to recover it.
\nA maximum of 100 leads per API call
\nA maximum of 100 API calls per minute across all endpoints combined
\nThe request body is of raw type and contains a JSON array or objects. Each object should have a key \"lead_id\" which is a string parameter.
\nThe response for this request is a JSON object with the following properties:
\n\"status\": Indicates the status of the bulk API operation
\n\"message\": Provides additional information about the response.
\n\"result\": An array containing objects; each object represets the result of a downstream request made for a specific lead. Each object will contain the following properties:
\n\"status_code\": Status of the request against that specific lead
\n\"data\": An object containing details about the operation, which will include
\nlead_id
\nall other input keys
\nan error message in case of a failed API request
\n\"metadata\": An object providing metadata about the operation, including the total number of leads, successful operations, and failed operations.
\nWelcome to Squadstack Bulk API reference guide!
Here you will find documentation around all our Bulk APIs and the relevant action that each API takes.
Some important points to note:
\nYou can find a list your campaigns here
\nPlease note that we provide campaign specific endpoints , and as such, you would be given a unique reference ID that would need to be substituted in your endpoint.
Please reach out to your Squadstack POC or write to us at customer-integrations@squadstack.com to get your campaign specific reference IDs.
All of our endpoints can be accessed by basic authentication. You can access the token here.
\n\n\nPlease reach out to customer-integrations@squadstack.com in case you are unable to access the token
\n
Our standard rate limits are 100 records per minute. Kindly contact customer-integrations@squadstack.com in case an increase of rate limit is needed.
\nWe allow 100 leads per request in our Bulk APIs
\nPrerequisites for whitelisting:
\n\n\nPlease note that these are mandatory before you integrate our APIs
\n
Generic Response for each bulk API request:
\nOn executing a bulk API request, the response for each request is a JSON object with the following properties:
\n\"status\": Indicates the status of the bulk API operation
\n\"message\": Provides additional information about the overall response.
\n\"result\": An array containing objects; each object represets the result of a downstream request made for a specific lead.
Each object will contain the following properties:
\"status_code\": Status of the request against that specific lead
\n\"data\": An object containing details about the operation, which will include
\nlead_id
\nall other input keys
\nan error message in case of a failed API request
\n\"metadata\": An object providing metadata about the operation, including the total number of leads, successful operations, and failed operations.
\n\n\n","_postman_id":"f71db816-ece3-4690-ba34-2bdfb3badc65"},{"name":"Common status codes and their meanings","item":[],"id":"263de7cc-d12c-4267-b831-795b3aa51b6e","description":"","_postman_id":"263de7cc-d12c-4267-b831-795b3aa51b6e"},{"name":"Integrating with standard CRMs","item":[{"name":"Hubspot","item":[],"id":"5bdb49c2-b75f-4b42-bb54-8e1061872ca8","description":"For errors specific to individual leads, you may refer this link
\n
Method-1 : Worfklows
\nMethod-2 : Airbyte (Hosted on Squadstack’s servers)
\nPrerequisites:
\nPros:
\nCons:
\nSetup Owner:
\nMethod 1: LAPP
\nMethod 2: Workflow
\nMethod: Webhooks
\nMethod: Airbyte (Hosted on Squadstack’s servers)
\nPrerequisites:
\nPros:
\nCons:
\nSetup Owner:
\nWe have vast experience integrating with a lot of standard CRMs. Here's how we commonly integrate with them
\n","_postman_id":"5f870728-237f-46e1-a6e5-5d487d722c92"},{"name":"Disposition updates","item":[],"id":"740cab39-a8f7-4988-989d-9daac31ad8fb","description":"A key part of integrating with us is our ability to keep your system up to date on the actions taken by Squadstack on the lead!
\nHere are the most common actions(referred to as events henceforth)
\nCall
\nWhatsapp message
\nSMS
\nJudgement
\nIVR
\nFor each of these events, there is a standard set of data that we capture along with a disposition. Depending upon your usecase, we would also be collecting script specific information from the lead.
Here's some standard data that we can send back to your system on each event:
{\n \"phone_number\": \"+91xxxxxxxxxx\",\n \"lead_id\": \"test_lead_id\",\n \"recording_url\": \"https://www.squadstack.ai/\",\n \"campaign_id\": \"{campaign_id}\",\n \"called_at\": \"2018-12-03T14:36:38+00:00\",\n \"call_outcome\": \"Connected : Objective Met\",\n \"contact_name\": \"John Doe\",\n \"created_at\": \"2018-12-03T14:36:01+00:00\",\n \"call_attempt_number\": 1\n}\n\n{\n \"phone_number\": \"+91xxxxxxxxxx\",\n \"lead_id\": \"test_lead_id\",\n \"latest_recording_url\": \"https://www.squadstack.ai/\",\n \"campaign_id\": \"{campaign_id}\",\n \"latest_called_at\": \"2018-12-03T14:36:38+00:00\",\n \"lead_outcome\": \"Payment complete\",\n \"processed_at\": \"2018-12-03T14:37:54+00:00\",\n \"contact_name\": \"John Doe\",\n \"created_at\": \"2018-12-03T14:36:01+00:00\",\n \"additional_notes\": \"additional_notes\"\n }\n\nHow do we access our API token?
\nWhat are the rate limits that you currently support?
\nHow many leads can we create in a day?
\nWhat kind of data can we get back from Squadstack after my lead is catered to?
\nHow can you send these updates to us?
\nWe want to run multiple campaigns with Squadstack, but do not wish to consume multiple API endpoints. Can we have something generic that can be reused for all campaigns?
\nIs it possible to share encrypted information through integration?
\nHave more queries?
\n