Crono integration
Crono is a sales engagement platform and CRM. Read, search, create and update companies, contacts and deals; log notes and tasks; manage lists; read message templates and custom field definitions; import records in bulk or copy them from the connected CRM; build sequences and enroll contacts in them, which makes Crono email or message those people on schedule. Contacts, activities and call recordings are personal data; the raw log a calling platform attaches to a call is not returned. Authentication is a key pair from your Crono account: the public key in an X-Api-Key header and the private key in an X-Api-Secret header.
Say what should happen.
The workflow builds itself.
What you can do with Crono
Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.
Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.
Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.
List, 13 operations
add_companies_to_listAdd companies to listPOSTAgents: ask firstAdds existing companies to a list, by the list id and their company objectIds. Returns isSuccess.add_contacts_to_listAdd contacts to listPOSTAgents: ask firstAdds existing contacts to a list, by the list id and their contact objectIds. Returns isSuccess.add_sequences_to_listAdd sequences to listPOSTAgents: ask firstAdds existing sequences to a list, by the list id and their numeric sequence ids. Returns isSuccess.add_templates_to_listAdd templates to listPOSTAgents: ask firstAdds existing templates to a list, by the list id and their numeric template ids. Returns isSuccess.create_listCreate listPOSTAgents: ask firstCreates a list of companies (Account), contacts (Prospect), leads, templates or sequences (Strategy), optionally filled at once: objectIds for companies or contacts, ids for templates or sequences. Returns the list with its id.delete_listDelete listDELETEAgents: ask firstDeletes a list by its numeric id (from search_lists). Returns the deleted list.get_listGet listGETAgents: ask firstReturns one list by its numeric id: name, type of records it holds, owner and the users it is shared with.remove_companies_from_listRemove companies from listDELETEAgents: ask firstRemoves companies from a list, by the list id and their company objectIds. Returns isSuccess.remove_contacts_from_listRemove contacts from listDELETEAgents: ask firstRemoves contacts from a list, by the list id and their contact objectIds. Returns isSuccess.remove_sequences_from_listRemove sequences from listDELETEAgents: ask firstRemoves sequences from a list, by the list id and their numeric sequence ids. Returns isSuccess.remove_templates_from_listRemove templates from listDELETEAgents: ask firstRemoves templates from a list, by the list id and their numeric template ids. Returns isSuccess.search_listsSearch listsPOSTAgents: ask firstSearches lists by name, type, or the company, contact, template or sequence they contain. limit is required (at most 20 here), offset pages. Returns total and data[] with each list id, name, type, owner and sharing.update_listUpdate listPATCHAgents: ask firstRenames a list or changes who it is shared with, by its numeric id. Only the fields you send change: leave a field out to keep its current value. Returns the updated list.
Company, 7 operations
create_companyCreate companyPOSTAgents: ask firstCreates a company in Crono (name required) and returns it with its objectId. Optional: add it to a list (listId), also create it in the connected CRM (createInCrm), or enrich it from external data sources (enrichCompany).get_companyGet companyGETAgents: ask firstReturns one company by objectId (from list_companies or search_companies): website, industry, size, revenue, phone, Crono status, activity counters and owner. With* flags add custom field values, tags and sequences.import_companiesImport companiesPOSTAgents: ask firstImports up to 100 companies in one call as a background job; importType decides what happens to duplicates. Returns the import record: poll get_import with its id until status is Completed or CompletedWithErrors.list_companiesList companiesGETAgents: ask firstLists companies (Crono accounts) page by page: Limit 1 to 200 (vendor default 10), Offset to page. With* flags add the owner name, custom fields, tags, task analytics or active sequences. Returns total and data[] with objectId.search_companiesSearch companiesPOSTAgents: ask firstSearches companies by name, website, LinkedIn, status, industry, country, size, owner, dates, activity flags or custom field values. limit is required (at most 100 here), offset pages. Returns total and data[].sync_companies_from_crmSync companies from crmPOSTAgents: ask firstStarts a background job that copies up to 100 companies from the connected CRM (by their CRM object ids) into Crono, optionally adding them to a list. Returns the numeric job id in data: poll get_sync with it.update_companyUpdate companyPATCHAgents: ask firstUpdates one company by accountId: only the fields you send change, leave a field out to keep its current value. externalValues sets custom fields by property id (search_external_properties). Returns the updated company.
Contact, 7 operations
create_contactCreate contactPOSTAgents: ask firstCreates a contact (firstName, lastName required) and returns it. strategyId ENROLLS the new contact in a sequence whose automatic steps email or message the person; listId adds it to a list. A contact is personal data.get_contactGet contactGETAgents: ask firstReturns one contact by objectId: name, email, phones, title, LinkedIn, company, Crono status, opt-out status and counters. With* flags add custom fields, tags and sequences. Personal data.import_contactsImport contactsPOSTAgents: ask firstImports up to 100 contacts as a background job; importType decides what happens to duplicates. An item with strategyId enrolls that person in a sequence that emails them. Returns the import: poll get_import.list_contactsList contactsGETAgents: ask firstLists contacts (prospects) page by page: Limit 1 to 200 (vendor default 10), Offset. With* flags add the owner, company, custom fields, tags, task analytics or sequences. Personal data: names, emails, phones.search_contactsSearch contactsPOSTAgents: ask firstSearches contacts by name, email, LinkedIn, title, status, company, owner, sequence, verification, activity flags, opt-out or custom fields. limit is required (at most 100 here). Personal data.sync_contacts_from_crmSync contacts from crmPOSTAgents: ask firstStarts a background job copying up to 100 contacts or leads from the connected CRM into Crono, optionally adding them to a list or ENROLLING them in a sequence (strategyId). Returns the job id in data: poll get_sync.update_contactUpdate contactPATCHAgents: ask firstUpdates one contact by prospectId: only the fields you send change, leave a field out to keep its current value. externalValues sets custom fields by property id (search_external_properties). Returns the contact. A contact is personal data.
Deal, 6 operations
create_dealCreate dealPOSTAgents: ask firstCreates a deal on a company. accountId, pipeline and stage are required: pipeline and stage take the externalName values list_pipelines returns. Returns the deal with its objectId.get_dealGet dealGETAgents: ask firstReturns one deal by objectId: amount, stage, pipeline, close date, won and closed flags, company and owner. With* flags add the company, stage and pipeline details and custom fields.list_dealsList dealsGETAgents: ask firstLists deals (opportunities) page by page: Limit 1 to 200 (vendor default 10), Offset. With* flags add the owner name, the company, the stage and pipeline details and custom fields.search_dealsSearch dealsPOSTAgents: ask firstSearches deals by name, company, owner, stages, pipeline, close year, custom field values or date ranges. limit is required (at most 50 here), offset pages. Returns total and data[].sync_deals_from_crmSync deals from crmPOSTAgents: ask firstStarts a background job that copies up to 100 deals from the connected CRM (by their CRM object ids) into Crono. Returns the numeric job id in data: poll get_sync with it.update_dealUpdate dealPATCHAgents: ask firstUpdates one deal (opportunityId and its company's accountId required): only the fields you send change, leave a field out to keep its value. Can move the stage, or mark the deal won or closed. Returns the deal.
Note, 4 operations
create_noteCreate notePOSTAgents: ask firstLogs a note on a company (accountId and description required), optionally also on a deal and on contacts of that company. Returns the note with its objectId. Related contacts are personal data.get_noteGet noteGETAgents: ask firstReturns one note by objectId: its text, dates and the company, contact and deal it belongs to. With* flags add the author name and the related records. Related contacts are personal data.list_notesList notesGETAgents: ask firstLists notes logged on companies, contacts and deals, page by page: Limit 1 to 200, Offset. With* flags add the author name and the related company, contacts and deal. The related contacts are personal data.search_notesSearch notesPOSTAgents: ask firstSearches notes by company, deal, author, note ids, active flag or created and modified date ranges. limit is required (1 to 200), offset pages. Returns total and data[]. Related contacts are personal data.
Activity, 3 operations
get_activityGet activityGETAgents: ask firstReturns one logged activity (email, call or LinkedIn action) by objectId. With* flags add the related company, contact, deal and the email log (subject, HTML body), call log or LinkedIn log. Personal data.list_activitiesList activitiesGETAgents: ask firstLists logged activities (emails, calls, LinkedIn actions) page by page: Limit 1 to 200, Offset. With* flags add the related company, contact, deal and the email, call or LinkedIn log. Personal data.search_activitiesSearch activitiesPOSTAgents: ask firstSearches logged activities by company, contact, deal, user, task subtype or date ranges (created, modified, activity, first answer, first tracked). limit is required (1 to 200). With* flags add the related records.
Sequence, 3 operations
create_sequenceCreate sequencePOSTAgents: ask firstCreates a sequence (strategy) from its steps: type, delay in days, automatic flag and a template or inline subject and content. Creating it contacts nobody; contacts are enrolled with add_contacts_to_sequence.create_single_use_sequenceCreate single use sequencePOSTAgents: ask firstCreates a one-off sequence for ONE contact and enrolls that contact in it: its automatic steps email or message the person. prospectId, accountId and steps are required. Returns the enrollment with its tasks.search_sequencesSearch sequencesPOSTAgents: ask firstSearches sequences (strategies) by name, ids, owner, tags, or a company or contact they run on. limit is required (1 to 200). Returns each sequence with its counters; withSequence adds the steps and settings.
Sequence enrollment, 3 operations
add_contacts_to_sequenceAdd contacts to sequencePOSTAgents: ask firstENROLLS up to 100 existing contacts in a sequence: its automatic steps then email or message these real people on schedule. Returns addedCount and the enrollment ids. Stop one with stop_contact_sequence.search_sequence_enrollmentsSearch sequence enrollmentsPOSTAgents: ask firstLists the enrollments (sequence instances) of contacts in a sequence: current step, status, dates, selected email address and tasks. Filter by strategyId, status or task outcome; limit is required (1 to 200).stop_contact_sequenceStop contact sequencePOSTAgents: ask firstStops the sequence a contact is enrolled in, by prospectId: its remaining steps are not executed. Returns the stopped enrollment (status, step reached, tasks).
User, 3 operations
get_userGet userGETAgents: ask firstReturns one Crono user (a member of the subscription) by id: email, first and last name, active flag. Personal data.list_usersList usersGETAgents: ask firstLists the users of the Crono subscription page by page (Limit 1 to 200, Offset): id, email, first and last name, active flag (personal data). Use an id as userId to assign an owner.search_usersSearch usersPOSTAgents: ask firstSearches the users of the subscription by name, email or active flag. limit is required (1 to 200). Returns id, email, names and active flag of each (personal data).
Import, 2 operations
get_importGet importGETAgents: ask firstReturns one import job by its numeric id (from import_companies or import_contacts): status, progress, counts of records imported, new and with warnings. Poll it until status is Completed or CompletedWithErrors.list_importsList importsGETAgents: ask firstLists import jobs page by page (Limit 1 to 200, Offset), optionally filtered by record type and status: progress, counts of records imported, new and with warnings, and errors.
Sync, 2 operations
get_syncGet syncGETAgents: ask firstReturns one CRM sync job by the numeric id a sync_*_from_crm tool returned: status, progress (0 to 100), counts copied and with warnings. Poll it until status is Completed or CompletedWithErrors.list_syncsList syncsGETAgents: ask firstLists recent CRM sync jobs, most recent first (limit default 50, at most 100), optionally filtered by record type and status: progress and counts of records copied.
Task, 2 operations
create_taskCreate taskPOSTAgents: ask firstCreates a task on a company (accountId, type, activityDate, automatic required). automatic true lets Crono run it itself, so an automatic Email or LinkedIn task contacts the person. Returns isSuccess only.search_tasksSearch tasksPOSTAgents: ask firstSearches tasks (scheduled emails, calls, LinkedIn steps, to-dos) by company, contact, deal, sequence, list, type, date range, completion or automation error. limit and offset are required.
Template, 2 operations
get_templateGet templateGETAgents: ask firstReturns one message template by its numeric id: title, subject, content (may hold HTML and merge tags), type, language, sharing and usage counts (used, opened, answered).search_templatesSearch templatesPOSTAgents: ask firstSearches message templates by title, type, language, owner, shared or archived flag. limit is required (1 to 200). With* flags add the owner, tags and lists of each template.
Call recording, 1 operation
download_call_recordingDownload call recordingGETAgents: ask firstDownloads a call's audio recording (MP3) as a file, by externalCallId (the externalCallId of a call activity's callLog, from get_activity with WithCallLog). The recording holds the participants' voices: personal data.
External property, 1 operation
search_external_propertiesSearch external propertiesPOSTAgents: ask firstLists the custom fields (external properties) of one record type: id, name, value type, options and flags. Use an id as the key of externalValues when creating or updating companies, contacts or deals.
Pipeline, 1 operation
list_pipelinesList pipelinesGETAgents: ask firstLists the deal pipelines and their ordered stages: names (externalName is what create_deal and update_deal take), win probability and the closed and won flags of each stage.
Use Crono from Claude Code, Cursor or Codex
Connect Crono in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Crono operations become tools the client can call, next to every other integration you connected.
claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"
[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"{
"mcpServers": {
"livecontext": {
"type": "http",
"url": "https://livecontext.ai/mcp",
"headers": {
"X-API-Key": "YOUR_API_KEY"
}
}
}
}How to connect Crono
- Create your workspace
Sign up free. Nothing to install.
- Connect Crono once
Add your Crono connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
- Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.
Crono integration FAQ
What can you do with the Crono integration?
LiveContext exposes 60 operations on Crono, covering list, company, contact and deal.
