1. Add your C2S access
- In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the C2S option from the list of connectors.
-
Click Next and you’ll be prompted to add your access.
- API Token: an integration token generated inside C2S. In the C2S web app, go to Integrações -> Informações de integração por e-mail e API and click Gerar Token. The token is shown only once, so copy it right away and store it securely. For more information, check the official C2S API guide.
- Start Date (advanced): earliest record date to sync for the incremental leads stream. When empty, all history is synced.
- Click Next.
2. Select your C2S streams
-
The next step is letting us know which streams you want to bring. You can select entire groups of streams or only a subset of them.
Tip: The stream can be found more easily by typing its name.
If you don’t see a stream you were expecting to find, feel free to get in touch and we’ll help you out!
- Click Next.
3. Configure your C2S data streams
- Customize how you want your data to appear in your catalog. Select a name for each table (which will contain the fetched data) and the type of sync.
- Layer: companies in the Growth plan can choose in which layer the tables with the extracted data will be placed.
- Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
- Sync Type: depending on the data you are bringing to the lake, you can choose between INCREMENTAL and FULL_TABLE. Read more about Sync Types here.
- Click Next.
4. Configure your C2S data source
- Describe your data source for easy identification within your organization. You can inform things like what data it brings, to which team it belongs, etc.
- To define your Trigger, consider how often you want data to be extracted from this source. This decision usually depends on how frequently you need the new table data updated (every day, once a week, or only at specific times).
- Optionally, you can define some additional settings (if available).
- Configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here.
- Determine when to execute an Additional Full Sync. This will complement the incremental data extractions, ensuring that your data is completely synchronized with your source every once in a while.
Check your new source!
- Click Next to finalize the setup. Once completed, you’ll receive confirmation that your new source is set up!
- You can view your new source on the Sources page. Now, for you to be able to see it on your Catalog, you have to wait for the pipeline to run. You can now monitor it on the Sources page to see its execution and completion. If needed, manually trigger the pipeline by clicking on the refresh icon. Once executed, your new table will appear in the Catalog section.
Available streams
Leads
Leads
Leads of your company, synced incrementally by last update. Nested structures (customer, product, seller, messages, etc.) are delivered as JSON strings.Key Fields:
id- Unique identifier of the leadinternal_id- Internal numeric identifier of the lead in C2Sdescription- Free-text description of the lead’s interest (e.g. the property or product sought)observation- Latest observation or reminder note registered on the leadis_favorite- Whether the lead is marked as favorite by the seller
customer- Customer contact details: name, email and phone numbersproduct- Product or property the lead is interested in, with price, reference and locationseller- Seller (broker) currently responsible for the leadcollaborators- Additional users collaborating on the leadcreated_by- User who created the leadcompany- Company (branch) that owns the leadlead_source- Origin channel that generated the lead, e.g. a portal or campaignchannel- Communication channel of the lead, e.g. Showroom or WhatsApplead_status- Current status of the lead with id, alias and display namefunnel_status- Position of the lead in the sales funnellost_reasons- Reason registered when the lead was lostdone_details- Closed-deal details: done flag, notes and final pricearchive_details- Archiving details: archived flag and notestags- Tags applied to the leadlog- Chronological activity log entries of the leadmessages- Messages exchanged on the lead, with sender, recipient and timestampsschedulated_actions- Scheduled follow-up actions for the lead, with type, date and statusfacebook_attributes- Attributes captured from Facebook lead ads, when applicablecustom_attributes- Account-specific custom attributes of the lead
created_at- When the lead was createdupdated_at- Last update, used as the incremental replication keyexternal_created_at- Creation timestamp in the external system that originated the leadlast_activity_date- Last activity registered on the leadread_at- When the lead was first read by the sellerreplied_at- When the lead was first replied todone_deal_at- When the deal was closed, when applicable
from_hierarchy_company- Name of the hierarchy (company) that generated the leadurl- URL associated with the lead, when provided by the sourcedemo_company- Whether the lead belongs to a demo company
Sellers
Sellers
Sellers (brokers) of your company and its group companies.Key Fields:
id- Unique identifier of the sellername- Full name of the selleremail- Email address of the sellerphone- Phone number of the sellercompany- Name of the company (branch) the seller belongs tocompany_id- Identifier of the company (branch) the seller belongs tois_recipient- Lead distribution recipient flag/level for the sellercan_view_bucket- Whether the seller can view the lead pool (bucket)external_id- Identifier of the seller in an external system, when mappedexternal_name- Name of the seller in an external system, when mappedis_master- Whether the seller is a master (admin) user
Companies
Companies
Companies (branches) of your company’s group.Key Fields:
id- Unique identifier of the company branchname- Display name of the company branch
Distribution Rules
Distribution Rules
Lead distribution rules (regions) of your company and its branches.Key Fields:
cod_1- First matching code of the rule (e.g. development/property reference)cod_2- Second matching code of the rule (e.g. development name)cod_3- Third matching code of the rule (e.g. negotiation type)priority- Priority of the rule; lower numbers are evaluated firsttype_rule- Type of the rule: distribution (direct assignment) or rotation (round-robin)seller_id- Identifier of the seller the rule assigns leads tocompany_id- Identifier of the company (branch) the rule belongs to
Distribution Queues
Distribution Queues
Lead distribution queues of your parent company.Key Fields:
id- Unique numeric identifier of the distribution queuename- Display name of the queuepriority- Priority of the queue; higher-priority queues receive leads firststatus- Whether the queue is enabled or disabledqueue_type- Type of the queue (e.g. custom_queue)leads_count- Number of leads currently held by the queueredistributable_leads_count- Number of leads eligible for redistribution in the queueredistributable- Whether leads in the queue can be redistributedcheck_in- Whether sellers must check in to receive leads from the queuecheck_in_qr_code- Whether check-in is done via QR codegroup_memory_lead- Whether returning leads are routed to the seller who previously handled themreceptionist_enabled- Whether the receptionist flow is enabled for the queuetoday_working_time- Working hours of the queue for the current day (JSON string)sales_stand_form_id- Identifier of the sales-stand form linked to the queue, when applicableadvanced_queue_edit- Whether advanced queue editing is enabledrules- Matching rules that route leads into the queue (JSON string)next_seller_index- Index of the next seller in the rotationnext_seller- Seller next in line to receive a lead from the queue (JSON string)distribution_sellers_quantity- Number of sellers participating in the queue
Company Info
Company Info
Information about the authenticated company and its sub-companies.Key Fields:
company_id- Unique identifier of the authenticated companycompany_name- Display name of the authenticated companysub_companies- Sub-companies (branches) linked to the authenticated company (JSON string)
Good to know
- Rate limit: the C2S API tolerates roughly 10 requests per minute. The connector throttles itself accordingly, so large first syncs of the leads stream may take a while; subsequent incremental runs only fetch what changed.
- Encrypted IDs: all identifiers returned by C2S are encrypted strings and should be used as-is.
- Incremental sync: the leads stream uses the
updated_attimestamp, so leads that change status, receive messages or are updated in any way are re-synced automatically.