Search SignalHire for prospects and reveal their verified contact details.
Connect SignalHire with an API key to search its profile database by title, company, location and keywords, and to ask it to reveal verified emails and phone numbers for the people you find.
Connect
| Credential field | Required | Where it comes from |
|---|
API key (API_KEY) | Yes | A SignalHire API key, sent as the apikey header. |
| Setting | Required | What it is |
|---|
Callback URL (CALLBACK_URL) | Yes | Where SignalHire POSTs revealed contact details. Point it at a yekar webhook trigger. It is set here rather than per call so that no agent can redirect personal contact data to an address you did not choose. |
| Tool | Access | What it does |
|---|
Search prospects (yekar.signalhire.search-prospects) | Read | Search SignalHire's profile database and return profile summaries with a scrollId for the next page. Summaries carry NO email or phone - use reveal-contacts for those. |
Scroll search results (yekar.signalhire.scroll-search) | Read | Fetch the next page of a prospect search. Pass the requestId and the newest scrollId; each page returns a new scrollId. Call it immediately - a scrollId expires about 15 seconds after the page that issued it, and an expired one means re-running the search rather than retrying. |
Reveal contacts (yekar.signalhire.reveal-contacts) | Write | Ask SignalHire to reveal contact details for up to 100 people. ASYNCHRONOUS: this returns only a requestId - the contacts are delivered later to the callback URL configured on this connection, not as this tool's result. Spends a credit per revealed profile. |
Check credits (yekar.signalhire.check-credits) | Read | Report how many SignalHire credits the connected account has left. |
Notes
- In SignalHire, open the API section of your account settings and create an API key.
- Searching returns profile summaries only. Revealing contact details spends a credit per profile, and an exhausted balance is refused the same way a rate limit is - check-credits tells the two apart.
- Revealing is asynchronous: SignalHire POSTs the contacts to the Callback URL below rather than returning them. Set it to a yekar webhook trigger's URL so a second automation receives them - without it, reveal-contacts refuses rather than spending credits on a delivery that has nowhere to land.