Connect Intercom and Owler
Describe what you want to happen between Intercom and Owler in plain words. HumDay writes the program, proves it on real data, and runs it — no node graph, no field mapping, and no connector to wait for.
What HumDay can do on each side
Read from each provider’s own published API description, in their words.
Intercom
108 documented operations. See all Intercom operations
- POSTCreate a ticket
/tickets - POSTCreate contact
/contacts - POSTCreate a message
/messages - POSTAdd subscription to a contact
/contacts/{contact_id}/subscriptions - POSTMerge a lead and a user
/contacts/merge - POSTCreate event summaries
/events/summaries
Owler
13 documented operations. See all Owler operations
- GETSearch Company by Ticker or Website or Name or PermID
/v1/company/search - GETBasic Search Company by Ticker or Website or Name or PermID
/v1/company/basicsearch - GETFuzzy Search Company by Name or Address or Phone
/v1/company/fuzzysearch - GETGet Feeds for given Company Ids
/v1/feed - GETGet Feeds for given Company Websites
/v1/feed/url - GETGet Company by URL
/v1/company/url/{website}
How a Intercom and Owler automation gets built
- Describe the outcome. Say what should happen — not which endpoints to call. HumDay works out which operations each side needs.
- Approve the contract. Before anything is built you see exactly what it will do in Intercom and Owler, and what it will never do.
- See it proven. The program runs and shows you the result before it is allowed near either live account.
- Grant access, then go live. You approve the specific operations it may use on each side — and only those.
Related integrations
- Intercom and OData for namespace microsoft.graphintegration
- OData for namespace microsoft.graph and Owlerintegration
- Cloudflare and Intercomintegration
- Cloudflare and Owlerintegration
- Intercom and NetBoxintegration
- NetBox and Owlerintegration
- GitHub and Intercomintegration
- GitHub and Owlerintegration
- Intercom and Mistintegration
- Mist and Owlerintegration
Questions about connecting Intercom and Owler
- Can Intercom connect with Owler?
- Yes. HumDay reads both providers' own published API descriptions and derives what each one can do, so neither side needs a hand-built connector before you can use it.
- How do I connect Intercom to Owler?
- Describe the outcome you want in plain words. HumDay agrees a contract with you saying exactly what it will do, writes the program, and shows you a proof run before either account is touched.
- Do I need to write code to integrate Intercom and Owler?
- No. There is no node graph to wire up and no field mapping to do. You say what should happen and HumDay works out which operations it needs from each side.
- What can HumDay do across Intercom and Owler?
- Intercom publishes 108 documented operations and Owler publishes 13. HumDay only ever uses the specific ones your approved contract needs.
- Is it safe to connect both accounts?
- Your credentials are stored encrypted and never appear in chat, code, or logs. Anything that writes to either Intercom or Owler is held behind an approval you grant explicitly.
Where this came from
Operations are read from the published API descriptions for Intercom and Owler. Descriptions are each provider’s own words, not ours.