Administration
      Back to home
      1. Emitwise Academy
      2. Administration & Security
      3. Administration

      Automate data collection with integrations

      This guide outlines your options—ranging from Snowflake shares to API connections—helping you pick the best fit for your organization.

      Introduction

      Manual data entry can be time-consuming and prone to errors. Emitwise offers several integration methods so you can automatically feed your emissions-related data into the platform. This guide outlines your options—ranging from Snowflake shares to API connections—helping you pick the best fit for your organization.

      How to

      If you are interested in integrations, we recommend setting a call with your IT team to discuss the options together and review the data in question.

      Options available

      1. Snowflake Database Integration

        Best if you store relevant data in Snowflake.

        • We begin with a meeting to review your data schema and confirm you have all the necessary data for accurate emissions calculations.
        • Set up a dedicated table or view in Snowflake that contains the required data for emissions analysis.
        • Emitwise will provide Snowflake account details hosted in either Azure US East2 or AWS EU West1.
        • Your team will share the Snowflake data with Emitwise's account by creating a data share. This process typically takes no more than one business day.
        • Emitwise will verify that the shared data is accessible and accurate.

        Example: one of our biggest clients has set up a Snowflake integration between their database and Emitwise to pull their procurement listing every month and automatically calculate their Scope 3 emissions.

        78

      2. API Integration

        Works with any system or database.

        • We begin with a meeting to review your data schema and confirm you have all the necessary data for accurate emissions calculations.
        • Emitwise gives you access to an API key management settings page.
        • Your team references our API documentation to build a simple backend service to transform and send the data to Emitwise’s API. This should take them less than a week.
        • The data is automatically processed and emissions are instantly calculated and visible in your Analyse page.

        Example Use Case: Real-time updates from your custom internal tools.

        79

      3. SFTP Integration

        Ideal for uploading CSV or similar files automatically—especially from on-premise systems like SAP. Easier to setup than an API integration.

        • We begin with a meeting to review your data schema and confirm you have all the necessary data for accurate emissions calculations.
        • Emitwise sets up an SFTP server: we can either use yours or create one for you
        • You schedule a process to export data (e.g., monthly) and upload it to the SFTP server as CSV file.
        • Emitwise automatically processes the file and the emissions are visible in Analyse.

        Example: one of our client has set up an SFTP integration to automatically export waste and water data from their SAP on-premise system every month.

      4. Utilities Integration

        Handles data directly from any of your utility providers. Powered by a partner service (Nectar) at an additional cost.

        • You share your utility provide authentication details with Nectar
        • Nectar logs in to your utility accounts to fetch usage data and uploads it to Emitwise on your behalf.

        Example Use Case: Gathering electricity or gas consumption data without manual input.

      Conclusion

      With the right integration, data automatically flows into Emitwise, saving you time and ensuring more accurate carbon reporting. If you also want to send data out of Emitwise (e.g., to your BI tools), see our Integrations for Data Export article.