How to Push Tenders-SA Data to Your CRM: A Practical Guide

Many South African businesses that actively pursue government tenders manage their opportunity pipeline and supplier records in a Customer Relationship Management (CRM) system. The challenge has always been getting procurement data into that system efficiently. Manually copying tender details from a website into your CRM is time-consuming and error-prone.

Tenders-SA provides a CRM integration feature that pushes procurement data from the platform directly into your CRM. This guide walks through the setup process and explains what the integration can and cannot do.

Understanding the CRM Integration

The Tenders-SA CRM integration is a push-only data connector. It sends procurement records from Tenders-SA to your external CRM system. It does not pull data from your CRM back into Tenders-SA, nor does it maintain a continuous synchronisation between the two systems. Each push is a one-time data transfer triggered manually from the Tenders-SA dashboard.

The integration is available on the Professional and Enterprise subscription plans. Two providers are currently implemented: monday.com via its GraphQL API v2, and a Generic Webhook that can connect to any system that accepts JSON payloads over HTTPS.

Supported Datasets

Five datasets are available for CRM export. Each dataset contains a specific set of fields:

Step 1: Create a CRM Connection

Navigate to your Dashboard, open Settings, and select the Integrations tab. The CRM Integration section lists your current connections and a button to add a new one.

When adding a connection, select your provider. For monday.com, you will need your monday.com API v2 token, which you can generate from your monday.com account under Admin > API. Paste the token into the field and click Connect. Tenders-SA tests the connection live by making a validation request to the monday.com API.

For the Generic Webhook, you need to provide the HTTPS URL where you want the data delivered. You can optionally configure an HMAC signing secret. If provided, Tenders-SA will sign each payload with a X-TendersSA-Signature header containing sha256= followed by the HMAC hash, allowing your receiving system to verify the payload came from Tenders-SA.

Credentials are encrypted at rest using AES-256-GCM encryption before being stored in the database.

Step 2: Configure Field Mapping

Once connected, you need to map the Tenders-SA data fields to the corresponding fields in your CRM. This is done per dataset using the field mapping editor.

For monday.com, the editor shows your board columns and lets you assign each Tenders-SA field to the appropriate column. One field must be designated as the item name (the title that appears in the monday.com board). The mapping is saved per connection per dataset, so you only need to configure it once.

For the webhook adapter, the default mapping uses identity mapping, meaning field names are preserved as-is in the JSON payload. You can customise the mapping if your receiving system expects different field names.

Step 3: Push Data to Your CRM

With the connection and field mapping configured, return to the Export Configurator in the Dashboard Exports section. Select the dataset you want to push (for example, Active Tenders), apply any filters such as province or category to narrow the results, and switch the mode toggle from Download file to Send to CRM.

Select your configured CRM connection, review the field mapping preview, and click Send to CRM. The system pushes up to 500 records per operation. The sync job status is tracked through PENDING, PROCESSING, and COMPLETED or FAILED states.

Using the Webhook with Automation Platforms

The Generic Webhook adapter functions as a universal bridge to platforms such as Zapier, Make (formerly Integromat), n8n, and other automation tools. You can configure a webhook trigger in your automation platform, paste the webhook URL into the Tenders-SA connection settings, and route the incoming data to any destination your automation platform supports, including HubSpot, Salesforce, Pipedrive, Zoho, Google Sheets, or email notifications.

This approach effectively extends the CRM integration to any system that an automation platform can reach, even though Tenders-SA does not have a native adapter for that system. The HMAC signing option provides payload verification so your automation platform can confirm the data originated from Tenders-SA.

Limitations and Practical Considerations

The CRM integration is designed for occasional, manual data pushes rather than continuous sync. The 500-record limit per operation is appropriate for focused data exports but may require multiple operations for larger datasets.

The integration is push-only. It does not synchronise changes from your CRM back to Tenders-SA. If you update a record in your CRM after pushing it from Tenders-SA, the next push will create a new record or update based on your CRM's duplicate detection logic.

As of July 2026, only monday.com and Generic Webhook are implemented. HubSpot, Pipedrive, Zoho, and Salesforce are listed as coming soon in the adapter registry but do not yet have functional adapters.

Summary

The Tenders-SA CRM integration moves procurement data from the platform into your existing CRM workflows without manual data entry. Configure a monday.com or webhook connection, map your fields once, and push filtered datasets on demand from the Export Configurator. Start in your Dashboard at /dashboard under Settings > Integrations > CRM Integration.