- Recipes
- Apollo.io contacts to Azure Blob NDJSON file
Connect Apollo.io contacts and Azure Blob NDJSON file in our serverless environment
Use this template to Search for contacts using Apollo.io API using them to create NDJSON file entries in Azure Blob Container.
Share
Search for contacts using Apollo.io API
Used integrations:
JavaScript
Python
class HttpSourceApolloIoSearchContacts {
async init() {
// TODO: Create your http credential with apollo.io information:
// More info at https://yepcode.io/docs/integrations/http/#credential-configuration
// baseUrl: https://api.apollo.io/v1/
this.axiosClient = yepcode.integration.http(
"your-http-apollo-io-credential-name"
);
}
async fetch(publish, done) {
// TODO: Customize your request checking the API documentation:
// https://apolloio.github.io/apollo-api-docs/#search-for-contacts
const {
data
} = await this.axiosClient.post("/contacts/search", {
// TODO: You need to create a YepCode env var called `APOLLO_IO_API_KEY`
api_key: yepcode.env.APOLLO_IO_API_KEY,
q_keywords: "<contact-name>, <contact-title>, <contact-company>",
});
for (const contact in data.contacts) {
await publish(contact);
}
done();
}
async close() {}
}
class HttpSourceApolloIoSearchContacts:
def setup(self):
# TODO: Create your http credential with apollo.io information:
# More info at https://yepcode.io/docs/integrations/http/#credential-configuration
# baseUrl: https://api.apollo.io/v1/
self.session = yepcode.integration.http("your-http-apollo-io-credential-name")
def generator(self):
# TODO: Customize your request checking the API documentation:
# https://apolloio.github.io/apollo-api-docs/#search-for-contacts
response = self.session.post("/contacts", json={
# TODO: You need to create a YepCode env var called `APOLLO_IO_API_KEY`
"api_key": yepcode.env.APOLLO_IO_API_KEY,
"q_keywords": "<contact-name>, <contact-title>, <contact-company>",
})
response.raise_for_status()
contacts = response.json()
for contact in contacts:
yield contact
def close(self):
pass
Do you need help solving this integration with YepCode?
Let's talkCreate NDJSON file entries in Azure Blob Container
Used integrations:
JavaScript
Python
class AzureBlobTargetUploadNdjson {
async init() {
// TODO: Create your azure blob credential
// More info at https://yepcode.io/docs/integrations/azure-blob/#credential-configuration
const azureBlob = yepcode.integration.azureBlob(
"your-azure-blob-credential-name"
);
// TODO: customize the container name and blob name to upload
// // More info at https://docs.microsoft.com/en-us/javascript/api/@azure/storage-blob/blobserviceclient?view=azure-node-latest#@azure-storage-blob-blobserviceclient-getcontainerclient
const containerClient = azureBlob.getContainerClient("container-name");
const blockBlobClient = containerClient.getBlockBlobClient("blob-name");
// Transforms the items into a ndjson format
this.stringifier = ndjson.stringify();
this.upload = blockBlobClient.uploadStream(this.stringifier);
}
async consume(item) {
this.stringifier.write(item);
}
async close() {
try {
this.stringifier.end();
} catch (error) {
console.error(`Error ending stringifier`, error);
}
try {
await this.upload;
} catch (error) {
console.error(`Error ending upload`, error);
}
}
}
Comming soon
We are releasing new Python recipes every week
FAQs
YepCode is a SaaS platform that allows to create, execute and monitor integrations and automations using source code in a serverless environment.
We like to call it the Zapier for developers, since we bring all the agility and benefits of NoCode tools (avoid server provisioning, environment configuration, deployments,...), but with all the power of being able to use a programming language like JavaScript or Python.
These recipes are a good starting point for you to build your own YepCode processes and solve your integration and automation problems.
You only have to fill the sign up form and your account will be created with our FREE plan (no credit card required).
YepCode has been created with a clear enterprise approach (multi-tenant environment, team management, high security and auditing standards, IdP integrations, on-premise options,...) so we can be the Swiss army knife of any team of engineering, especially those that need to extract or send information to external systems, and where a certain dynamism or adaptation to change is necessary in that process.
Sure! You just need to do some configuration to allow YepCode servers to connect to that service. Check our docs page to get more information.