Developer portal
Welcome to Sweet’s developer portal, where you can find resources like Sweet’s API documentation, integrations, frequently asked questions and answers, and other useful documentation. Sweet right?
Sweet CRM API
Learn more about how you can use the Sweet CRM REST API for your integrations in the API documentation.
Sweet Forms API
Discover more about utilizing the Sweet Forms REST API for your integrations in the Sweet Forms API documentation.
Sweet Automation API
Learn more about how you can use the Sweet Automation REST API for your integrations. To access the documentation, open your Sweet Automation environment, copy the URL, and append the extension “Api/swagger” at the end to proceed to Swagger and the documentation. Or find it here
Sweet manual
Read more about the features of the Sweet platform in our user manuals. Here, you can step-by-step learn how to use the platform, adjust settings, add integrations, and more on your own.
Q&A
How does Sweet ensure that information security is high?
At Sweet, we prioritize the security of your data, and we are proud to be ISO 27001 certified in “Information Security Management.” With our well-established processes, we ensure that your data is always handled and managed securely, and we are audited annually by an external party to maintain our certification.
The work with information security involves having clear guidelines and processes for:
– Development of new features with internal testing and external penetration testing
– Selection of technology for our platform
– Management of customer data, only relevant information is stored
– Development of customer solutions, only necessary individuals have access
– Access to code, only necessary individuals have access
– Access to customer data, only necessary individuals have access
– Incident management
– Monitoring and error handling
– Availability/uptime
– Ongoing training in information security threats
– Training in incident management
The work with information security involves having clear guidelines and processes for:
– Development of new features with internal testing and external penetration testing
– Selection of technology for our platform
– Management of customer data, only relevant information is stored
– Development of customer solutions, only necessary individuals have access
– Access to code, only necessary individuals have access
– Access to customer data, only necessary individuals have access
– Incident management
– Monitoring and error handling
– Availability/uptime
– Ongoing training in information security threats
– Training in incident management
What types of integrations can you do in Sweet?
Sweet enables various types of integrations to suit different needs and infrastructures. Sweet Automation acts as the integration engine and is often used to create customized integrations between Sweet platforms, including Sweet CRM, Sweet Forms, Sweet Performance, and Sweet Automation. This also includes connections to the client’s own systems or other external solutions. Here are some types of integrations that can be done in Sweet:
– API Integrations: Connect to the Sweet platform using APIs to send and retrieve data. This provides flexibility and the ability to tailor integration flows to specific requirements.
– Direct to Database or Datamart: The ability to integrate directly with databases or datamarts provides an efficient and fast link between systems, facilitating data exchange.
– FTP or SFTP Integrations: File Transfer Protocol (FTP) or Secure File Transfer Protocol (SFTP) can be used to transfer files between Sweet and other systems, which is useful for batch transfers.
– Message Queues: Integration through message queues enables asynchronous communication between systems, useful for handling large data volumes and improving performance.
We always aim to be at the forefront of integration possibilities to make automation and digitization easy. Therefore, we continuously develop new integrations for our standard offering. You can read about our standard integrations under Platform/Integrations.
– API Integrations: Connect to the Sweet platform using APIs to send and retrieve data. This provides flexibility and the ability to tailor integration flows to specific requirements.
– Direct to Database or Datamart: The ability to integrate directly with databases or datamarts provides an efficient and fast link between systems, facilitating data exchange.
– FTP or SFTP Integrations: File Transfer Protocol (FTP) or Secure File Transfer Protocol (SFTP) can be used to transfer files between Sweet and other systems, which is useful for batch transfers.
– Message Queues: Integration through message queues enables asynchronous communication between systems, useful for handling large data volumes and improving performance.
We always aim to be at the forefront of integration possibilities to make automation and digitization easy. Therefore, we continuously develop new integrations for our standard offering. You can read about our standard integrations under Platform/Integrations.
What authentication methods are supported in Sweet?
Sweet supports various authentication methods, including two-step verification:
– Sweet’s own authentication with username and password
– Synkzone
– Microsoft Azure AD
– OpenID
– Google
– Sweet’s own authentication with username and password
– Synkzone
– Microsoft Azure AD
– OpenID
Sweet CRM
What types of API calls can you do in Sweet CRM?
You can make the following API calls with Sweet CRM’s API:
GET: Used to retrieve information from an entity in the platform.
POST: Used to send data and request the creation of an entity in the platform.
PUT: Used to update an existing entity in the platform with new information.
DELETE: Used to request the removal of a specific entity from the server.
Find the API doucumentation furter up on the page.
GET: Used to retrieve information from an entity in the platform.
POST: Used to send data and request the creation of an entity in the platform.
PUT: Used to update an existing entity in the platform with new information.
DELETE: Used to request the removal of a specific entity from the server.
Find the API doucumentation furter up on the page.
How do you store data in Sweet CRM?
Sweet CRM is primarily a web platform built on cloud storage in Microsoft Azure. You can choose a completely individual and private cloud or a shared cloud with separation between instances. Sweet also offers on-premise installation on your own servers for self-storage. If you want an additional layer of security for highly sensitive data, we have a partnership with the Swedish storage company Synkzone and together can provide cryptographically separated storage in different zones, governed by permissions.
Sweet Automation
What types of API calls can you do in Sweet Automation?
You can make the following API calls with Sweet Automation’s API:
– GET: Used to retrieve information from an entity in the platform.
– POST: Used to send data and request the creation of an entity in the platform.
– PUT: Used to update an existing entity in the platform with new information.
– DELETE: Used to request the removal of a specific entity from the server.
– GET: Used to retrieve information from an entity in the platform.
– POST: Used to send data and request the creation of an entity in the platform.
– PUT: Used to update an existing entity in the platform with new information.
– DELETE: Used to request the removal of a specific entity from the server.
What is the setup model for Sweet Automation?
Sweet Automation is primarily a digital platform available in the cloud via Microsoft Azure, either in a shared or private cloud. It’s also possible to install Sweet Automation locally if desired.
How do you store data in Sweet Automation?
Sweet Automation is a digital platform designed to automate business processes. It focuses its capabilities on two core functionalities: Selections for lists, filtering, and segmentation, and Flows for building rules, chains of actions, integration, and automation.
Selections
Metadata for Selections
The selection engine stores metadata about data sources within the platform, including names and descriptions of tables and columns in a relational database, paths, filenames, and file types for files stored either on network shares or online, and API endpoints. Sensitive metadata, such as connection strings and authentication credentials, is encrypted for security. Only administrators with necessary permissions can access the metadata for selections.
Selection Templates
Using the stored metadata, users can craft selection templates. Upon execution, these templates extract data from the data source, logging details like user access, time of extraction, exact database query details, and the number of data rows returned. Selections may be locked to prevent changes by other users or administrators. All selection templates and data extraction logs are accessible to all users.
Flows
Users of the system can create flows that execute actions. These actions can perform a variety of tasks, such as sending or retrieving emails, exporting or reading a file, updating a database, making API calls, etc. Sweet Automation needs to retain specific data to keep track of ongoing processes. This data could be unique IDs like CaseId, AccountId, CustomerId, or anything else that uniquely identifies the “object being processed in the flow,” referred to as the “flow participant.”
Users can choose where to store flow-related data:
– Within the platform.
– In any relational database table outside of the platform.
Depending on the nature of the data, the user can decide which storage fits best per flow.
Logging
Every run within a flow is logged, capturing details like:
– User scheduling the run.
– Start and end dates of the run.
– Affected rows in the run.
– Exact configuration of the action at the time of the run.
If any selection templates were used within the run, that is logged according to the specification above. Flows may be locked to prevent changes by other users or administrators. Flows can be configured to run in “test mode” where selected actions are skipped. All flows and run logs can be accessed by all users in the system.
Files Uploaded in Flows
Users have the option to upload files into Sweet Automation that might be needed for a specific flow. These files are stored within the platform and can be accessed by all users in the system.
Selections
Metadata for Selections
The selection engine stores metadata about data sources within the platform, including names and descriptions of tables and columns in a relational database, paths, filenames, and file types for files stored either on network shares or online, and API endpoints. Sensitive metadata, such as connection strings and authentication credentials, is encrypted for security. Only administrators with necessary permissions can access the metadata for selections.
Selection Templates
Using the stored metadata, users can craft selection templates. Upon execution, these templates extract data from the data source, logging details like user access, time of extraction, exact database query details, and the number of data rows returned. Selections may be locked to prevent changes by other users or administrators. All selection templates and data extraction logs are accessible to all users.
Flows
Users of the system can create flows that execute actions. These actions can perform a variety of tasks, such as sending or retrieving emails, exporting or reading a file, updating a database, making API calls, etc. Sweet Automation needs to retain specific data to keep track of ongoing processes. This data could be unique IDs like CaseId, AccountId, CustomerId, or anything else that uniquely identifies the “object being processed in the flow,” referred to as the “flow participant.”
Users can choose where to store flow-related data:
– Within the platform.
– In any relational database table outside of the platform.
Depending on the nature of the data, the user can decide which storage fits best per flow.
Logging
Every run within a flow is logged, capturing details like:
– User scheduling the run.
– Start and end dates of the run.
– Affected rows in the run.
– Exact configuration of the action at the time of the run.
If any selection templates were used within the run, that is logged according to the specification above. Flows may be locked to prevent changes by other users or administrators. Flows can be configured to run in “test mode” where selected actions are skipped. All flows and run logs can be accessed by all users in the system.
Files Uploaded in Flows
Users have the option to upload files into Sweet Automation that might be needed for a specific flow. These files are stored within the platform and can be accessed by all users in the system.
What types of integrations can you do in Sweet Automation?
Sweet enables various types of integrations to suit different needs and infrastructures. Sweet Automation serves as the integration engine and is often used to create customized integrations between Sweet platforms, including Sweet CRM, Sweet Forms, Sweet Performance, and Sweet Automation. This also includes connections to the customer’s own systems or other external solutions. Here are some types of integrations that can be done in Sweet:
– API Integrations: Connect to the Sweet platform using APIs to send and retrieve data. This provides flexibility and the ability to customize integration flows according to specific requirements.
– Direct to Database or Datamart: The ability to integrate directly with databases or datamarts provides an efficient and fast link between systems, facilitating data exchange.
– FTP or SFTP Integrations: File Transfer Protocol (FTP) or Secure File Transfer Protocol (SFTP) can be used to transfer files between Sweet and other systems, useful for batch transfers.
– Message Queues: Integration through message queues enables asynchronous communication between systems, useful for handling large data volumes and improving performance.
We always strive to be at the forefront of integration possibilities to make automation and digitization easy. Therefore, we continuously develop new integrations for our standard offerings. You can read about our standard integrations under Platform/ Integrations.
– API Integrations: Connect to the Sweet platform using APIs to send and retrieve data. This provides flexibility and the ability to customize integration flows according to specific requirements.
– Direct to Database or Datamart: The ability to integrate directly with databases or datamarts provides an efficient and fast link between systems, facilitating data exchange.
– FTP or SFTP Integrations: File Transfer Protocol (FTP) or Secure File Transfer Protocol (SFTP) can be used to transfer files between Sweet and other systems, useful for batch transfers.
– Message Queues: Integration through message queues enables asynchronous communication between systems, useful for handling large data volumes and improving performance.
We always strive to be at the forefront of integration possibilities to make automation and digitization easy. Therefore, we continuously develop new integrations for our standard offerings. You can read about our standard integrations under Platform/ Integrations.
Are there any standard integrations?
Yes, Sweet has a range of standard integrations that are continuously developed, see all of them here. In addition to existing integrations, it is possible to build integrations to/from Sweet via API, directly to the database or datamart, through FTP or SFTP, as well as through message queues. You can read about our standard integrations under Platform/ Integrations.
Sweet Forms
What types of API calls can you do in Sweet Forms?
You can make the following API calls with Sweet Forms API, and the call can apply to the form or incoming responses to the form:
– GET: Used to retrieve information from a form or a set of responses.
– POST: Used to send data and request the creation of a response set in the platform.
– PUT: Used to update an existing response set with new information.
– DELETE: Used to request the removal of a specific response set from the server.
How are the answers, files, and forms stored in Sweet Forms?
Storage is determined by where and how the solution is set up. Sweet Forms is a digital platform with a cloud-based storage strategy, but we can assist you in installing it locally if needed.
You can choose to set up Sweet Forms in:
Azure Cloud, either shared or separate cloud
On-premise
Form Templates
Form templates are stored within the platform, based on the chosen configuration and storage model, and can be accessed by form administrators (form designers) in the form solution. Published forms are made available as needed, for internal or external use, with or without authentication.
Form Responses
Responses can be stored in two different ways: either in a database or as a file.
Database: Responses are stored in Azure Cloud (or your own database) and can be accessed by system administrators and, if desired, users. It is possible to change access control settings, from limited to fully accessible responses. Form responses can, for example, be limited to only being accessible to form designers or by using the link to the response for a certain period.
File: File storage enables storage outside Sweet, for example, through an external storage provider or another file area.
Files Uploaded to the Form
Files attached/uploaded to forms can be accessed by administrators and users through the “Selection” menu.
Digitally Signed Documents
When using an external e-signing provider, they store the final and signed version of the form in their e-signing platform. We can also provide the signed PDF from the signing provider in Sweet via integration.
External Storage
If your data is very sensitive, we suggest storing it in your own database or in a cloud storage provider with your desired level of security. We collaborate closely with our partner Synkzone, who are experts in storing sensitive files, documents, or forms with strict user access controls divided into encrypted zones.
You can choose to set up Sweet Forms in:
Azure Cloud, either shared or separate cloud
On-premise
Form Templates
Form templates are stored within the platform, based on the chosen configuration and storage model, and can be accessed by form administrators (form designers) in the form solution. Published forms are made available as needed, for internal or external use, with or without authentication.
Form Responses
Responses can be stored in two different ways: either in a database or as a file.
Database: Responses are stored in Azure Cloud (or your own database) and can be accessed by system administrators and, if desired, users. It is possible to change access control settings, from limited to fully accessible responses. Form responses can, for example, be limited to only being accessible to form designers or by using the link to the response for a certain period.
File: File storage enables storage outside Sweet, for example, through an external storage provider or another file area.
Files Uploaded to the Form
Files attached/uploaded to forms can be accessed by administrators and users through the “Selection” menu.
Digitally Signed Documents
When using an external e-signing provider, they store the final and signed version of the form in their e-signing platform. We can also provide the signed PDF from the signing provider in Sweet via integration.
External Storage
If your data is very sensitive, we suggest storing it in your own database or in a cloud storage provider with your desired level of security. We collaborate closely with our partner Synkzone, who are experts in storing sensitive files, documents, or forms with strict user access controls divided into encrypted zones.
