A brief guide to integrating your software tools with a Betty Blocks application.
As a developer, you’re likely looking for ways to enhance your software tool without getting bogged down in lengthy learning paths. Betty Blocks offers a powerful platform that allows you to augment your software package quickly and effectively. This guide will walk you through the essential steps to start the integration process. But first, let’s briefly walk you through the baseline of Betty Blocks.
How does Betty Blocks work?
The platform is built on three main pillars: Pages, Models, and Actions, which together form the foundation of application development on the platform. These pillars are complemented by additional features like the Block Store and various Tools, which enhance and extend the platform’s capabilities.
Pages are where you design the user interface of your application. With a drag-and-drop interface, you can easily construct layouts, add navigation elements, incorporate data components, and create forms or buttons. You can start with a blank canvas or use pre-defined templates, to build and preview the front end using Pages.
Models serve as the backbone for managing and organizing data within your application. Models can be linked through relations, such as connecting ‘Customers’ with ‘Orders’. Betty Blocks also supports schema models for temporary data organization and remote models for integrating external data sources like broadening the scope of your application’s functionality.
Actions are used to define the logic that drives your application. These are event-driven workflows that are visually constructed within the platform. Actions can be triggered by user interactions, such as button clicks, and are built using action steps (functions) defining the events' sequence. Actions allow you to create complex application logic and workflows.
Block Store is a repository of reusable blocks: data sources, page components and action steps that can be easily integrated into your application. The store also offers pre-built application themes and page-sharing functionality. Tools contain additional features like translation utility, logs, public file storage, authentication options, etc.
Augmenting your software
One of the most powerful features of Betty Blocks is its ability to integrate with any external data sources and APIs. This capability allows your application to interact with external systems, retrieve or push data, and extend its functionality beyond what is available within the platform.
Betty Blocks’ augmented strategy enables enterprise strategic partners and vendors to enrich their ecosystem by offering a platform that fills gaps in their infrastructure. The first step in augmenting your software package is understanding the integration process with Betty Blocks.
What is needed?
Everything begins with understanding your current system and its architecture. This process typically involves identifying the areas where they want to augment functionality. Set clear objectives such as improved data management, user experience, optimized processes, etc. Then you need the following:
-
Access to external APIs or data sources: If you plan to integrate external data, you need access credentials, API keys, or endpoint information for the services you wish to connect to (e.g., databases, and third-party APIs like Salesforce or SAP).
-
Environments: if an external API provides a test or acceptance environment, you should configure and use it in your sandbox environment.
Betty Blocks integration toolkit
The integration process typically begins with the HTTP(s) action step. It is used to pull data into the application. This data can then be directed into either a schema model or a remote model, depending on how it needs to be processed and displayed within the application.
Schema models can handle both remote and local data, functioning as temporary data structure units within an action. They allow you to organize and format incoming data (by giving the structure to JSON objects), making it easier to use in your workflows. Although they are temporary, schema models still contain properties used to manipulate the data during an action’s execution.
Remote models are ideal for data that comes with pre-defined formatting and logic, as these models integrate external data directly into the application for immediate use. Each remote model has a default set of properties and generated actions within it. Though data remains hosted outside the Betty Blocks environment, it is fully accessible and usable within the application.
1. HTTP(s) action step: enables API calls to your system directly from within your Betty Blocks application for real-time data exchange and process triggering. The HTTP(s) action step can be automated to trigger based on specific conditions or schedules. This means your application can automatically sync data, execute processes, or update external systems without manual intervention
-
Configure the HTTP(s) step by specifying the API endpoint, request method (GET, POST, etc.), and any necessary headers or body content.
Follow the process of common API setup in Configurations.
2. Data source setup includes two flows:
-
The builder creates a custom data source. The supported API specification is OpenAPI (also known as Swagger)
-
Installation of an available data source from Block Store, like Google Sheets or Microsoft Teams APIs
3. Remote models function just as native data models but pull data from external data sources created or installed into your application. Then you can map remote models (with generated properties) to your application’s data models.
Branding and styling
Brand your Betty Blocks application to match your current environment with a range of features to help you align your application’s look with your brand’s identity.
Color schemes
Theme builder in Tools section helps to define and apply primary, secondary, and accent colors across your application. These colors should be used consistently for backgrounds, text, buttons, and other design elements. Read more in Color use: best practices.
Fonts and typography
Our also Theme builder offers options to select fonts and apply them consistently across your application. You can upload custom fonts to match your brand’s style and control text properties such as size, weight, and color.
Using partials
Partials are reusable interface elements like navigation bars or footers. They can be styled centrally, and any updates will automatically reflect wherever they are used in your application.
Button styles and icons
Buttons and icons are interactive elements that should reflect your brand’s identity. In Betty Blocks, button styles can be configured globally through the Theme builder or customized individually via Pages. This includes setting button colors, shapes, sizes, etc.
CSS styles
For developers seeking more precise control over styling, Betty Blocks allows the addition of custom CSS properties. This feature is particularly useful for implementing advanced styling rules that go beyond the default options.
Responsive design
Your application’s layout, navigation, and other elements will adjust to different screen sizes. The page builder includes tools to preview and tweak the design for various devices, ensuring that your branding and styling remain intact on desktops, tablets, and smartphones.
Reusability and public files
As already mentioned, Betty Blocks offers various features that allow you to reuse components and other entities across different projects, saving time and resources. Additionally, public files, like your company’s logo, can be stored and reused across your application.
Read more about branding your applications in Styling best practices.
Security measures
Security is a top priority in any development project. This section outlines what Betty Blocks offers in terms of security and how you can implement it in your projects. Refer to our security FAQ document for more details.
Betty Blocks has solid access controls to ensure that only authorized users can access or modify data. Besides native authentication methods, the platform integrates OAuth and Single Sign-On (SSO) protocols for secure user authentication using existing credentials.
Additionally, role-based access control allows administrators to define precise access levels for different user roles, ensuring users can only access data relevant to their responsibilities. Multi-factor authentication is also available for an added layer of security.
Data security
Betty Blocks ensures data protection through comprehensive encryption protocols. Data at rest is encrypted using industry-standard algorithms, while data in transit is secured with transport layer security (TLS) or secure sockets layer (SSL), preventing unauthorized access during data transmission. Token-based authentication is used for authenticated API requests, managing data access via secure tokens.
Each Betty Blocks application operates with two separate databases: one for application configuration and another for actual data storage. This structure ensures that databases are never shared between applications, enhancing security.
User provisioning and governance
Managing users and establishing proper governance is essential for maintaining control over your application. Betty Blocks offers simple user provisioning - a solution that ensures that user accounts are automatically created, given proper permissions, updated, and have their access revoked to the platform.
Using My Betty Blocks space allows managing permissions on different levels: company, organizational and application.
Final remarks
Augmenting your application with Betty Blocks is a structured process that starts with a clear understanding of your current system and specific integration needs. Then using remote models and the HTTP(s) action step, you can integrate any external data and automate workflows, boosting your application’s capabilities. Begin by setting up the necessary data connections, building out your workflows, and iterating based on testing and feedback.