Hey Biginners,

In our last post, we discussed what toppings are, why they're essential to extending Bigin's capabilities, and how the Bigin Developer Center serves as the starting point for building them. As a cloud platform, the Developer Center empowers developers with a dedicated space exclusively for creating and managing toppings, as well as publishing them to the Bigin Marketplace. Once they create their topping drafts in the Bigin Developer Center, developers can enter the Bigin Developer Console, which is where the actual development takes place.

The Developer Console provides all the resources needed for the entire development journey, from creating and automating to testing toppings before they go live. By using these features, you can create a unique topping that perfectly bridges the gap between Bigin and user-specific needs.

When building a topping, you can include custom components from the Bigin Developer Console. These components range from simple fields to related lists that enable easier navigation through Bigin's user interface.

You can add custom fields in addition to the standard fields available in Bigin to handle your topping requirements. Using custom buttons and links can streamline actions in Bigin or integrate Bigin data with external URLs, applications, or systems. To establish a direct relationship between the records inside Bigin, you can use related lists.

For a step-by-step implementation guide to creating these custom components, please refer to the following links:

Next, let's explore the Bigin Developer Console's automation features and incorporate them to adding more functionalities to your topping.

The Bigin Developer Console offers features that automate repetitive tasks, simplify processes, reduce manual effort, and enhance user efficiency. You can incorporate automation features like workflows, schedules, functions, signals, and more.

A developer creating a topping to improve pipeline management in Bigin might seek to automate repetitive tasks, such as managing stages and assigning responsibilities. For instance, when a new deal enters the "Inquiry" stage in the Sales pipeline, the system promptly assigns it to an appropriate sales rep through an automatic owner assignment rule, which eliminates the need for manual intervention. Likewise, you can set a schedule to send automated email reminders to prospects who haven't responded within a week and define a signal that notifies users in real time when a recipient opens an email.

To learn more about how to implement these automation features in your toppings, check out our detailed implementation guide here. Alongside our automation features, we also enable developers to create custom functions using Deluge scripts.

The Bigin Developer Console enables developers to create custom functions using Zoho's Deluge scripting language. These functions serve to implement business-specific logic in toppings, and are invoked by other functions or components. They eliminate the need for manual repetitive tasks by enabling developers to define specific functions once and invoke them as needed.

Custom functions are categorized into two types: standalone functions and REST API functions.

Standalone functions are self-contained blocks of code that can be invoked from any part of the topping. They can also be invoked from other functions, which enables modular and reusable scripting. On the other hand, Bigin's REST API functions allow developers to expose Deluge code as an API endpoint, enabling external applications to invoke the custom logic hosted in the topping.

For a comprehensive understanding of custom functions, their types, and how to implement them, please refer to our Functions Guide.

While these features enhance the utilities of toppings and improve Bigin's native functionalities, there's another kind of feature that helps expand Bigin's capabilities by integrating it with other applications.

One sort of topping you may want to build is a connection that transfers data between Bigin and a third-party service. Connections simplify this integration process, ensuring seamless data exchange between applications. Once a connection is established, you can access authenticated data.

Preconfigured default services are available when you're creating a connection. For these services, developers only need to provide the connection details, select the necessary scopes from the available list, and establish the connection. If their preferred services aren't preconfigured, developers can create custom connections by providing service details and authentication credentials. In this case, understanding the authentication and authorization protocols these third-party applications follow is essential for successful integrations.

Consider a scenario in which a sales team wants to notify customers about the sales process by sending instant message notifications via Twilio. For example, when a deal advances to the Proposal Sent stage, Bigin can trigger an SMS notification via Twilio to provide the customer with proposal details. Similarly, when the deal status changes to Closed-Won, the system automatically sends a confirmation message from Bigin to update the customer about the deal's successful closure.

To implement this functionality, developers can create a connector to integrate Bigin with Twilio, as well as to include the logic necessary for sending the message. Also, by incorporating Bigin automation features like workflows, developers can set up triggers that execute functions when certain conditions are met. This streamlines communication, enhances customer satisfaction, and keeps customers informed throughout the sales process. For more information on creating and managing connections, please refer to our detailed guide.

While connections handle backend integrations to enable data exchange between Bigin and other applications, connected apps comes into play when you need an interactive way to engage with both internal data and data from external applications directly within the Bigin interface.

Let's see how Bigin's connected app functionality facilitates this interaction!

A connected app enables an external application to integrate with Bigin through an interface, which is a widget that enhances Bigin's functionality and provides users with a seamless experience in Bigin. You can design your own UI interface and have complete control over the widget.

For example, sales teams often need customers to sign contracts or agreements before closing deals. With a connected app, you can embed an e-signature widget like Zoho Sign directly into Bigin. This enables users to send documents for signatures, track their statuses, and receive signed copies—all without leaving Bigin.

Read here to learn how to build a connected app, create a widget, and embed it into Bigin's UI.

Once you've built all the custom components you need for your topping, you can test it out inside the Bigin Developer Center itself. Let's explore how!

Testing ensures that the topping is working as expected, and is important to do before publishing. The Bigin Developer Console provides a sandbox environment wherein you can thoroughly test all your customization components, connections, widgets, and workflows.

Once testing is complete, you can publish the topping through either of the following methods:

In the next post, we'll explore testing and publishing in detail and implement real-time use cases.

Stay tuned!