Automate Data2CRM.
HumDay reads Data2CRM.’s own published API description and derives 336 operations from it. Describe the outcome you want in plain words — you get a program that is written, proven on real data, and run for you.
What Data2CRM. is
Make use of our in-depth documentation to get more information about the various functions of the service. Those willing to explore the mechanics of Data2CRM.API can test it in live regime using the short code samples. Select CRM: Loading... please wait Here are the API access keys: X-API2CRM-USER-KEY : <span id="d
API host: api-2445581398133.apicast.io:443
What HumDay can do in Data2CRM.
178 documented operations change something in Data2CRM.. The 81 most useful are listed here.
- POSTPOST for internalUser
/user - POSTPOST for lead
/application/entity/lead - POSTPOST for task
/application/entity/task - POSTPOST for user
/application/entity/user - POSTPOST for email
/application/entity/email - POSTPOST for event
/application/entity/event - POSTPOST for ticket
/application/entity/ticket - POSTPOST for comment
/application/entity/comment - POSTPOST for contact
/application/entity/contact - POSTPOST for invoice
/application/entity/invoice - POSTPOST for meeting
/application/entity/meeting - POSTPOST for campaign
/application/entity/campaign - POSTPOST for application
/application - POSTPOST bulk for lead
/application/entity/lead/bulk - POSTPOST bulk for task
/application/entity/task/bulk - POSTPOST bulk for user
/application/entity/user/bulk - POSTPOST bulk for email
/application/entity/email/bulk - POSTPOST bulk for event
/application/entity/event/bulk - POSTPOST bulk for ticket
/application/entity/ticket/bulk - POSTPOST bulk for comment
/application/entity/comment/bulk - POSTPOST bulk for contact
/application/entity/contact/bulk - POSTPOST bulk for invoice
/application/entity/invoice/bulk - POSTPOST bulk for meeting
/application/entity/meeting/bulk - POSTPOST bulk for campaign
/application/entity/campaign/bulk - POSTPOST for request
/application/request - DELETEDELETE for internalUser
/user/{internal_user_id} - PUTPUT for internalUser
/user/{internal_user_id} - POSTPOST for tag
/application/entity/tag - POSTPOST for call
/application/entity/call - POSTPOST for case
/application/entity/case - POSTPOST for note
/application/entity/note - POSTPOST for post
/application/entity/post - POSTPOST for quote
/application/entity/quote - POSTPOST for account
/application/entity/account - POSTPOST for product
/application/entity/product - POSTPOST for project
/application/entity/project - POSTPOST for priceBook
/application/entity/priceBook - POSTPOST for quoteItem
/application/entity/quoteItem - POSTPOST for attachment
/application/entity/attachment - POSTPOST for invoiceItem
/application/entity/invoiceItem - POSTPOST for opportunity
/application/entity/opportunity - POSTPOST for priceBookItem
/application/entity/priceBookItem - POSTPOST for opportunityProduct
/application/entity/opportunityProduct - POSTPOST for fieldItem
/application/field/{field_id} - POSTPOST for entityItem
/application/entity/{entity_id} - POSTPOST bulk for tag
/application/entity/tag/bulk - POSTPOST bulk for call
/application/entity/call/bulk - POSTPOST bulk for case
/application/entity/case/bulk - DELETEDELETE bulk for lead
/application/entity/lead/bulk - PUTPUT bulk for lead
/application/entity/lead/bulk - POSTPOST bulk for note
/application/entity/note/bulk - DELETEDELETE bulk for post
/application/entity/post/bulk - POSTPOST bulk for post
/application/entity/post/bulk - PUTPUT bulk for post
/application/entity/post/bulk - DELETEDELETE bulk for task
/application/entity/task/bulk - PUTPUT bulk for task
/application/entity/task/bulk - DELETEDELETE bulk for user
/application/entity/user/bulk - PUTPUT bulk for user
/application/entity/user/bulk - DELETEDELETE bulk for email
/application/entity/email/bulk - PUTPUT bulk for email
/application/entity/email/bulk - DELETEDELETE bulk for event
/application/entity/event/bulk - PUTPUT bulk for event
/application/entity/event/bulk - POSTPOST bulk for quote
/application/entity/quote/bulk - DELETEDELETE bulk for ticket
/application/entity/ticket/bulk - PUTPUT bulk for ticket
/application/entity/ticket/bulk - POSTPOST bulk for account
/application/entity/account/bulk - DELETEDELETE bulk for comment
/application/entity/comment/bulk - PUTPUT bulk for comment
/application/entity/comment/bulk - DELETEDELETE bulk for contact
/application/entity/contact/bulk - PUTPUT bulk for contact
/application/entity/contact/bulk - DELETEDELETE bulk for invoice
/application/entity/invoice/bulk - PUTPUT bulk for invoice
/application/entity/invoice/bulk - DELETEDELETE bulk for meeting
/application/entity/meeting/bulk - PUTPUT bulk for meeting
/application/entity/meeting/bulk - POSTPOST bulk for product
/application/entity/product/bulk - POSTPOST bulk for project
/application/entity/project/bulk - DELETEDELETE bulk for campaign
/application/entity/campaign/bulk - PUTPUT bulk for campaign
/application/entity/campaign/bulk - POSTPOST bulk for priceBook
/application/entity/priceBook/bulk - POSTPOST bulk for quoteItem
/application/entity/quoteItem/bulk - POSTPOST bulk for attachment
/application/entity/attachment/bulk
What HumDay can read from Data2CRM.
These are the operations a schedule or a trigger can watch.
- GETGET for internalUser
/user/list - GETGET for lead
/application/entity/lead/list - GETGET for post
/application/entity/post/list - GETGET for task
/application/entity/task/list - GETGET for user
/application/entity/user/list - GETGET for email
/application/entity/email/list - GETGET for event
/application/entity/event/list - GETGET for ticket
/application/entity/ticket/list - GETCOUNT for internalUser
/user/count - GETGET for comment
/application/entity/comment/list - GETGET for contact
/application/entity/contact/list - GETGET for invoice
/application/entity/invoice/list - GETGET for meeting
/application/entity/meeting/list - GETGET for campaign
/application/entity/campaign/list - GETGET for platform
/platform/list - GETGET for application
/application/list - GETGET for internalUser
/user/{internal_user_id} - GETGET for field
/application/field/list - GETGET for entity
/application/entity/list
How automating Data2CRM. works
- Describe the outcome. Say what you want to happen, in your own words. No node graphs, no field mapping.
- Approve the contract. HumDay writes down exactly what it will do, what it will touch, and what it will never do. You approve it before anything is built.
- See it proven. The program runs and shows you the result before it is allowed near your live Data2CRM. account.
- Grant access, then go live. You approve the specific Data2CRM. operations it may use — and only those.
Questions about Data2CRM. automation
- Can HumDay connect to Data2CRM.?
- Yes. HumDay reads Data2CRM.'s own published API description and derives the operations from it, so there is no hand-built connector to wait for. 336 operations are documented.
- Do I need to write code to automate Data2CRM.?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a test run before anything touches your Data2CRM. account.
- What can HumDay do in Data2CRM.?
- 178 of the 336 documented operations change something in Data2CRM., and 158 read from it. HumDay only ever uses the specific operations your approved contract needs.
- Is my Data2CRM. account safe?
- Your credentials are stored encrypted and are never shown in chat, code, or logs. Every run is limited to the operations you explicitly approved, and anything that writes to Data2CRM. is held behind that approval.
Where this came from
The operations above are read from a published API description for Data2CRM. at app.api2crm.com/swagger/spec/data2crm_api.json. Descriptions are the provider’s own words, not ours. Last published 2023-03-06.