Integrations
Here you connect goPrevina with the tools your company already uses: e-signature, Slack or Teams, Telegram for notifications, calendars, Google Drive, SharePoint, file exchange and, in the advanced part, corporate sign-in.
1. What is on the screen
At the top, the “Integrations” title and the “Single sign-on settings” link. Below, a search box and a category selector (“All”, “Digital Signatures”, “Collaboration”, “Messaging”, “Calendar”, “Identity & SSO”, “HR & People”, “File Storage”…) that filter the catalogue, and four counters: “Active”, “Disabled”, “With Errors” and “Available”.
In “Available integrations” each card says what the integration does and its state (“Not Configured” until you set it up), with the “Configure” and “Documentation” buttons.
2. Configure an integration
1. Press “Configure” on its card: its configuration page opens.
2. In “Basic Configuration” enter an “Integration Name” and the “Environment” (“Production”, “Sandbox” or “Development”).
3. In “Credentials” paste the data the other service gives you; each field explains below where it comes from.
4. Press “Save Configuration” and then “Test Connection”: if the test passes, the integration becomes “Active” and counts under “Active”; if it fails, it counts under “With Errors”.
“View Documentation” opens the step-by-step guide for that integration (Telegram and WhatsApp have their own).
3. Test, enable, disable and delete
Once configured, the card's button becomes “Settings” and, when you move the cursor over the card, four icon buttons appear: “Test” (checks the connection again), “Enable” or “Disable”, and “Delete”, which asks for confirmation. “Enable” does not work until the connection test has passed: until it is verified, the integration sends nothing.
4. Notifications by WhatsApp or Telegram
Telegram is the quickest route: you only need to create a bot in @BotFather. The WhatsApp card has its “Configure” button: it needs a Meta Business account and approved templates, and the guide explains it step by step.
Configuring Telegram here does not send anything yet: each user has to switch the channel on in their “Notification preferences” and press “Connect Telegram”.
5. Corporate sign-in and who uses this screen
“Show advanced integrations (4)” opens corporate sign-in and people sync: “Single sign-on (OIDC)” and “Single sign-on (SAML 2.0)” to sign in with Azure AD, Okta or Google Workspace, “User provisioning (SCIM 2.0)” so your identity provider creates and deactivates users, and “BambooHR” to bring in employees. The “Single sign-on settings” link opens the screen with several identity providers, SSO-only access, two-step verification and the mapping of groups to roles.
This is an administration screen. API keys, webhooks, data sync and integration monitoring are in the side menu, under Administration › System.